There are many different techniques that can be employed to improve the performance when working with the drafting of large assemblies. Simply put, use smart drafting techniques to generate in drafting only what is needed for the views. This will keep the data size down, which yields the best performance. If the smart drafting techniques aren’t sufficient, the assemblies should be simplified using the Convert Product to CATPart function. The following two sections show some of the smart drafting techniques and discusses simplified assemblies.
Examples of Smart Drafting Techniques for Large Assemblies
· Limit the number of scenes to the minimum number necessary to convey the Visualization of the assembly. Each scene created substantially increases the size of the CATProduct.
· Create Raster-generated views as images. This allows the user to quickly generate overall views for large assemblies that can be opened in visualization mode. Although there are restrictions on generating raster views, when used, they reduces data size andimprove addressable memory usage.
· Manually manage which elements are shown in the assembly, before generating them views. Anything that shouldn’t be seen in the view should not be visible in the assembly.
· Create views by multi-selecting only the nodes in the tree of the elements intended to be seen in the drawing, not the entire assembly.
Simplified Assemblies
A simplified assembly is created when the contents of an assembly are merged into one or more CATParts and then reassembled into a new CATProduct. The selected components of the original CATProduct(s) are converted into individual bodies within the CATParts. Assemblies over 200MB should be considered for the creation of simplified assemblies. Assemblies should be simplified using the Convert Product to CATPart function if the smart drafting techniques are not sufficient. Simplifying assemblies is best done after the design is nearly completed and ready for detailing. This technique is not intended to be used during the stages of the design when changes often occur because manual synchronization of the original data is required if there is a change.
