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://mp-staging.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/ovui-local-viewer-recipe/validation-build-order.md

ovui Local Validation And Build Order

13. Validate The Omniverse Realtime Viewer

Validate in this order:

  1. Compile or import-check the local app package.

  2. Launch with a real display and confirm the ovui window opens at the requested size.

  3. Confirm the main window resizes and the viewport image frame tracks the window dimensions.

  4. Push a synthetic RGBA gradient through the selected ovui image provider and capture a desktop screenshot proving native presentation works before any renderer debugging.

  5. Load a simple sample scene and save a direct ovrtx LdrColor artifact from the same render product and render var used by the viewport.

  6. Capture a desktop screenshot of the ovui window showing that rendered frame.

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

  8. Confirm the scene was not modified and no viewer lights were injected unless requested.

  9. Confirm camera orbit, pan, right-drag dolly, wheel zoom, and fit-to-stage update the rendered view.

  10. Confirm left-click selection does not fire after an orbit drag.

  11. Confirm viewport picking uses the visible image rect and remains accurate after resize.

  12. Confirm selected prim state appears in the tree and info panel.

  13. Confirm hierarchy expansion, properties, and variants display the current selected prim only.

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

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

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

  17. Confirm selection outline groups are cleared on every stage load when selection feedback is enabled.

  18. If a selected-prim transform gizmo is present, confirm dragging it changes a known prim's live omni:xform by a measured delta and the highlight/info panel follow the moved prim.

  19. Confirm the app shuts down without leaving a stale Python GPU process.

Use these failure checks:

  • Window opens but content does not resize: verify the ovui window fills the app window and viewport widgets use flexible sizing.

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

  • Direct LdrColor artifact is nonblank but the window is blank: verify ovui presentation with the synthetic frame and switch to a known-good ovui-native presentation path if needed.

  • Magenta materials: verify OVRTX_BIN_PATH and plugin library path.

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

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

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

  • Gizmo appears but prim does not move: verify the gizmo gets mouse-down priority before camera/orbit, drag release does not enqueue a pick, and drag deltas call renderer.write_attribute on omni:xform with the selected prim path.

  • OPEN button does nothing or fails inconsistently: remove or demote the dialog control until it is validated; keep the path-field LOAD path as the primary stage-loading control.

  • Tree or info panel shows stale data: verify cache invalidation after scene switch, variant change, and selection clear.

  • UI freezes on large scenes: verify hierarchy traversal is lazy or moved off the UI path.

Read for depth: see references/local-viewer, references/stage-loading, references/viewer-input-routing, references/camera-controls, references/object-selection, references/stage-hierarchy, references/render-settings, and references/stage-management 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. Build app config, runtime state, ovui lifecycle, and a resizable empty viewport shell.

  3. Add ovrtx renderer construction and a single hard-coded sample scene load.

  4. Add a synthetic ovui presentation smoke test and capture the first nonblank window screenshot.

  5. Add inline root/session setup with LdrColor, save a direct frame artifact, and confirm one displayed frame in the ovui window.

  6. Add continuous frame stepping and stable ImageBridge updates.

  7. Add letterbox math, normalized input routing, and a transparent viewport hit surface.

  8. Add camera orbit, pan, zoom, wheel zoom, and fit-to-stage.

  9. Add scene registry, scene picker, reload, and serialized scene switching.

  10. Add hierarchy and properties queries.

  11. Add tree-driven selection, then viewport picking.

  12. Add native selection outline feedback and prim info display.

  13. Add selected-prim transform gizmo behavior only after selection and live transform writes are proven.

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

  15. Run the validation checklist and fix failures before adding optional overlays, cloud assets, or editor-style widgets.

Do not skip the displayed-frame milestone. If the first implementation includes every feature before ovrtx image display is proven, failures become hard to isolate.

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