OpenBridge Modeler

Cached Dynamic View Scenarios

There are many benefits to the dynamic nature of Dynamic Views, and there are also scenarios and workflows where you may not want to reprocess a Dynamic View. Occasionally design activities and schedules can be separate from the documentation process. A Cached Dynamic View permits the documentation to capture a point in time to reflect the state of the design, and allow the documentation team to work toward a delivery milestone. Meanwhile, the design team can proceed with design development without impacting the documentation. Once the documentation is complete, the Cached Dynamic Views can be restored to dynamic to update the documentation to the current state of the design.

Another beneficial Cached Dynamic View scenario is when a design has stabilized and is not undergoing significant changes. Users can experience a performance increase while navigating between files and models since Dynamic Views do not need to sync with design model changes. In this case, Cached Dynamic Views is an additional option to enhance documentation productivity.

Cached Dynamic Views also provide options that increase the fidelity of Dynamic Views. A Cached Dynamic View enables you to include Calculated Intersections, make faceted curves more smooth, and to use custom line styles that are not supported in a traditional Dynamic View.

Note:
  • The option to cache a Dynamic view is only available in Dynamic Views using the Visible Edges display style.
  • A Cached Dynamic View remains connected to the design model and is not intended to be an independent Dynamic View. Separating a Cached Dynamic View from a design model, has the same effect as removing a traditional Dynamic View from a model. To output an independent Dynamic View, publish an i-model or use Save As in conjunction with the Merge Visible Edges of 3D Attachment References option.