This has a negative performance impact.Īvoid the practice of using Derived or Shrinkwrap models with Detail drawing views. When a derived component is used in a detail view, the entire model is calculated for creating the view instead of just the participating components. To reduce complexity some have resorted to using derive on large assemblies before creating views. Increase system memory to avoid hard drive memory swapping. When it happens, it will slow down Inventor operation. If there are other processes running at the same time, Windows use swap (hard drive) memory. For a typical 10K component assembly, it takes about 3GB to fully load the assembly.
Impact: Depending on geometric complexity and assembly levels, Inventor may require more memory than the minimum 8GB. Opening the top-level assembly in older version of Inventor and keep working on it can lead to corruption. Top-level assembly is left at the older version while some of its components are saved in newer versions. If components within the subassembly have DOF and they are supposed to be free, avoid creating constraints to subassembly origin planes, axes, or point. Their DOF at the top level assembly becomes confusing. The subassembly origin planes can be moved and all components constrained to the origin planes will move. Impact: The flexible subassembly exposes all the degrees of freedom within the subassembly. Components within the subassembly are constrained to subassembly origin planes, axes, or point. Then, turn it off until, again, the next change.Īn under-constrained subassembly. After using adaptivity, consider turning adaptivity off until model updates occur, then turn it on and allow it to resolve. Consider using Skeletal modeling instead. Part1 drives Part2 and Part2 drives Part3. Cascading adaptive relationships should be avoided, i.e.
Adaptive relationships must a clear adaptor and adaptee defined to avoid cyclic relationships. It can lead to performance problems at the assembly level because the part geometry must be updated along with assembly constraints. If you must use an LOD, use the Master LOD for all drawing views.
For a large assembly this can increase memory usage drastically.īest Practice: Use View Representations instead of LODs. Impact:For each view using a different LOD, a copy of the assembly is loaded into memory. Practice: Using more than one LOD representation in a drawing.
0 kommentar(er)
