AutoGineer
Generated banner for Omniverse Realtime Viewer
Generated logo for Omniverse Realtime Viewer

Omniverse Realtime Viewer

OpenAIOfficialCreated by NVIDIA OmniverseDistributed by OpenAI

  • Skill
  • Meta (authoring, orchestration, planning, memory)
  • Software development
  • Apache-2.0
  • Medium risk
Download ZIP

From the author

Use as the top-level router for Omniverse Realtime Viewer USD app requests 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 orchestrator for developing USD-based viewer applications. It provides a structured approach to selecting implementation recipes, enforcing architectural conventions, and managing dependencies. By utilizing a set of focused reference documents, it guides developers through the lifecycle of building, configuring, and validating viewer applications, ensuring consistent behavior across different delivery paths such as local workstations or streaming environments.

What it does

  • Routes development requests to specific implementation recipes based on the target delivery path.
  • Enforces architectural rules for USD rendering, stage management, and UI integration.
  • Provides guidance on camera selection, input handling, and viewport interaction.
  • Standardizes the integration of AOV switching and render product configuration.
  • Facilitates the capture of validation evidence for viewer readiness.
  • Maintains separation between user-provided USD files and application-specific session state.

When to use it

  • When initiating the development of a new USD viewer application within the Omniverse ecosystem.
  • When determining the appropriate delivery path for a viewer, such as local native or streaming.
  • When needing to implement consistent camera, selection, or UI behavior across viewer projects.
  • When integrating advanced rendering features like AOV switching into an existing viewer.

Advantages

  • Ensures architectural consistency across diverse viewer implementations.
  • Provides a clear, modular path for adding specific capabilities like input routing or data display.
  • Promotes clean separation of concerns between stage data and viewer-owned state.
  • Standardizes the validation process for consistent delivery.

Usage examples

“I need to build a browser-based viewer for USD files.”
The agent will route you to the streaming viewer recipe, providing guidance on WebRTC stream setup, UI integration, and viewport interaction.
“How do I implement AOV switching in my local USD viewer?”
The agent will provide the AOV switching reference, detailing how to map render vars and update the display state on the server.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/openai/omniverse-realtime-viewer/download

  2. 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

<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->

<!-- SPDX-License-Identifier: Apache-2.0 -->

Omniverse Realtime Viewer

This is the top-level entry point for the Omniverse Realtime Viewer skill package. It is self-contained: all required routing, conventions, and validation guidance live in the selected references.

Use the focused reference documents as implementation recipes. This file chooses the right recipes and preserves the architectural rules that must hold across all generated viewer apps.

Instructions

Start by classifying the requested viewer, then read only the references needed for that delivery path and feature set. Implement the render path first, layer interaction and UI behavior on top of it, and finish by capturing validation evidence from references/validation.md.

Read Order

  1. Read references/routing.md to choose the delivery path and focused references.

  2. Read references/conventions.md before implementing camera, input, selection, viewport, streaming protocol, scene loading, or environment behavior.

  3. For broad viewer requests, read references/usd-viewer-app/README.md.

  4. If the delivery path is unclear, read references/streaming-vs-local/README.md.

  5. If the prompt includes layout, panels, controls, inspectors, status, or UX, read references/viewer-ux-workflow/README.md and then the focused viewer UI references. This applies to React/WebRTC, Tauri, Electron, ovui, ovwidgets, and Dear ImGui apps; "frontend" means user-facing UI, not only browser UI.

  6. For viewport interaction, read references/viewer-input-routing/README.md before references/camera-controls/README.md, references/native-picking-selection/README.md, or references/object-selection/README.md.

  7. Read only the focused capability references needed for the requested app.

  8. Use references/validation.md to capture review evidence before handoff.

Non-Negotiables

  • Use ovrtx for all USD and 3D rendering.

  • Browser apps display an ovstream WebRTC video stream plus UI. The browser does not render USD geometry.

  • Do not substitute WebGL, Three.js, Babylon.js, PlayCanvas, A-Frame, model-viewer, react-three-fiber, glTF browser viewers, or other client-side 3D renderers.

  • If local validation cannot run because the GPU/runtime environment is absent, scaffold the ovrtx path and document the runtime requirement. Do not add a browser-renderer fallback.

  • Keep user USD files unmodified. Viewer cameras, render products, render vars, settings, selection metadata, and runtime state belong in session/composite layers or app state.

  • Keep one owner for renderer.step(), stage mutation, native picking, selection writes, and live attribute writes.

  • Keep dependency acquisition in references/dependencies/README.md and deployment choices in references/cloud-deployment/README.md; do not duplicate package locations or deployment setup.

Focused Reference Families

  • Entry points and recipes: references/usd-viewer-app/README.md, references/streaming-viewer-recipe/README.md, references/ovui-local-viewer-recipe/README.md, references/streaming-vs-local/README.md, references/electron-shm-viewer/README.md, references/ovwidgets-editor-shell/README.md.

  • Rendering and stage: references/ovrtx-rendering/README.md, references/stage-loading/README.md, references/stage-management/README.md, references/render-settings/README.md, references/aov-switching/README.md, references/stage-hierarchy/README.md, references/stage-queries/README.md, references/stage-attribute-reads/README.md, references/prim-transform-safety/README.md, references/usd-sample-data/README.md.

  • Delivery and runtime: references/streaming-server/README.md, references/streaming-client/README.md, references/streaming-messages/README.md, references/streaming-lifecycle/README.md, references/local-viewer/README.md, references/tauri-local-viewer/README.md, references/cpp-native-viewer/README.md, references/headless-shm-cli/README.md, references/viewer-backend-interface/README.md, references/webgl-shm-transport/README.md.

  • Viewer UI/UX: references/viewer-ux-workflow/README.md, references/viewer-layout-patterns/README.md, references/viewer-control-patterns/README.md, references/viewer-data-view-patterns/README.md, references/viewer-feedback-status/README.md.

  • Interaction: references/viewer-input-routing/README.md, references/camera-controls/README.md, references/object-selection/README.md, references/native-picking-selection/README.md, references/selection-feedback/README.md, references/selection-animation/README.md, references/transform-manipulator/README.md, references/gl-viewport-overlay/README.md, references/ovui-library/README.md, references/prim-pick-effects/README.md, references/prim-info-display/README.md, references/viewport-overlays/README.md.

  • Infrastructure: references/dependencies/README.md, references/windows-native-setup/README.md, references/cloud-assets/README.md, references/cloud-deployment/README.md, references/troubleshooting/README.md.

Build Workflow

  1. Classify the prompt by delivery path, target user, required capabilities, runtime environment, validation needs, and explicit constraints.

  2. Select a small reference set. Start with the recipe or routing reference, then add focused capabilities such as camera, picking, hierarchy, properties, render settings, transform tools, cloud assets, or deployment.

  3. Read selected references before writing app code. Follow their build order, import order, data-channel contracts, and renderer ownership rules.

  4. Implement the core render path first, then input routing and camera, then selection and data panels, then scene/settings features, then packaging or deployment.

  5. Treat the selected references as the behavior contract for API shape, compatibility, and generated project structure.

  6. Capture validation evidence before calling the viewer ready.

Examples

  • For a browser viewer request, use the streaming recipe references plus camera, picking, hierarchy, properties, render settings, and stream-status references.

  • For a local workstation viewer request, use the local or native delivery references plus renderer setup, stage loading, viewport input, and validation.

Completion Checklist

  • Selected references match the user's intent and delivery path.

  • No code path uses a browser-side 3D renderer for USD.

  • The generated app has one clear owner for render stepping and stage mutation.

  • User USD files remain untouched by viewer-owned session data.

  • Camera, input, selection, scene loading, and stream behavior follow references/conventions.md.

  • Setup/build/run results and visual interaction evidence are captured with references/validation.md.

Files

references/streaming-viewer-recipe/validation-build-order.md

Streaming Validation And Build Order

15. Validate The Omniverse Realtime Viewer

Validate in this order:

  1. Run the generated server setup wrapper or equivalent commands and record dependency installation results.

  2. Confirm ovrtx imports, constructs a renderer on the target GPU, and reports a usable version.

  3. Confirm ovstream.initialize() and ovstream.shutdown() complete in the generated server environment.

  4. Confirm warp initializes when CUDA conversion is enabled, and confirm the selected pxr subprocess path if USD queries are generated.

  5. Start the server with no client and confirm it initializes ovstream, constructs ovrtx, loads or waits for a scene, and exits cleanly on interrupt.

  6. Wait for /healthz to return 200 ok, or capture the server log and failing readiness command.

  7. Confirm the server logs the first valid converted frame, for example First BGRA frame ready: 1280x720.

  8. Start the frontend and confirm the browser connects to the signaling port.

  9. Confirm video appears and continues updating.

  10. Confirm colors are correct with a scene containing obvious red and blue objects.

  11. Confirm openStageRequest loads a scene and returns openStageResult.

  12. Confirm initial-state push works by loading a scene before connecting the browser, then refreshing the browser.

  13. Confirm server logs do not show immediate connected=True then connected=False loops after normal app messages arrive.

  14. Confirm camera orbit, pan, zoom, wheel zoom, and fit-to-stage update the streamed view.

  15. Confirm click selection does not fire after a drag gesture.

  16. Confirm selected prim state appears in the tree and info panel through stageSelectionChanged.

  17. Confirm getChildrenRequest, getPropertiesRequest, and getVariantsRequest responses include the requested prim path and render in the correct UI row/panel.

  18. Confirm scene switching clears stale selection, refreshes hierarchy, preserves render settings, and avoids concurrent render/reset.

  19. Confirm every visible render setting has validation evidence: before/after pixels, backend state proof, ovrtx docs/sample-backed API proof, wrapper diff plus explicit reload, or unsupported-key rejection.

  20. Confirm setRenderSettingRequest rejects unsupported keys and that success responses include applied, applies_at, and requires_reload.

  21. Confirm render settings persist after scene switch and server restart only for settings that were validated or accepted as non-live defaults.

  22. Confirm frontend reconnect does not flood logs or leave previous session already running loops.

  23. Confirm server shutdown calls ovstream stop, close, and shutdown.

Use these failure checks:

  • Browser connected but no video: verify the video element exists before connect, frontend did not set media port, server public IP/ICE is valid, and frames are being submitted.

  • Video has swapped colors: verify CUDA RGBA-to-BGRA conversion.

  • Black frame: verify render product path, camera path, render var source, resolution, and camera transform.

  • Scene load works once but fails after switching: verify renderer reset/load serialization, inline sublayer paths, and operation error handling.

  • Messages do nothing: verify browser envelope unwrapping, exact event_type names, data-channel readiness, and send guard.

  • Camera moves incorrectly: verify row-major camera matrix layout, world-up convention, finite state, input button mapping, viewport ownership, and letterbox transform.

  • Picking fails: verify native pick query enqueue/step/result handling, input routing, pick coordinate transform, RenderProduct GPU pinning when required by the active ovrtx build, and no picking during load/reset.

  • UI stays loading after refresh: verify server pushes initial openStageResult and root getChildrenResult after connection.

  • Render setting appears to work but image does not change: verify the control came from the backend capability list and that renderSettingsChanged.applied is true for immediate settings.

Read for depth: see references/streaming-lifecycle, references/streaming-server, references/streaming-client, references/stage-loading, references/viewer-input-routing, references/camera-controls, and references/object-selection for full debugging contracts.

Recommended Build Order For Agents

Follow this sequence when implementing from scratch:

  1. Create the project skeleton and dependency files.

  2. Create generated setup and run wrappers for the server environment.

  3. Build server config, ovstream lifecycle, and render-loop shell with no scene features.

  4. Add ovrtx renderer construction and a minimal user-provided or generated validation stage load.

  5. Add inline root/session setup with LdrColor and confirm one streamed frame path.

  6. Add CUDA RGBA-to-BGRA conversion and continuous frame streaming.

  7. Build the React streaming provider and video viewport.

  8. Connect browser to server and validate live video before adding UI panels.

  9. Add message router with envelope unwrapping and guarded sends.

  10. Add openStageRequest, loading state, and initial-state push.

  11. Add normalized input routing, camera handling, and live camera writes.

  12. Add hierarchy and properties queries.

  13. Add selection and native selection outline feedback.

  14. Add scene picker and scene switching.

  15. Add render settings capabilities, immediate apply paths, and persistence only for validated settings.

  16. Run the validation checklist and fix failures before adding deployment or optional overlays.

Do not skip the live-video milestone. If the first implementation includes every feature before video is proven, failures become hard to isolate.

Read for depth on streaming Omniverse Realtime Viewers: see references/streaming-client, references/streaming-server, references/streaming-messages, references/ovrtx-rendering, references/viewer-input-routing, and references/camera-controls.

Requirements and compatibility

Written for: OpenAI Codex

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.

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
OpenAI (Official)
Distributed by
OpenAI
Source
openai/plugins · plugins/nvidia/skills/omniverse-realtime-viewer · commit d420d13
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (written by AutoGineer)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

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

Download ZIP

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