---
title: "What's covered today"
description: "The SimReady Foundation profile Rigyd targets today and the spec areas it enforces on every conversion."
---

Today, every Rigyd output targets the **`Prop-Robotics-Neutral`** profile: single rigid-body props built for robotics simulation, runtime-neutral so they drop cleanly into [Isaac Sim](https://developer.nvidia.com/isaac/sim), [Isaac Lab](https://isaac-sim.github.io/IsaacLab/), [MuJoCo](https://mujoco.org/), [Gazebo](https://gazebosim.org/), or any other [OpenUSD](https://openusd.org/)-aware simulator. Concretely, validation covers:

- **Stage-level conformance** — `defaultPrim`, `upAxis = Z`, `metersPerUnit = 1.0`, `kilogramsPerUnit`, and a single root [`UsdGeomXform`](https://openusd.org/release/api/class_usd_geom_xform.html).
- **Naming and on-disk layout** — prim, file, and folder names that survive a round-trip through Linux, Windows, and the Omniverse Nucleus path resolver, with no absolute paths in references.
- **Geometry** — manifold meshes, valid topology, indexed primvars, no co-located vertices, correct face winding, normals on non-subdivided meshes, and sane RTX world-space bounds.
- **Visual materials** — [`UsdPreviewSurface`](https://openusd.org/release/spec_usdpreviewsurface.html) and [MDL](https://www.nvidia.com/en-us/design-visualization/technologies/material-definition-language/) bindings that resolve, texture color spaces set correctly, dimensions within RTX limits.
- **Non-visual materials** — base material type and surface coating annotated so downstream physics queries (friction, restitution, density priors) have something to read.
- **Semantic labels** — every renderable prim labeled via [`SemanticsLabelsAPI`](https://docs.omniverse.nvidia.com/kit/docs/omni.replicator.core/latest/API.html), with [Wikidata Q-codes](https://www.wikidata.org/wiki/Wikidata:Identifiers) where applicable, so synthetic-data pipelines and VLM-based scene understanding can use the asset out of the box.
- **Rigid-body physics** — [`UsdPhysics`](https://openusd.org/release/api/usd_physics_page_front.html) `RigidBodyAPI` and `MassAPI` applied correctly, mass and inertia coherent with collision volume, no nested rigid bodies without a connecting joint, no skewed transforms.
- **Collision** — [`CollisionAPI`](https://openusd.org/release/api/class_usd_physics_collision_a_p_i.html) and `MeshCollisionAPI` applied to the right prims, collision approximations chosen per geometry, invisible colliders marked `purpose = "guide"` so they don't render but still simulate.

The full check list is what determines whether a conversion is allowed to finish. If you are submitting through the API, you do not need to think about any of it — the asset either passes and is downloadable, or the job fails and your credit is refunded.

For the per-requirement status of every code in the registry — including the ones marked `N/A` on prop assets — see [Full requirement coverage](/simready-validation/full-coverage).