Large Assembly
Basic Concepts
- breaking assemblies into subassemblies facilities multi-user design environments
- for performance and collaboration, better to have more subassemblies. assemblies with large number of components slows down the hardware.
- best practice is to have few top-level part components, but have majority of parts in sub-assemblies
- lightweight components only load a subset of the data. The remaining data is loaded as needed.
- lightweight can be either set when loading, or automatically set when a certain number of components is loaded (via T>O>S>Performance)
- break large assemblies into smaller sub-assemblies. This creates faster and efficient assemblies.
Along the Way
- set isolate in display states to help manage the files
- use Isolate to create a temporary view state. This is not saved into the Display State. Right click on the component to isolate. You can set whether to display the other components wireframe, transparent, or hidden.
- lightweight components cannot be edited, but can be mated
Techniques
- best practice to always work in lightweight assembly mode. You can always clear the lightweight check box.
