Skip to content

USD Export, Import and Apply

Commercial

Included in the public demo Compare editions

The USD files group of the USD menu moves a document between realvirtual WEB and the OpenUSD world. It has three functions: Export USD scene…, Import USD scene… and Apply realvirtual data from USD….

These functions belong to the Commercial edition and are included in the public demo. A Community build shows them as Not in this build. See Editions.

The USD menu opened from the left main menu with its three groups: USD files (export, import, apply), Animation (record USD animation) and Isaac Sim live sync with the Sync to Isaac Sim switch

Export USD scene… writes the open document as a USD file. It needs an open document; without one the entry is disabled. The dialog starts with Export this document for Isaac Sim, Omniverse, Blender or usdview. and offers two modes:

ModeFileWhat it contains
Complete scene.usdzGeometry, materials and the realvirtual data (drives, sensors, signals) as customData. Referenced placements contain no geometry. The file has no animation — to capture motion, record a USD animation.
realvirtual data layer.rv.usdaOnly the realvirtual data, on the original USD prim paths. Use it together with the USD scene the document was imported from. Available only for documents imported from USD; otherwise the mode is disabled with the note Only for documents imported from USD.

Pick a mode and click Export. The browser downloads the file.

The Export dialog with the two modes: Complete scene (.usdz) and realvirtual data layer (.rv.usda), the second one disabled with the note that it is only for documents imported from USD

A document can contain placements, for example from the planner. The export does not copy their geometry into the file. The dialog warns “{n} placements will be exported without geometry” before you export, and a note repeats it afterwards. The placements are written as empty prims that carry their realvirtual data, so they show up in the receiving tool with geometry only if you bring the referenced assets there as well.

If a vertex colour cannot be combined with a material in the target format, it is approximated, and the note after the export tells how many.

Import USD scene… opens the import dialog on its USD tab and creates a new document from a USD file. If the file carries realvirtual customData from an earlier export, the import restores it. Settings and limits of the dialog are described under Importing CAD.

A typical round trip: export the document, change or extend the geometry in Blender or Omniverse, then bring the realvirtual data back. Apply realvirtual data from USD… replaces the realvirtual data of the open document with the data from a USD file. Geometry stays unchanged.

  1. Choose Apply realvirtual data from USD…. A dialog explains what happens.
  2. Click Choose USD file… and pick the file. Nothing is changed yet.
  3. Review the preview: the file name, how many nodes were matched and how many prims are unmatched. Nodes that would lose their data are listed.
  4. Click Apply data. If nodes would lose data, the button reads Apply and remove missing data, so you confirm the removal explicitly. The document is written and reloaded.

The Apply dialog before a file is chosen: it explains that the realvirtual data of this document is replaced, geometry stays unchanged, and the data is reviewed before applying; buttons Cancel and Choose USD file

The preview can block the apply:

  • Ambiguous prims — some prims cannot be assigned to exactly one node. Nothing can be applied from this file; the dialog lists the prims.
  • No realvirtual data in the file — the document has data, but the file has none. The tool that wrote the file most likely dropped customData on export. You can still apply, which removes the data of the document, after an explicit confirmation.

The MCP tool web_export_usd runs the same export (mode standalone or overlay) and writes the result into the open project under exports/. web_import_usd_extras and web_import_usd_extras_commit are the two steps of Apply: preview first, commit second. See AI bridge.