AnsweredAssumed Answered

what's quicker when importing 3rd party data?

Question asked by Josh Killalea on Jan 25, 2015
Latest reply on Jan 25, 2015 by Josh Killalea

we have quite a bit of 3rd party data in our large models, and ideally we would like to just be able to import data in the future and be confident we are doing the right thing.


what we have noticed when doing the imports is that SW will either let you make an assembly with 1 part for each body in the thing you are importing and that part usually consists of a single "imported body".


the other option is to make the whole thing one part and everything is imported as surface bodies.or you can save your assembly as a part and it converts all the parts in the assembly as surfaces.


the real question is, which is less resource hungry? which one is quick/more stable to open?


any ideas or input welcome.