What's coming next
The SimReady Foundation specification is itself young — at the time of writing it is the team’s stated position that the spec “currently covers basic static props (ones that don’t move or articulate)”, and the broader profile set is being filled in as the foundation grows. Rigyd’s coverage moves with it.
The foundation publishes profiles across two asset families today, and we map them like this:
| Profile family | Asset class | Foundation profiles | Rigyd coverage |
|---|---|---|---|
| Props | Single rigid-body objects for robotics scenes | Prop-Robotics-Neutral, Prop-Robotics-PhysX, Prop-Robotics-Isaac | Live today — every conversion validated against Prop-Robotics-Neutral; runtime-specific profiles roll out as we wire in PhysX and Isaac-specific feature adapters. |
| Robot bodies | Articulated multi-body robots and agents | Robot-Body-Neutral, Robot-Body-Runnable, Robot-Body-Isaac | On the roadmap — lands alongside Rigyd’s articulated-asset and robot generation work. The validator already implements the articulation, driven-joint, and robot-core requirement codes (HI.009, JT.ART.*, DJ.*, BA.*, RC.*, RM.*); they’re returned as N/A on prop assets and will activate once articulated outputs ship. |
When the foundation publishes additional profiles (vehicles, characters, environments — all signposted as future work in the SimReady overview), Rigyd’s coverage will track them. The validator is structured so that adding a profile means adding a target, not rewriting the engine.