Start with the package and your simulator version
Before importing an asset, identify its entry USD file, texture and layer dependencies, licence, and any supplied validation report. Record the Isaac Sim build you intend to use. A format label such as USD is not a tested-version guarantee.
Keep the extracted folder structure intact. Open the entry file rather than guessing which internal layer is the complete asset. If the package has no entry-file guidance, ask the supplier before moving or renaming files. The simgenerator quickstart explains the package inspection workflow.
Inspect the scene before running physics
Our recommended first pass is deliberately small:
- Open the asset in an otherwise simple scene and inspect warnings about missing dependencies.
- Compare its dimensions with a known task reference, such as the robot gripper or a measured object.
- Check orientation, materials and the prim hierarchy.
- Inspect the collision representation separately from the visible surface.
- Identify static bodies, moving bodies and joints that the task requires.
NVIDIA's physics fundamentals describe how colliders, rigid bodies and articulations are represented and used in Isaac Sim. Use documentation that matches your installed version when applying settings.
Run an interaction, not only a turntable
Choose a short test with a clear outcome. For a cabinet, open and close the door through its intended range. For a grasped object, check contact, lift and release. For a navigation obstacle, check its collision footprint against the route.
Record initial state, scene settings and the result. If something fails, isolate the asset from the larger scene before changing several parameters at once. An asset can look correct while failing a contact or motion requirement.
Keep acceptance scoped
The SimReady Foundation profiles provide explicit content requirements. Keep profile validation alongside runtime testing; neither replaces the other. Report the version and checks that passed rather than describing an asset as universally compatible.
Inspect the specifications in our asset library. For a complete facility or a task-specific set of interactions, scope a digital twin with the team. The required simulator build and acceptance tests should be part of that scope.