Skip to content

What's covered today

View Markdown llms-full.txt

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, Isaac Lab, MuJoCo, Gazebo, or any other OpenUSD-aware simulator. Concretely, validation covers:

  • Stage-level conformance — defaultPrim, upAxis = Z, metersPerUnit = 1.0, kilogramsPerUnit, and a single root UsdGeomXform.
  • 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 and MDL 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, with Wikidata Q-codes where applicable, so synthetic-data pipelines and VLM-based scene understanding can use the asset out of the box.
  • Rigid-body physics — UsdPhysics 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 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.