Overview
Every asset that comes out of a Rigyd conversion is checked against the SimReady Foundation specification before the job is marked completed. We do not ship a “SimReady” label on assets that do not actually meet the spec.
If you have ever opened a USD in Isaac Sim and watched it fall through the floor, intersect itself, or refuse to articulate, you already know what this is for. Validation is the line between “loads in a viewer” and “drops into a simulator and behaves.”
What we conform to
Section titled “What we conform to”The SimReady Foundation is an open specification layer on top of OpenUSD that defines exactly what a simulation-ready asset must contain — naming and folder structure, units, hierarchy, geometry, visual and non-visual materials, semantic labels, rigid-body and collision physics, joints and articulation, and runtime-specific requirements for PhysX and NVIDIA Isaac Sim. The foundation packages these requirements into features and rolls them up into profiles — concrete bundles you can target.
Rigyd’s validator implements the full requirement registry — every code from NP.001 (prim naming) through RC.009 (root joint pinned per robot type) — and runs it on every successful conversion. A conversion is only completed when the asset clears the profile we are targeting for that asset class.
Where to go next
Section titled “Where to go next”- What’s covered today — the profile we target and the spec areas it enforces.
- What’s coming next — how our coverage tracks the SimReady Foundation’s published profile families.
- Full requirement coverage — every requirement code in the spec and our current status against it.