Rigyd vs NVIDIA SimReady Asset Library
They solve different halves of the same problem. NVIDIA's SimReady library is a curated catalog of ready-made assets. Rigyd converts raw 3D, images, and text into SimReady OpenUSD. Here's how they compare and when to use each.
Updated 2026-05-19
NVIDIA's SimReady library offers roughly 1,000 free, hand-validated assets, ideal for prototyping and generic scenes. Rigyd converts raw 3D models, images, and text descriptions into SimReady OpenUSD in minutes, ideal when simulation must match your real environment's specific objects at scale. Most teams use both.
Side-by-side comparison
| Dimension | NVIDIA SimReady LibraryCurated free catalog | RigydGenerate your own catalog |
|---|---|---|
| Asset source | ~1,000 NVIDIA-curated assets | Your own raw 3D (.glb, .fbx, .obj), images, or text |
| Catalog size | ~1,000 fixed assets | Unlimited, bounded only by your catalog |
| Physics accuracy | Hand-validated, high precision | AI-estimated: mass ±15-20%, friction ±0.1 |
| Covers your specific SKUs | No, generic objects only | Yes, your exact products and equipment |
| Output formats | OpenUSD | OpenUSD + MJCF native; URDF/SDF via community converters |
| Time to a new asset | N/A, use what exists | ~5 minutes per asset |
| Bulk / API processing | Manual download | Enterprise API for entire catalogs |
| Best fit | Prototyping, generic scenes | Production sim matching your real environment |
NVIDIA SimReady library: curated quality, fixed scope
NVIDIA's SimReady asset library is a set of roughly 1,000 hand-validated 3D assets built to the SimReady specification, correct USDPhysics schemas, semantic labels, and material bindings. Because each asset is curated, physics quality is high and consistent. The trade-off is scope: the library covers common, generic objects (pallets, crates, basic furniture, tools), not the specific SKUs in your warehouse or the custom equipment on your factory floor. It is free and the fastest way to start prototyping a scene.
Rigyd: your catalog, automated
Rigyd takes the opposite approach: instead of a fixed catalog, it converts raw 3D models, images, or text descriptions you provide into SimReady OpenUSD in about five minutes. Mass, friction, collision meshes, and semantic labels are estimated automatically, calibrated within domain-randomization variance ranges (mass ±15-20%, friction ±0.1). This is what you need when the simulation has to match your real environment, the 50,000 unique SKUs in a warehouse, or the proprietary fixtures in a manufacturing line, rather than generic stand-ins.
They are complementary, not mutually exclusive
The most common production setup uses both: NVIDIA's curated library for common, generic objects where a stand-in is fine, and Rigyd for the long tail of catalog-specific assets that no curated library could contain. The gap NVIDIA itself names, roughly 1,000 SimReady assets exist while a single warehouse needs 50,000+, is precisely the gap automated conversion fills.
When to choose each
Prototyping, generic scenes, zero budget, and getting a simulation running quickly with common objects.
Production simulation that must match your real environment, your specific SKUs, custom equipment, and asset diversity beyond ~1,000 objects.
Most production teams: curated assets for common objects, automated conversion for the catalog-specific long tail.
Where Rigyd fits
Rigyd outputs the same SimReady-spec OpenUSD that NVIDIA's library uses, so assets from both sources drop into the same Isaac Sim or Omniverse scene without friction. If you have started with NVIDIA's library and hit its coverage ceiling, Rigyd extends it with your own catalog rather than replacing it.