Complex Assemblies

[GTRcktSci]

Would someone be able to offer some insight on the following issue?


I'm working on a project that contians steel gratings used for walkways, but I can't seem to come up with a solution that isn't performance-hindering on my
computer. I made grating that looks great, but it seriously slows down my computer after just one level. It's not necessarily my system either (I'm running a P4 2.66 GHz, 1GB of DDR RAM, 128MB vid card). The way I modeled the grating: I basically extruded "rectangular bars" the length that the particular grating needed to be. The rectangular bars (in my model) represent length of the section (load bearing bars in industry terms). I then extruded round bars perpendicular to create the cross bars. (I hope that makes sense). I just can't figure out a less cpu-intensive method of doing it.


If anyone is able to shed some light on this, it would be greatly appreciated.


Thanks

 

[Rich1000]

I also have encountered this problem on a number of occasions. Unfortunately i have not come up with any solution that maintains the visual appearance of the model. Doe anyone else have any ideas?


Cheers





Rich

 

[Israr]

On the specs you have mentioned (P4 2.66 GHz, 1GB of DDR RAM, 128MB vid card) I have developed assemblies of the order of 300 MBs.


You have to use good modeling skills, intelligent use of suppress option, a few anti-performance-hindering configuration options and the best performance configuration of your operating systems can help you.


Israr

 

[dufortm]

You can also make aextrusion and apply a mapping on them.

 

[sip]

What if you saved the part as a neutral file, opened it, and replaced the part in your assembly with this new part?





Sip

 

[GTRcktSci]

dufortm,


That sounds similar to what someone in another forum told me to do. What exactly is mapping and how do you go about doing it. Also, is this something you can use Family Table with for different sized sections?


sip,


I'm not sure what you mean, would you mind elaborating?


Thanks guys,


GTRcktSci

 

[sip]

You can save the part that is causing the slowness as a .neu file.


Openthis.neu fileas a new part (.prt), save this new part and replace the part in the assembly that causes the slownesswith this new part.


The.neuimported part containsa single feature, that regenerates very fast. This may solve your problem. I hope this is clear.


Sip

 

[GTRcktSci]

That makes much more sense and sounds like the perfect solution. So... what's the catch I would assume something like not being able to modify, etc.





GTRcktSci

 

[sip]

The file made from NEU is non-modifiable. Howerever, if you keep your old file intact, you can always change it there, and re-save it to neu. The assembly should pick up the same references if you leave them in there.





Sip