Instance a SimReady Asset#

This page expands the answer to What is the design pattern or best practice for instancing a SimReady asset?.

A vendor creates a SimReady asset (for example, a Power Distribution Unit) and provides it to an integrator who has “n” of them in their facility. How do you distinguish instance properties (unique per placement) from asset properties (shared across all instances)?

USD’s composition model already provides the building blocks:

  • References: Each placement of the asset in a scene is a reference to the shared asset definition. The asset definition (geometry, materials, base physics properties) is authored once and shared across all instances.

  • Overrides: Per-instance properties (position, orientation, operational state, serial number, specific configuration) are authored as overrides on each reference. These are instance-level. They differ per placement without modifying the shared asset.

  • Native instancing: For rendering performance, USD’s native instancing allows the renderer to share geometry data across identical placements while still supporting per-instance overrides on non-geometric properties.

  • Payloads: Heavy data (detailed geometry, internal components) can be deferred using payloads, so scenes with hundreds of instances only load the detail they need.

In object-oriented terms: the asset definition is the class, each reference is an instance, and overrides are instance attributes. USD composition handles this natively. No special SimReady mechanism is required.

What SimReady Adds#

  • Where a Profile exists, it defines which properties belong in the shared asset definition (and must be validated there) and which are expected to be overridden per instance.

  • Example: a Prop-Robotics-Neutral asset’s collision geometry and mass properties are asset-level (shared), while placement transforms are instance-level.

  • As domain Profiles expand, the distinction between asset-level and instance-level properties will be made explicit in each Profile’s Requirements.

What SimReady Does Not Prescribe#

Specific instancing workflows are inherently contextual:

  • How many levels of payload nesting

  • When to use native instancing rather than explicit references

  • How to partition hierarchy for a particular scene scale

These depend on the simulation, scene complexity, and runtime.

  • Some of these patterns can never become specifications or Profiles by design.

  • SimReady specs are prescriptive, defining the bar for interoperability. Asset structuring decisions that do not affect interoperability are best addressed through guidance.

Decisions a Profile Does Not Cover#

For decisions not covered by a Profile:

  • Use the VFI Guide and OpenUSD’s Principles of Scalable Asset Structure for reference.

  • Leverage AI coding agents to reason through your specific trade-offs using the documentation as a guide.

  • The VFI Guide is descriptive. It helps you weigh options for your context rather than mandating a single answer.