SimReady describes requirements for a use case
A simulation asset needs more than a convincing render. Your task may depend on contact geometry, moving parts, meaningful labels and a package that opens on another machine.
NVIDIA SimReady Foundation defines content requirements through profiles for different runtime use cases. A useful readiness claim names the profile and version, the checks performed and any failures or exceptions. The word SimReady alone does not establish that a model works in every simulator.
What to inspect in a package
Use this checklist when evaluating an asset, whether it was hand-authored or generated:
| Area | Question to answer |
|---|---|
| Geometry | Are scale, orientation and task-relevant shapes correct? |
| Contacts | Do colliders preserve the handles, openings and surfaces the robot will touch? |
| Dynamics | Are moving bodies, mass assumptions and joint limits documented where needed? |
| Appearance | Do the required materials and textures resolve? |
| Labels | Can the task identify the relevant objects and parts? |
| Packaging | Can a colleague open the entry file with all dependencies available? |
| Evidence | Which profile and simulator build were actually checked? |
A static background prop does not need the same behavior as a drawer the robot must open. Choose requirements around the intended interaction before comparing asset quality.
OpenUSD is the container, not the acceptance test
OpenUSD can represent and compose scene content. The presence of a USD file does not show that a collision model, joint or physical value was authored correctly. Inspect the resolved scene and run the relevant task in your target simulator.
For a drawer, a useful acceptance test includes reaching its handle, opening it through the intended range, checking for intersections and returning it to rest. A successful import is only the first check.
Keep the evidence with the asset
Record the asset revision, validation profile, validator version, simulator version and task checks. Keep unresolved findings visible. A package can be successfully created while validation reports failures; packaging and validation are separate outcomes.
Browse the hand-authored library, read the USD quickstart, or run supported checks with the free SimReady Validator. simgenerator follows NVIDIA SimReady Foundation as an authoring standard; review each package's actual evidence for your task.