Omniverse Realtime Viewer

NVIDIAOfficialCreated by NVIDIA Omniverse

Skill
Tool integration
Software development
Apache-2.0
Medium risk

From the author

Use as the top-level router for Omniverse Realtime Viewer USD apps, XR delivery, SPG GPU processing, stylized rendering, and focused viewer reference documents.

— the description by NVIDIA Omniverse

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Omniverse Realtime Viewer skill acts as a central routing and architectural framework for developing USD-based 3D viewer applications. It provides a structured approach to composing rendering, scene state, and delivery mechanisms, ensuring that developers can integrate OVRTX rendering, OVStage scene management, and various UI or streaming adapters effectively. The skill emphasizes a modular architecture where the viewer runtime, UI/input adapters, and delivery systems are decoupled, allowing for consistent behavior across local and streamed environments.

What it does

Provides a routing architecture for USD viewer apps, XR delivery, and GPU-accelerated rendering.
Defines the separation of concerns between viewer runtime, UI adapters, and delivery systems.
Offers guidance on integrating OVRTX for high-fidelity 3D rendering.
Establishes conventions for camera interaction, scene state management, and input handling.
Supports the implementation of specialized features like stylized rendering and CAE/CFD visualization.
Provides protocols for agent-to-UI communication and scene control.

When to use it

When starting the development of a new USD-based realtime viewer application.
When integrating advanced rendering features like stylized visualization or AOV switching.
When building XR or spatial editing capabilities into an existing Omniverse application.
When you need to standardize the architecture for local and streamed viewer deployments.
When implementing chat-driven scene control or agent-based inspection of a 3D scene.

Advantages

Promotes a clean, modular architecture that separates rendering logic from UI and transport.
Ensures consistent behavior across different delivery methods, such as local windows or WebRTC streaming.
Provides clear paths for extending functionality without disrupting the core viewer runtime.
Facilitates the integration of complex simulation and visualization data into the viewer.
Standardizes conventions for scene state, selection, and camera control.

Usage examples

“How do I set up a basic USD viewer application using the Omniverse Realtime Viewer architecture?”: The agent will guide you to start with the viewer app reference, resolve dependencies, and implement the core runtime owner to manage the OVStage and OVRTX renderer.
“I need to add stylized rendering to my existing viewer. Where should I start?”: The agent will direct you to the stylized visualization references to implement the required USD/Lua/CUDA nodes within your existing runtime owner.
“How can I enable an AI agent to control the viewer scene?”: The agent will point to the A2UI Scene Copilot reference to implement an operation interface that allows the agent to send commands through the existing runtime owner.
“How do I switch between different render outputs like beauty and depth in my viewer?”: The agent will explain how to use the AOV switching reference to map RenderVars and update the RenderProduct's orderedVars through the runtime owner.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/nvidia/omniverse-realtime-viewer/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip omniverse-realtime-viewer.zip -d .agents/skills

Documentation by NVIDIA Omniverse

Omniverse Realtime Viewer

Build responsive USD viewers by composing OVRTX rendering, OVStage scene state, and the delivery/UI libraries appropriate to the app. Use this package for viewer architecture and interaction; use each selected SDK's upstream guidance for installation and exact release-specific APIs.

Start With The App

When delivery is explicit, select its recipe through references/routing.md and follow its current phase. Otherwise start with references/usd-viewer-app/README.md. For an existing app, keep its architecture and read only the references for the requested change. Broad app, conventions and UI catalogs are lookups as needed.
Resolve the selected libraries through references/dependencies/README.md. Preserve the project's manifest unless an upgrade is requested.
Build a working frame and camera interaction in the chosen shell, then add the requested capabilities. Read references/conventions.md for shared input, camera, selection, and protocol conventions.
Use references/viewer-ux-workflow/README.md for broader interface design. Loading, selection feedback, errors, and input responsiveness belong in the first working app, alongside rendering.
Validate the actual delivery path with references/validation.md. A browser screenshot does not validate a native window or a different transport.

Architecture

Owner	Responsibility
Viewer runtime	Own the live OVStage, publication clock, OVRTX renderer, scene changes, and render stepping.
UI and input adapter	Display frames and copied app state; send user intent to the runtime owner.
Storage/query/simulation workers	Perform their assigned work and return results through the selected integration boundary.
Delivery adapter	Present locally or stream through ovstream; respect frame ownership and backpressure.

Use OVRTX for USD/3D rendering. Browser apps display its WebRTC video; local apps present its output through their native shell. A missing GPU means rendering is unverified, not a reason to substitute a browser 3D renderer.

Keep viewer cameras, settings, effects, and transient edits in app-owned session or runtime state so the source USD stays intact. Serialize scene mutation and render stepping through the runtime owner. Read references/ovstage-ovrtx-integration/README.md for that loop, then the population or data-plane references when implementing scene loading or attribute writes.

Keep expensive loading and metadata work off the UI and render threads. Keep transport details behind a delivery adapter so camera, selection, properties, and loading state can be reused across local and streamed shells.

Add Capabilities As Needed

Use references/routing.md to select camera/picking, scene management, render settings, cloud assets, simulation, editor tools, deployment, or CAE/CFD visualization. Read the selected capability's implementation flow and its linked contract; the full reference catalog is not a prerequisite for a first frame.

For simulation, use the routing reference's Simulation Ecosystem section plus references/realtime-sim-integration/README.md. For UI-driven forces or control, add references/interaction-round-trip/README.md.

For example scenes, use references/usd-sample-data/README.md. When a runtime failure needs diagnosis, use references/troubleshooting/README.md and the selected SDK's matching release guidance before changing the architecture.

Solid Modeling: Upstream First

For usd-brep, exact BRep, solid modeling, kernel failures, CAD topology, or BrepArray questions, first read references/dependencies/README.md → USD BRep. Follow the owning repository's current agent guidance, skills, operation docs, and package API before selecting local integration references. Discover the upstream router rather than assuming skill names or directory layouts remain fixed. Upstream owns modeling semantics, schema rules, tuning, and diagnostics; this package owns OVRTX display, worker handoff, selection mapping, and publication timing.

GPU Processing And Stylized Viewers

For custom GPU processing, chained outputs and lens sampling, read references/spg-processing/README.md. For toon, ink, technical/X-Ray styles, geometry strokes or full wireframe, continue to references/stylized-visualization/implementation.md. Its USD/Lua/CUDA starting node and geometry/depth/composite build sequence work with the selected viewer recipe; use references/stylized-visualization/style-recipes.md for the preset math and references/stylized-visualization/README.md for supporting contracts. Implement the result inside the existing OVRTX/runtime owner and deliver the published processed output. These instructions do not require a sample checkout or a prior stylized-rendering implementation.

For an optional usd-brep geometry source, first read references/dependencies/README.md → USD BRep and the owning repository's current agent guidance, skills, and operation docs; then read references/stylized-visualization/usd-brep-source.md for the display boundary.

XR Viewers

For headsets, immersive viewers, or spatial editors, start with references/xr-viewer-recipe/README.md. Resolve SDK setup and contracts through references/dependencies/ovxr.md; the library owns OpenXR lifecycle and frame submission. For controllers, hands, navigation, or scene tools, add references/xr-spatial-input/README.md and references/ovxr-python-interactions/README.md. For projection-integrated UI, read references/ovxr-composition-ui/README.md and references/ovxr-composition-ui-validation/README.md.

Files

ATTRIBUTION.mdAdded by AutoGineer943 B
BENCHMARK.md13.4 KiB
LICENSELicence file added by AutoGineer11.2 KiB
SKILL.md6.4 KiB
evals/evals.json7.0 KiB
references/a2ui-scene-copilot/README.md10.9 KiB
references/aov-switching/README.md10.5 KiB
references/cae-cfd-visualization/README.md10.1 KiB
references/cae-cfd-visualization/cae-data-ingestion.md5.6 KiB
references/cae-cfd-visualization/coordinate-systems-and-up-axis.md11.0 KiB
references/cae-cfd-visualization/data-and-operators.md11.7 KiB
references/cae-cfd-visualization/driving-cae-viz-via-ovstage.md6.4 KiB
references/cae-cfd-visualization/emitter-and-seed-sources.md16.3 KiB
references/cae-cfd-visualization/glyphs.md7.1 KiB
references/cae-cfd-visualization/ovstage-render-and-camera.md11.0 KiB
references/cae-cfd-visualization/ovui-controls.md13.2 KiB
references/cae-cfd-visualization/rtwt-blueprint-recreation.md11.9 KiB
references/cae-cfd-visualization/streaming-cae-viewer.md25.9 KiB
references/cae-cfd-visualization/temporal-playback.md9.2 KiB
references/cae-cfd-visualization/usd-authoring-and-materials.md21.5 KiB
references/cae-cfd-visualization/volume-rendering.md2.5 KiB
references/camera-auto-select/README.md9.0 KiB
references/camera-controls/README.md20.9 KiB
references/camera-picker/README.md9.5 KiB
references/cloud-assets/README.md4.5 KiB
references/cloud-deployment/README.md19.6 KiB
references/cloud-deployment/container-image-build.md2.2 KiB
references/cloud-deployment/gpu-container-runtime.md2.8 KiB
references/cloud-deployment/nvcf-self-hosted.md8.4 KiB
references/cloud-deployment/nvcf-viewer-container-contract.md4.8 KiB
references/cloud-deployment/webrtc-network-diagnostics.md3.9 KiB
references/cloudxr-opaque-data-channel/README.md1.1 KiB
references/conventions.md7.4 KiB
references/cpp-native-viewer/README.md4.9 KiB
references/cpp-native-viewer/build-details.md5.2 KiB
references/cpp-native-viewer/interaction-features.md11.3 KiB
references/cpp-native-viewer/presentation-loop.md8.0 KiB
references/cpp-native-viewer/project-build.md3.4 KiB
references/cpp-native-viewer/renderer-session.md7.1 KiB
references/cpp-native-viewer/validation.md3.4 KiB
references/dependencies/README.md6.8 KiB
references/dependencies/electron-shm.md1.5 KiB
references/dependencies/environment-validation.md6.6 KiB
references/dependencies/frontend.md2.3 KiB
references/dependencies/local-openusd-gpu.md8.7 KiB
references/dependencies/nvidia-runtime.md14.8 KiB
references/dependencies/ovrtx.md3.1 KiB
references/dependencies/ovstream.md3.3 KiB
references/dependencies/ovxr.md2.3 KiB
references/dependencies/quick-setup.md2.6 KiB
references/dependencies/skia-yoga.md936 B
references/electron-shm-viewer/README.md2.5 KiB
references/electron-shm-viewer/architecture-project.md6.3 KiB
references/electron-shm-viewer/electron-client.md6.5 KiB
references/electron-shm-viewer/protocol-interaction-lifecycle.md7.9 KiB
references/electron-shm-viewer/python-shm-server.md5.5 KiB
references/electron-shm-viewer/validation.md2.8 KiB
references/exact-brep-in-usd/README.md2.5 KiB
references/gl-viewport-overlay/README.md8.0 KiB
references/gl-viewport-overlay/architecture.md4.1 KiB
references/gl-viewport-overlay/example-gizmo.md5.5 KiB
references/gl-viewport-overlay/interaction-pattern.md4.0 KiB
references/gl-viewport-overlay/projection-alignment.md4.3 KiB
references/headless-shm-cli/README.md12.3 KiB
references/huggingface-usd/README.md7.7 KiB
references/interaction-round-trip/README.md40.1 KiB
references/local-viewer/README.md17.8 KiB
references/native-picking-selection/README.md13.1 KiB
references/navigation-presets/README.md4.6 KiB
references/navigation-presets/preset-camera-ops.md5.1 KiB
references/newton-physics/README.md8.8 KiB
references/object-selection/README.md11.1 KiB
references/ovrtx-rendering/README.md23.0 KiB
references/ovstage-data-plane/README.md3.5 KiB
references/ovstage-live-geometry/README.md3.3 KiB
references/ovstage-ovrtx-integration/README.md5.0 KiB
references/ovstage-population/README.md3.7 KiB
references/ovstage-runtime/README.md3.1 KiB
references/ovui-library/README.md3.3 KiB
references/ovui-library/api-reference.md4.3 KiB
references/ovui-library/extending.md4.8 KiB
references/ovui-local-viewer-recipe/README.md4.7 KiB
references/ovui-local-viewer-recipe/interaction-features.md16.9 KiB
references/ovui-local-viewer-recipe/project-structure.md6.2 KiB
references/ovui-local-viewer-recipe/setup-shell-renderer.md16.4 KiB
references/ovui-local-viewer-recipe/validation-build-order.md6.1 KiB
references/ovwidgets-editor-shell/README.md5.4 KiB
references/ovxr-composition-ui-validation/README.md7.1 KiB
references/ovxr-composition-ui-validation/evidence-gates.md3.5 KiB
references/ovxr-composition-ui-validation/frustum-placement.md2.4 KiB
references/ovxr-composition-ui-validation/library-only-validation.md8.1 KiB
references/ovxr-composition-ui-validation/owned-orchestration.md5.3 KiB
references/ovxr-composition-ui-validation/viewer-evidence.md4.0 KiB
references/ovxr-composition-ui/README.md8.5 KiB
references/ovxr-composition-ui/async-raster-pipeline.md5.0 KiB
references/ovxr-composition-ui/compositor-passes-and-sync.md6.4 KiB
references/ovxr-composition-ui/depth-tools.md5.0 KiB
references/ovxr-composition-ui/editor-document-model.md4.8 KiB
references/ovxr-composition-ui/experience-quality.md8.5 KiB
references/ovxr-composition-ui/foveation-and-edge-math.md3.5 KiB
references/ovxr-composition-ui/library-only-compositor.md10.4 KiB
references/ovxr-composition-ui/native-build-and-discovery.md4.6 KiB
references/ovxr-composition-ui/performance-and-telemetry.md7.9 KiB
references/ovxr-composition-ui/primary-projection-compositor.md3.5 KiB
references/ovxr-composition-ui/primary-projection.md4.1 KiB
references/ovxr-composition-ui/projection-and-depth.md5.3 KiB
references/ovxr-composition-ui/raster-abi.md3.0 KiB
references/ovxr-composition-ui/sdk-frame-backend.md1.6 KiB
references/ovxr-composition-ui/skia-yoga.md2.8 KiB
references/ovxr-composition-ui/spatial-interaction.md5.6 KiB
references/ovxr-composition-ui/spatial-surfaces-and-interaction.md10.4 KiB
references/ovxr-composition-ui/telemetry-contract.md3.8 KiB
references/ovxr-composition-ui/validation-and-live-gates.md3.9 KiB
references/ovxr-foveation-and-display/README.md1.1 KiB
references/ovxr-frame-loop-and-readback/README.md1.2 KiB
references/ovxr-library-runtime/README.md1.1 KiB
references/ovxr-library-runtime/ar-compositing.md4.4 KiB
references/ovxr-library-runtime/frame-input-order.md2.2 KiB
references/ovxr-library-runtime/library-only.md1.1 KiB
references/ovxr-library-runtime/live-ar-controls.md4.3 KiB
references/ovxr-library-runtime/mirror-lifetime.md4.1 KiB
references/ovxr-library-runtime/settings-and-lifetime.md3.9 KiB
references/ovxr-library-runtime/viewer-assembly.md225 B
references/ovxr-openxr-runtime/README.md1012 B
references/ovxr-python-interactions/README.md1.8 KiB
references/ovxr-python-interactions/architecture.md5.5 KiB
references/ovxr-python-interactions/feature-patterns.md7.4 KiB
references/physics-simulation/README.md7.1 KiB
references/prim-info-display/README.md10.9 KiB
references/prim-pick-effects/README.md7.3 KiB
references/prim-transform-safety/README.md8.6 KiB
references/realtime-sim-integration/README.md7.0 KiB
references/render-settings/README.md12.6 KiB
references/routing.md37.7 KiB
references/section-views/README.md5.8 KiB
references/seg-outline-highlight/README.md1.5 KiB
references/selection-animation/README.md5.0 KiB
references/selection-feedback/README.md7.5 KiB
references/smlib-brep-pitfalls/README.md2.5 KiB
references/spg-processing/README.md8.0 KiB
references/stage-attribute-reads/README.md6.2 KiB
references/stage-hierarchy/README.md20.3 KiB
references/stage-hierarchy/fallback-worker-protocol.md7.4 KiB
references/stage-loading/README.md7.1 KiB
references/stage-management/README.md6.6 KiB
references/stage-queries/README.md6.1 KiB
references/streaming-client/README.md25.6 KiB
references/streaming-lifecycle/README.md4.6 KiB
references/streaming-messages/README.md19.5 KiB
references/streaming-messages/server-handler-map.md3.1 KiB
references/streaming-server/README.md17.7 KiB
references/streaming-server/frame-loop-and-continuity.md3.8 KiB
references/streaming-viewer-recipe/README.md1.9 KiB
references/streaming-viewer-recipe/client-protocol.md14.2 KiB
references/streaming-viewer-recipe/interaction-features.md13.8 KiB
references/streaming-viewer-recipe/project-structure.md7.3 KiB
references/streaming-viewer-recipe/server-runtime.md20.2 KiB
references/streaming-viewer-recipe/validation-build-order.md8.5 KiB
references/streaming-vs-local/README.md9.4 KiB
references/stylized-visualization/README.md8.7 KiB
references/stylized-visualization/aov-guide-contracts.md8.1 KiB
references/stylized-visualization/implementation.md11.4 KiB
references/stylized-visualization/line-compositor-delivery.md7.7 KiB
references/stylized-visualization/mesh-xray.md10.1 KiB
references/stylized-visualization/reproduction-validation.md10.2 KiB
references/stylized-visualization/style-composition-contract.md5.4 KiB
references/stylized-visualization/style-recipes.md14.7 KiB
references/stylized-visualization/usd-brep-source.md4.9 KiB
references/subprocess-geometry-bridge/README.md3.5 KiB
references/tauri-local-viewer/README.md6.7 KiB
references/tauri-shm-transform-gizmo/README.md12.3 KiB
references/transform-manipulator/README.md17.1 KiB
references/troubleshooting/README.md11.2 KiB
references/troubleshooting/scenario-playbooks.md24.7 KiB
references/usd-sample-data/README.md12.0 KiB
references/usd-viewer-app/README.md5.0 KiB
references/validation.md6.3 KiB
references/viewer-backend-interface/README.md20.1 KiB
references/viewer-control-patterns/README.md4.8 KiB
references/viewer-data-view-patterns/README.md5.6 KiB
references/viewer-feedback-status/README.md5.0 KiB
references/viewer-input-routing/README.md11.9 KiB
references/viewer-layout-patterns/README.md4.7 KiB
references/viewer-ux-workflow/README.md5.2 KiB
references/viewport-overlays/README.md9.9 KiB
references/viewport-overlays/cuda-compositing.md6.6 KiB
references/viewport-resize/README.md4.0 KiB
references/vulkan-compositing/README.md6.1 KiB
references/vulkan-compositing/depth-overlays.md15.7 KiB
references/vulkan-compositing/interop-and-lifecycle.md6.6 KiB
references/webgl-shm-transport/README.md14.5 KiB
references/windows-native-setup/README.md11.6 KiB
references/xr-client-connection/README.md1.1 KiB
references/xr-client-message-contract/README.md8.5 KiB
references/xr-desktop-mirror/README.md13.8 KiB
references/xr-session-modes-and-passthrough/README.md930 B
references/xr-spatial-input/README.md2.3 KiB
references/xr-spatial-input/advanced-tools.md5.2 KiB
references/xr-spatial-input/controllers.md16.3 KiB
references/xr-spatial-input/feature-validation.md4.9 KiB
references/xr-spatial-input/gesture-arbitration.md4.9 KiB
references/xr-spatial-input/gesture-filtering.md5.5 KiB
references/xr-spatial-input/hand-recognizers.md4.0 KiB
references/xr-spatial-input/hands.md10.3 KiB
references/xr-spatial-input/navigation.md13.5 KiB
references/xr-spatial-input/physics-interaction.md23.2 KiB
references/xr-spatial-input/simulation-lifecycle.md5.9 KiB
references/xr-spatial-input/stage-composition.md4.9 KiB
references/xr-spatial-input/teleport-acceptance.md5.2 KiB
references/xr-spatial-input/webxr-client.md3.9 KiB
references/xr-tracking-anchor-and-scale/README.md950 B
references/xr-viewer-recipe/README.md10.5 KiB
skill-card.md7.7 KiB
skill.oms.sig58.2 KiB

references/usd-sample-data/README.md

USD Sample Data

Triggers

Use this skill for I need sample data, find USD assets, get me a scene, download USD, sample scenes, test data, USD examples, or need a stage to load.

Use this skill when a developer needs sample OpenUSD data for an ovrtx viewer and does not already have scenes. Prefer local filesystem paths because ovrtx loads stages and their dependencies from disk.

Recommended storage root:

export USD_ASSET_ROOT="${USD_ASSET_ROOT:-/path/to/usd-assets}"
mkdir -p "$USD_ASSET_ROOT"

Fast Choices

Need	Use
Official viewer samples	`stage01.usd` / `stage02.usd` from `https://d4i3qtqj3r0z5.cloudfront.net/omni.usd_viewer.samples-106.3.3.zip`
Fast smoke test	`stage01` / `stage02` from the official viewer samples, or NVIDIA Scene Templates
Small material/variant test	`usd-wg/assets` StandardShaderBall
Demo scene	OldAttic, Kitchen Set, or a small Marbles subset with required dependencies
Renderer stress test	full Marbles, Showcases, Sample Scenes pack
Production-scale stress	full Sample Scenes, ALab, or Moana

Official USD Viewer Sample Stages (stage01 / stage02)

These are the actual sample stages used by the Omniverse USD Viewer extension. Use them when an agent needs the viewer's default sample scenes with known-good USD composition, PBR materials, and texture coverage.

Direct download URL, no auth required:

https://d4i3qtqj3r0z5.cloudfront.net/omni.usd_viewer.samples-106.3.3.zip

Archive size can vary; check the download response rather than assuming a small fixture. The archive contains samples_data/ with stage01.usd, stage02.usd, materials/, textures/, and referenced sub-USD files.

Download and unzip:

export USD_ASSET_ROOT="${USD_ASSET_ROOT:-/path/to/usd-assets}"
mkdir -p "$USD_ASSET_ROOT/usd_viewer_samples"

curl -L https://d4i3qtqj3r0z5.cloudfront.net/omni.usd_viewer.samples-106.3.3.zip -o /tmp/omni.usd_viewer.samples.zip
unzip -q /tmp/omni.usd_viewer.samples.zip -d $USD_ASSET_ROOT/usd_viewer_samples

After unzipping, load:

$USD_ASSET_ROOT/usd_viewer_samples/samples_data/stage01.usd
$USD_ASSET_ROOT/usd_viewer_samples/samples_data/stage02.usd

This is the recommended source for agents needing the official viewer default sample scenes.

Preserve the samples' authored material values when composing viewer prims. For interactive material effects, use prim-pick-effects and restore only values the viewer changed.

NVIDIA Omniverse Downloadable Packs

Source page: https://docs.omniverse.nvidia.com/usd/latest/usd_content_samples/downloadable_packs.html

CDN base: https://d4i3qtqj3r0z5.cloudfront.net/

No auth is required. Use curl -L and keep each pack in its own directory so relative asset references stay intact after unzip.

Pack	Size	Direct URL	Notes
Default Scene Templates	24 MB	`https://d4i3qtqj3r0z5.cloudfront.net/Scene_Templates_NVD%4010011.zip`	10 template scenes; best quick-start pack
Sample Scenes	26 GB	`https://d4i3qtqj3r0z5.cloudfront.net/Sample_Scenes_NVD%4010013.zip`	441 assets; includes Old Attic, Marbles, composed scenes
Showcase Scenes	2.3 GB	`https://d4i3qtqj3r0z5.cloudfront.net/Showcases_Content_NVD%4010011.zip`	2 RTX showcase scenes; depends on Sample Scenes
Commercial	5.8 GB	`https://d4i3qtqj3r0z5.cloudfront.net/Commercial_NVD%4010013.zip`	82 office assets; needs Base Materials
Industrial	1.8 GB	`https://d4i3qtqj3r0z5.cloudfront.net/Industrial_NVD%4010012.zip`	72 industrial components
Residential	22.5 GB	`https://d4i3qtqj3r0z5.cloudfront.net/Residential_NVD%4010012.zip`	507 residential assets
Warehouse	18 GB	`https://d4i3qtqj3r0z5.cloudfront.net/Warehouse_NVD%4010013.zip`	763 warehouse components
Base Materials	8.2 GB	`https://d4i3qtqj3r0z5.cloudfront.net/Base_Materials_NVD%4010013.zip`	Required by Commercial pack
Environments	varies	`https://d4i3qtqj3r0z5.cloudfront.net/Environments_NVD%4010012.zip`	HDR domes and skies
Characters	891 MB	`https://d4i3qtqj3r0z5.cloudfront.net/Characters_NVD%4010012.zip`	Rigged assets; viewer usually does not support animation playback

Download a CloudFront Pack

export USD_ASSET_ROOT="${USD_ASSET_ROOT:-/path/to/usd-assets}"
mkdir -p "$USD_ASSET_ROOT/downloads" "$USD_ASSET_ROOT/Scene_Templates"

curl -L \
  "https://d4i3qtqj3r0z5.cloudfront.net/Scene_Templates_NVD%4010011.zip" \
  -o "$USD_ASSET_ROOT/downloads/Scene_Templates_NVD.zip"

unzip -q "$USD_ASSET_ROOT/downloads/Scene_Templates_NVD.zip" \
  -d "$USD_ASSET_ROOT/Scene_Templates"
find "$USD_ASSET_ROOT/Scene_Templates" -iname "*.usd" -o -iname "*.usda" -o -iname "*.usdc"

For large packs, prefer resumable downloads:

curl -L -C - \
  "https://d4i3qtqj3r0z5.cloudfront.net/Sample_Scenes_NVD%4010013.zip" \
  -o "$USD_ASSET_ROOT/downloads/Sample_Scenes_NVD.zip"

NVIDIA Public S3 Bucket

Bucket host: omniverse-content-production.s3.us-west-2.amazonaws.com

Use AWS CLI with unsigned requests:

python3 -m pip install --user awscli
export USD_ASSET_ROOT="${USD_ASSET_ROOT:-/path/to/usd-assets}"
mkdir -p "$USD_ASSET_ROOT/NVIDIA_Samples"

aws s3 sync --no-sign-request \
  "s3://omniverse-content-production/Samples/Marbles/" \
  "$USD_ASSET_ROOT/NVIDIA_Samples/Marbles/"

Use HTTPS for individual files when the exact key is known:

curl -L \
  "https://omniverse-content-production.s3.us-west-2.amazonaws.com/Samples/Marbles/<path-to-file.usd>" \
  -o "$USD_ASSET_ROOT/NVIDIA_Samples/Marbles/<path-to-file.usd>"

Useful prefixes:

Prefix	Size	Notes
`Samples/Marbles/`	4.5 GB, 3,892 files	Excellent stress test; root prim is `/stage`
`Samples/OldAttic/`	1.5 GB, 929 files	Good composed scene for demo work
`Samples/Showcases/`	14.7 GB, 1,462 files	Larger RTX showcase scenes
`Samples/Examples/`	29 GB, 11K files	Broad sample corpus
`Samples/Flight/`	4.3 GB	Flight-themed scene content
`Samples/Astronaut/` and `Samples/EuclidVR/`	1.5 GB combined	Character/VR-oriented samples

Sync a Selective Prefix

export USD_ASSET_ROOT="${USD_ASSET_ROOT:-/path/to/usd-assets}"
mkdir -p "$USD_ASSET_ROOT/NVIDIA_Samples/OldAttic"

aws s3 sync --no-sign-request \
  "s3://omniverse-content-production/Samples/OldAttic/" \
  "$USD_ASSET_ROOT/NVIDIA_Samples/OldAttic/"

To inspect a prefix before downloading:

aws s3 ls --no-sign-request "s3://omniverse-content-production/Samples/Marbles/" --recursive --human-readable --summarize

For a subset, start from the root .usd and include every referenced layer, texture, MDL, and material file. If any dependency is missing, the Omniverse Realtime Viewer may load a gray or partial scene. Full prefix sync is usually faster than debugging broken relative references for large NVIDIA samples.

External USD Sources

Source	URL	Use
USD Working Group assets	`https://github.com/usd-wg/assets`	30+ PBR test assets with variants, skeletons, and material coverage
StandardShaderBall live asset	`https://prefrontalcortex.github.io/usd-wg-assets/full_assets/StandardShaderBall/layers/shaderball/`	Quick shader/material smoke test
OpenUSD samples	`https://openusd.org/release/dl_downloads.html`	Kitchen Set, City Set, and UsdSkel examples; accept the displayed license before download
ALab / DPEL	`https://dpel.aswf.io/` and `https://github.com/DigitalProductionExampleLibrary/ALab`	Full production USD scene with characters; large download and registration/download-page flow may apply
Intel 4004 Moore Lane	`https://dpel.aswf.io/4004-moore-lane/`	House interior/exterior for ray-tracing tests; direct package is `https://dpel-assets.aswf.io/4004-moore-lane/intel_moorelane_v1_2_0.zip`
DPEL OpenPBR Shader Playground	`https://github.com/DigitalProductionExampleLibrary/OpenPBRShaderPlayground`	MaterialX/OpenPBR/USD material testing
Moana Island Scene	`https://www.disneyanimation.com/resources/moana-island-scene/`	Production-scale island scene; use the USD package for USD testing

Clone usd-wg/assets:

export USD_ASSET_ROOT="${USD_ASSET_ROOT:-/path/to/usd-assets}"
mkdir -p "$USD_ASSET_ROOT"
git clone https://github.com/usd-wg/assets.git "$USD_ASSET_ROOT/usd-wg-assets"
find "$USD_ASSET_ROOT/usd-wg-assets" -iname "*.usd" -o -iname "*.usda" -o -iname "*.usdc"

Download Intel 4004 Moore Lane:

export USD_ASSET_ROOT="${USD_ASSET_ROOT:-/path/to/usd-assets}"
mkdir -p "$USD_ASSET_ROOT/downloads" "$USD_ASSET_ROOT/Intel_4004_Moore_Lane"

curl -L -C - \
  "https://dpel-assets.aswf.io/4004-moore-lane/intel_moorelane_v1_2_0.zip" \
  -o "$USD_ASSET_ROOT/downloads/intel_moorelane_v1_2_0.zip"

unzip -q "$USD_ASSET_ROOT/downloads/intel_moorelane_v1_2_0.zip" \
  -d "$USD_ASSET_ROOT/Intel_4004_Moore_Lane"

Clone OpenPBR Shader Playground:

export USD_ASSET_ROOT="${USD_ASSET_ROOT:-/path/to/usd-assets}"
git clone https://github.com/DigitalProductionExampleLibrary/OpenPBRShaderPlayground.git \
  "$USD_ASSET_ROOT/OpenPBRShaderPlayground"

Quality Tiers

Tier	Recommendations
Quick start	bundled `stage01` / `stage02`, Scene Templates pack, `usd-wg/assets` StandardShaderBall
Demo-quality	Marbles subset with dependencies, OldAttic, Kitchen Set
Stress test	full Marbles, Showcase Scenes, full Sample Scenes pack
Production-scale	full Sample Scenes, ALab, Moana

Quick-start zip sizes can exceed the tier name. Choose by stage complexity and load time, not only archive size.

Directory Layout

Keep each source unpacked under one stable root:

/path/to/usd-assets/
  Scene_Templates/
  NVIDIA_Samples/
    Marbles/
    OldAttic/
  usd-wg-assets/
  Intel_4004_Moore_Lane/

Do not flatten directories. USD layers, textures, MDL files, and payloads often use relative paths.

Omniverse Realtime Viewer Integration Notes

Marbles uses root prim /stage; many other samples use /World. Detect the root prim dynamically and pass it through openStageResult.
The frontend openStageRequest sent on WebRTC connect can override a server-loaded stage. Match defaults on both sides or let the server's initial state be authoritative.
Large scenes over 1 GB need async stage loading, progress/error state, and skip-reload logic for the currently loaded normalized path.
First load with new MDL/materials can spend several minutes compiling shaders. A 4 minute first load is plausible for Marbles-class content.
Keep sample stages on a fast local disk. Use /path/to/usd-assets/<PackName>/ or a configurable USD_ASSET_ROOT.
Never substitute a browser 3D renderer for large or unsupported samples. The Omniverse Realtime Viewer still uses server-side ovrtx; the browser only displays the WebRTC video stream.
After any stage switch, rebuild hierarchy, native pickability state, selection state, and native selection outline groups.

Sample Data Directory Layout For Deployment

The download script (or zip extraction) places samples in samples/samples_data/. However, the server expects samples_data/ as a sibling directory (not nested under samples/). The _ovrtx_composite_*.usda files reference stage USD files by relative path (e.g., ./stage01.usd), so the composite and the referenced stage USD must be in the same directory.

Correct layout for the server:

/app/samples_data/
  stage01.usd
  stage02.usd
  _ovrtx_composite_stage01.usda
  _ovrtx_composite_stage02.usda
  materials/
  textures/

Incorrect (nested) layout that breaks relative references:

/app/samples/samples_data/    ← extra nesting breaks relative paths
  stage01.usd
  ...

When deploying, ensure you copy or symlink the samples_data/ contents to the path the server's --stage argument expects. For Docker images, COPY samples_data/ /app/samples_data/ is sufficient if the build context has the correct flat structure.

See also: huggingface-usd, usd-viewer-app, stage-management, stage-loading, cloud-assets, render-settings, streaming-server, streaming-client.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python, Needs Node.js

The author says: Orchestrator skill. Downstream focused references may require NVIDIA GPUs, ovrtx, ovstream, ovui, OpenUSD, Python, Node/React, Tauri, Electron, C++, or cloud GPU deployment access depending on the selected viewer path.

Security

What our scanner noticed· Medium risk

Large base64-encoded blobs
Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by

NVIDIA Omniverse

Publisher

NVIDIA (Official)

Source

NVIDIA/skills · skills/omniverse-realtime-viewer · commit fce3cca

Licence

Apache License 2.0 (redistribution allowed)

LICENSE (added by AutoGineer from LICENSE-APACHE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-08

AutoGineer is not affiliated with or endorsed by NVIDIA Omniverse or NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download omniverse-realtime-viewer.zip

From the author

AutoGineer summary

What it does

When to use it

Advantages

Usage examples

Install

Documentation by NVIDIA Omniverse

Omniverse Realtime Viewer

Start With The App

Architecture

Add Capabilities As Needed

Solid Modeling: Upstream First

GPU Processing And Stylized Viewers

XR Viewers

Files

references/usd-sample-data/README.md

USD Sample Data

Triggers

Fast Choices

Official USD Viewer Sample Stages (stage01 / stage02)

NVIDIA Omniverse Downloadable Packs

Download a CloudFront Pack

NVIDIA Public S3 Bucket

Sync a Selective Prefix

External USD Sources

Quality Tiers

Directory Layout

Omniverse Realtime Viewer Integration Notes

Sample Data Directory Layout For Deployment

Requirements and compatibility

Security

Attribution and licence

Related skills

Setup TS Deep Modules

To Spec

Improve Codebase Architecture

Domain Modeling

Codebase Design

Prototype

Download ZIP