Simulation & digital-asset dossier · 02
Read robot USD assets as versioned simulation dependencies with explicit roots, layered physics, articulation metadata and validation markers—not as downloadable manufacturing packages.
Identify the exact asset first
NVIDIA Isaac Sim provides a broad catalogue of USD robot assets spanning wheeled, holonomic, manipulator, quadruped, aerial and humanoid platforms. Current documentation also distinguishes multiphysics-ready variants and marks which transformed assets have been validated against the originals.
Digital asset map
Versioned USD paths, referenced layers and catalogue locations for supported robot families.
Verify before adoptionFreeze Isaac Sim version, asset root, exact USD path, dependency resolver, layer stack and all referenced files.
Links, joints, articulation, drives, limits and robot relationships encoded through USD and physics schemas.
Verify before adoptionInspect joint axes, limits, drive mode, gains, mass, inertia, collision APIs, root articulation and units.
Visual geometry, materials, sensors and platform-specific extensions linked into the composed stage.
Verify before adoptionTrace every external texture, material, sensor profile and extension dependency, including redistribution boundaries.
Catalogued validation indicators and, for a growing subset, neutral-physics multiphysics variants.
Verify before adoptionRecord whether the exact asset is validated, unmarked/in validation or independently modified; rerun validator after every change.
Layered licence reading
Use follows the applicable NVIDIA software and content terms for the exact product and asset version.
Archive the governing terms, product version and asset path; do not describe catalogue availability as open-source permission.
Robot designs, names, meshes and source materials can retain manufacturer or upstream rights.
Confirm asset-specific attribution, redistribution, trademark and commercial-use conditions before export or publication.
Rendered images, synthetic data and modified USD layers can combine rights from software, source assets and added content.
Create an output provenance record; do not infer downstream rights from successful generation.
This table is a source-navigation and engineering-decision aid, not legal advice. Use original licence texts and qualified advice for an actual decision.
Model & asset validation gates
Isaac Sim build, asset root, USD path, content version, extensions, referenced layers, checksums and governing terms.
Stop conditionStop if the asset path silently resolves to a different version or any required layer is missing.
Validator report for folder structure, schemas, links, joints, materials, physics layers, relationships and thumbnails.
Stop conditionDo not use an asset with unresolved fundamental validator failures in controlled experiments.
Static pose, joint sweep, drive response, contacts, mass/inertia, sensor alignment, timestep and solver sensitivity.
Stop conditionA catalogue validation marker cannot replace testing of the behaviours used by the experiment.
Baseline outputs and a documented comparison after engine, asset, driver or local-layer upgrades.
Stop conditionDo not compare results across versions when asset or physics drift has not been quantified.
FUURAA analysis
Rapid access to heterogeneous robot assets within a composable USD ecosystem for simulation, synthetic data and workflow integration.
Stable-looking catalogue names hide changing asset roots, product versions, validation states and rights inherited from third parties.
Treat every USD path as a pinned dependency. Combine NVIDIA's structural validator with experiment-specific physics checks and an asset-rights manifest.
Applicability boundary