![]() ![]() The last selection, “Preserve geometry references” allows you to save data for the assembly mates in the multibody part. There will be a few options to select from, as shown below. To save an assembly as a multi-body part document, first, open an assembly file. ![]() This would also cut down on overall file size as I wouldn’t have to send a large assembly file. I can save the engine assembly as a part document in SOLIDWORKS and send the part file to the client without potentially risking breaking the assembly file itself. For example, if I design a jet engine and a client wants to see if my engine will fit in their frame. You may want to do this because this makes file sharing easier. You also can save assemblies as a multibody part. Assemblies have more files to juggle, more potential for downstream problems.Saving multibody parts without their feature tree eliminates long rebuild times.Multibody hide/show components are slower than assemblies.Save time by using multi bodies instead of adding a configuration for each part and the assembly level.Multibody performance is not as good as assembly graphical performance.Multibody generally has faster file loading speed (no external references).Assemblies take longer to load in general.Assemblies have access to dynamic motion, flexible assemblies, etc.Assembly.īelow is a chart in my opinion on some of the pros and cons of multibody parts vs assemblies: In this article I will review the key differences of SOLIDWORKS Multibody part vs. I don’t work in industry, but I generally see clients I work with use multibody parts for purchased parts and then insert them into assemblies. For example, in part files, we lack the ability to use some tools like dynamic clearance, collision detection, etc. SOLIDWORKS multibody parts are not meant to replace the use of assemblies. A general rule to follow is that one part generally should represent a single part number for your bill of materials. ![]()
0 Comments
Leave a Reply. |