Skip to content
GuideAdvanced13 min

Export an OpenUSD scene

Choose OpenUSD encoding, composition, hierarchy, units, up axis, origin, instancing and data controls for a local USD pipeline.

Applies to
Current Prism release · Navisworks Manage 2025–2027
Availability
Ultra and eligible Pilot access; requires the installed OpenUSD component
For
Advanced visualization and scene-pipeline teams
Last reviewed

Choose the USD deliverable

Encoding table
EncodingUse
.usdGeneral extension using the selected physical encoding.
.usdaHuman-readable ASCII layer for inspection and version control on manageable scenes.
.usdcBinary Crate layer for compact, efficient scene delivery.
Root + .assetsRelative source payload layers for composition and source separation.

Configure the stage

  • Choose a single layer, source payload composition or per-model independent layers according to the downstream pipeline.
  • Use full hierarchy, storey grouping or flat elements based on selection and scene-management needs.
  • Set stage units and Z-up/Y-up explicitly to match the receiving application.
  • Use Federation center for stable coordinates, Preserve world for an absolute local frame, or an explicit XYZ origin shared with the receiver.
  • Preserve stable prototypes/instances when the consumer supports them; expand when interoperability requires independent meshes.
  • Select typed properties and Preview Surface material data deliberately; avoid exporting unnecessary model metadata.

OpenUSD requirements and limitations

Prism uses an isolated packaged OpenUSD 26.05 runtime. OpenUSD becomes available after Prism verifies Ultra access and the installed component. A separate OpenUSD installation does not enable this export format.

Validate the USD result

  1. Review Prism validation

    Resolve stage, layer, path, prim, reference and finite-coordinate errors before publication.

  2. Open the root layer

    Use the exact destination and confirm every relative payload resolves without absolute machine paths.

  3. Check stage orientation and units

    Measure a known object and compare the agreed origin.

  4. Check hierarchy and instances

    Confirm selection, source payloads, prototypes and repeated placements behave as planned.

  5. Check materials/properties

    Verify supported Preview Surface appearance and typed property mapping in the receiver.

Related guidance

Choose an export format and compatible settingsCompare Prism output formats, plan availability, packaging, coordinate conventions and the most important interoperability limits.Export 3D Tiles 1.1 and 3TZCreate a validated, locally written 3D Tiles hierarchy with direct GLB content, stable BIM feature identity and optional projected placement.Manage Prism engine components and repairUnderstand the signed components Prism activates for each plan, inspect their health and repair or add optional components safely.