Autodesk Inventor

[#1]

Here is a assembly that I have been working on just to show you what I would call a "large assembly". This assembly is pretty slow to work in and it takes about 15 minutes to open it up. I would think that it would handle yours just fine. Kirk -- IV R9, SP1 Dell PWS360, 2.6ghz, P4 2 Gb ram nVidia FX1000 6.14.10.6808Driver 1260x1024x32 bit "JerkerPihl" wrote in message news:6513916.1099029324135.JavaMail.jive@jiveforum1.autodesk.com... > The assembly is made of 992objects.

[#2]

If he has 992 unique parts with 50 features each then he would be in trouble...not ? Regards, Jorgen "Kirk A." wrote in message news:418235b7$1_3@newsprd01... > Inventor should be able to handle this just fine. Were any of the parts in > the assembly imported in from a .stp or .sat file? > > -- > IV R9, SP1 > Dell PWS360, 2.6ghz, P4 > 2 Gb ram > nVidia FX1000 > 6.14.10.6808Driver > 1260x1024x32 bit > > > "JerkerPihl" wrote in message > news:6513916.1099029324135.JavaMail.jive@jiveforum1.autodesk.com... >> The assembly is made of 992objects. > >

[#3]

Is that "parts" or "instances"?

[#4]

I don't think it would make any difference in the assembly no matter how many features were in each part. If the parts are adaptive, this would slow the assembly down. -- IV R9, SP1 Dell PWS360, 2.6ghz, P4 2 Gb ram nVidia FX1000 6.14.10.6808Driver 1260x1024x32 bit "JGH" wrote in message news:41823944$1_2@newsprd01... > If he has 992 unique parts with 50 features each then he would be in > trouble...not ? > > Regards, > Jorgen > > "Kirk A." wrote in message > news:418235b7$1_3@newsprd01... > > Inventor should be able to handle this just fine. Were any of the parts in > > the assembly imported in from a .stp or .sat file? > > > > -- > > IV R9, SP1 > > Dell PWS360, 2.6ghz, P4 > > 2 Gb ram > > nVidia FX1000 > > 6.14.10.6808Driver > > 1260x1024x32 bit > > > > > > "JerkerPihl" wrote in message > > news:6513916.1099029324135.JavaMail.jive@jiveforum1.autodesk.com... > >> The assembly is made of 992objects. > > > > > >

[#5]

> I don't think it would make any difference in the assembly no matter how > many features were in each part. Makes a big difference, as does face / edge complexity. That's why cosmetic threads and the like are used.

[#6]

Face/edge complexity, yes, I would think so. I thought the cosmetic threads were used because the coil feature took so much to calculate. The parts are not rebuilt as the assembly is loaded. Only the graphical information is loaded. -- IV R9, SP1 Dell PWS360, 2.6ghz, P4 2 Gb ram nVidia FX1000 6.14.10.6808Driver 1260x1024x32 bit "Jeff Howard" wrote in message news:41828c42$1_3@newsprd01... > > I don't think it would make any difference in the assembly no matter how > > many features were in each part. > > Makes a big difference, as does face / edge complexity. That's why > cosmetic threads and the like are used. >

[#7]

I am still on IV8 SP! and I get the 80% of address space used every day. Some times after working for 1-2 hours, most times after 4-5 hours. It depends a lot on how many files I open (does not seem to matter if I close them or not) IDW files with 10 plus views makes it happen faster. My assys are not even close to what others here think as large (smallest assy I have had this problem with has 10 different parts, 50 total parts, plus a few iparts, parts have less than 100 features and some arrays)
If I shut down and restart I get another few hours.

The PC specs are as follows:
IBM A30 8199-66U
Intel Pentium 4 2.66GHz (512KB), 533MHz FSB,
2 GB IBM Memory,
40GB 7200RPM IDE HDD, divided into 10 and 30 gb
Intel Extreme Graphics (onboard)
NVIDIA Quardro NVS 64MB PCI
Intel 10/100 Ethernet,

virtual memory is is divided C: is 350-450mb and E: is 2500-2700 mb
Task manager shows Peak at less than 700000 K
WE are running NT4 SP6
Is this a good amount with 2gb ram?
Is it good to split over 2 drives?
Thanks
Fred

[#8]

> > The parts are not rebuilt as the assembly is loaded. Only the graphical > information is loaded. > Parts are not regenerated on loading, but part geometry must be loaded to generate render meshes; all face / edge dependant. Assembly constraints, assembly features, top down methods, etc. all require model geometry access. I'm not really sure, but imagine it would be pretty easy to get an idea by importing patterned solids; complex parts in one assy and prismatic parts in another (import so they are multiple part definitions and not multiple instances of the same definition), then working (not just looking at) the assemblies.

[#9]

> WE are running NT4 SP6 What little I know that may be pertinent: Large imports have always been prone to triggering these errors. NT4 / SP6a was the lowest limit, W2K / SP1 raised it, W2K / SP2 raised it still higher (e.g. larger STEP files could be imported without getting 80% - shutting down type errors. Relevant to what you are seeing?

[#10]

Stevensf, You may try a uninstall and reinstall of your video driver. This fixed a similar problem on one of our work stations.