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

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/routing.md

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

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

Omniverse Realtime Viewer Routing

Use this reference to route plain-language viewer requests into focused references. This routing reference is self-contained; focused references live in sibling directories under this references/ directory.

Architectural Constraint

All USD and 3D rendering must use ovrtx, NVIDIA's RTX renderer.

The pattern is always:

  • Server-side: Python or native process owns ovrtx.Renderer plus OpenUSD stage access, then renders frames on the GPU.

  • Browser delivery: ovstream WebRTC streams rendered frames to a browser. The browser displays video plus UI overlays.

  • Desktop delivery: ovui native windows, Tauri WebViews, C++ windows, or Electron SHM pixel transport display ovrtx rendered frames.

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

How To Use These Skills

When a user describes an Omniverse Realtime Viewer:

  1. Route by user intent first.

  2. Read usd-viewer-app/README.md for broad viewer requests.

  3. Add focused references for requested capabilities.

  4. Follow each selected reference's implementation notes and gotchas.

  5. Capture validation and review evidence before considering the generated app ready to share.

Intent-Based Routing

User says...Read these references
"I want to visualize USD files" / "build an Omniverse Realtime Viewer" / "3D viewport"usd-viewer-app/README.md first
"simple interactive viewport"ovui-local-viewer-recipe/README.md, then local-viewer/README.md, ovrtx-rendering/README.md, stage-loading/README.md, viewer-input-routing/README.md, camera-controls/README.md; add viewer-control-patterns/README.md if the app has toolbar, sidebar, or settings controls
"native desktop app with React UI" / "Tauri viewer" / "Rust OVRTX"tauri-local-viewer/README.md, ovrtx-rendering/README.md
"C++ viewer" / "native desktop" / "ImGui viewer" / "GLFW viewer"cpp-native-viewer/README.md; add viewer-control-patterns/README.md for Dear ImGui controls, toolbars, settings, or dialogs
"Electron app" / "Electron viewer" / "SHM viewer" / "shared memory viewer"electron-shm-viewer/README.md
"headless automation" / "scripted testing" / "CLI tool" / "SHM automation"headless-shm-cli/README.md
"local separate-process viewer" / "process-isolated local viewer"electron-shm-viewer/README.md
"reusable UI" / "ViewerBackend" / "shared components" / "cross-transport UI"viewer-backend-interface/README.md
"viewer UI" / "frontend UI" / "UX" / "app layout" / "redesign" / "panels" / "toolbar" / "ovui UI" / "ImGui UI"viewer-ux-workflow/README.md, then focused viewer UI references
"viewport layout" / "outliner and properties" / "drawer" / "anchored inspector" / "responsive layout"viewer-layout-patterns/README.md
"buttons" / "actions" / "forms" / "controls" / "sliders" / "confirmations"viewer-control-patterns/README.md
"stage tree UI" / "asset grid" / "property inspector UI" / "JSON tree"viewer-data-view-patterns/README.md
"loading state" / "error banner" / "stream health" / "offline" / "lagged" / "status UI"viewer-feedback-status/README.md
"stream to a browser" / "browser Omniverse Realtime Viewer"streaming-viewer-recipe/README.md, then streaming-server/README.md, streaming-client/README.md, streaming-messages/README.md, streaming-lifecycle/README.md, viewer-input-routing/README.md
"pick objects" / "click to select"viewer-input-routing/README.md, native-picking-selection/README.md, object-selection/README.md, selection-feedback/README.md
"when picked, change a material/visibility/effect attribute"prim-pick-effects/README.md, plus object-selection/README.md
"see info/properties for highlighted objects"prim-info-display/README.md, stage-attribute-reads/README.md, stage-hierarchy/README.md
"highlight selected objects"selection-feedback/README.md, native-picking-selection/README.md
"custom segmentation-buffer outline overlay"seg-outline-highlight/README.md
"animate selected objects"selection-animation/README.md
"move/rotate/scale selected objects" / "transform gizmo" / "manipulator"transform-manipulator/README.md, plus prim-transform-safety/README.md
"Tauri SHM transform gizmo" / "client-side gizmo overlay"tauri-shm-transform-gizmo/README.md, plus tauri-local-viewer/README.md and webgl-shm-transport/README.md
"C++ viewport overlay" / "C++ gizmo" / "GL gizmo"gl-viewport-overlay/README.md, ovui-library/README.md, plus cpp-native-viewer/README.md
"switch scenes" / "load different USD files" / "asset browser"stage-management/README.md, stage-loading/README.md
"rendering settings" / "lighting" / "quality controls"render-settings/README.md, viewer-control-patterns/README.md
"switch AOVs" / "view normals" / "segmentation render output"aov-switching/README.md, ovrtx-rendering/README.md, streaming-messages/README.md
"settings persist across scenes"stage-management/README.md, render-settings/README.md, viewer-control-patterns/README.md
"scene tree" / "hierarchy" / "variants"stage-hierarchy/README.md
"viewport overlays" / "camera gizmo" / "floating panel"viewport-overlays/README.md, plus camera-controls/README.md or prim-info-display/README.md
"load from S3/MinIO/cloud assets"cloud-assets/README.md
"browse assets with thumbnails"cloud-assets/README.md
"deploy with cloud sessions"cloud-deployment/README.md
"physics simulation" / "drop test" / "physics grab"Clone ovphysx and check its skills/
"import CAD files" / "convert STEP/IGES to USD"Clone cad2usd and check its skills/
"native Windows setup"windows-native-setup/README.md
"full editor with docking/property inspector"streaming-vs-local/README.md first; use ovwidgets-editor-shell/README.md for the full editor path, plus viewer-control-patterns/README.md and viewer-data-view-patterns/README.md for editor controls and panels

Target prompt routing:

I want to visualize USD files in a simple interactive viewport, I want to pick
objects and see information about the objects highlighted, and I want to easily
switch between different USD scenes and have some basic rendering and lighting
settings that persist across scenes.

Read: usd-viewer-app/README.md, ovui-local-viewer-recipe/README.md, local-viewer/README.md, ovrtx-rendering/README.md, stage-loading/README.md, viewer-input-routing/README.md, camera-controls/README.md, native-picking-selection/README.md, object-selection/README.md, selection-feedback/README.md, prim-info-display/README.md, stage-attribute-reads/README.md, stage-management/README.md, render-settings/README.md, viewer-control-patterns/README.md, and stage-hierarchy/README.md.

Capability-Based Routing

CapabilitySkills to read
High-level Omniverse Realtime Viewer recipeusd-viewer-app/README.md
Core ovrtx renderer construction/step/write APIsovrtx-rendering/README.md
Camera/render product/render var/session stage setupstage-loading/README.md
Local desktop end-to-end recipeovui-local-viewer-recipe/README.md; add viewer-control-patterns/README.md for toolbars, forms, render settings, or other user-facing controls
Local desktop lightweight ovui shelllocal-viewer/README.md; add viewer-control-patterns/README.md for header, sidebar, toolbar, or inline controls
Tauri/Rust native desktop with React WebViewtauri-local-viewer/README.md
Native C++ OVRTX viewer with ImGui/GLFWcpp-native-viewer/README.md; add viewer-control-patterns/README.md for Dear ImGui controls
Electron plus SHM local separate-process viewerelectron-shm-viewer/README.md, webgl-shm-transport/README.md
Headless SHM automation and testingheadless-shm-cli/README.md
ViewerBackend interface and shared React componentsviewer-backend-interface/README.md
SharedArrayBuffer to WebGL pixel transportwebgl-shm-transport/README.md
Interactive translate/rotate/scale manipulatorstransform-manipulator/README.md, prim-transform-safety/README.md
Client-rendered transform gizmo for Tauri SHMtauri-shm-transform-gizmo/README.md
C++ GL viewport overlays and reusable gizmo mathgl-viewport-overlay/README.md, ovui-library/README.md
Viewer UI intent routing and UX workflowviewer-ux-workflow/README.md
Viewport-dominant layout, panels, drawers, responsive shellviewer-layout-patterns/README.md
Toolbars, forms, sliders, semantic actions, confirmationsviewer-control-patterns/README.md
Stage tree, asset browser, property inspector, JSON data viewsviewer-data-view-patterns/README.md
Loading, errors, stream health, lagged/offline statusviewer-feedback-status/README.md
Full editor shellstreaming-vs-local/README.md, ovwidgets-editor-shell/README.md, viewer-control-patterns/README.md, viewer-data-view-patterns/README.md
Streaming architecture decisionstreaming-vs-local/README.md
Browser-streamed end-to-end recipestreaming-viewer-recipe/README.md
WebRTC/RTSP server and CUDA frame streamingstreaming-server/README.md
React/AppStreamer browser client for standalone ovstream Direct modestreaming-client/README.md
Streaming JSON data-channel protocolstreaming-messages/README.md
Stream callback/data-channel lifecyclestreaming-lifecycle/README.md
Viewer input routing / WebRTC input / click-vs-drag / viewport input ownershipviewer-input-routing/README.md
Orbit/pan/zoom/camera fitting/gizmoviewer-input-routing/README.md, camera-controls/README.md
Object picking/selectionviewer-input-routing/README.md, native-picking-selection/README.md, object-selection/README.md
Selection glow/highlightselection-feedback/README.md, native-picking-selection/README.md
Custom segmentation-buffer post-process overlaysseg-outline-highlight/README.md
Transform-safe live prim manipulationprim-transform-safety/README.md, ovrtx-rendering/README.md
Selection hover/motion animationselection-animation/README.md
Selected prim info/properties displayprim-info-display/README.md, stage-attribute-reads/README.md
Scene switching/reload/persistent statestage-management/README.md
Render quality/render vars/lighting/settingsrender-settings/README.md, viewer-control-patterns/README.md
Browser AOV/render-var switchingaov-switching/README.md, ovrtx-rendering/README.md, streaming-messages/README.md
Server-side ovui overlaysviewport-overlays/README.md
USD hierarchy/properties/variants/boundsstage-hierarchy/README.md
Native prim discovery/filteringstage-queries/README.md
Native scalar/array attribute readsstage-attribute-reads/README.md
Pick-driven USD attribute effectsprim-pick-effects/README.md
S3/MinIO asset loading and browsingcloud-assets/README.md
Physics simulationClone ovphysx, use its skills
CAD-to-USD conversionClone cad2usd, use its skills
Native Windows setupwindows-native-setup/README.md

Decision Tree

User prompt received
|
+- High-level app request? ("build an Omniverse Realtime Viewer", "visualize USD files")
|  +- READ: usd-viewer-app/README.md
|
+- Delivery method?
|  +- Browser/web -> READ: streaming-viewer-recipe + streaming-server + streaming-client + streaming-messages + streaming-lifecycle
|  +- Desktop/local (React UI, no Python) -> READ: tauri-local-viewer
|  +- Desktop/local (C++, ImGui, no Python/Rust) -> READ: cpp-native-viewer + viewer-control-patterns
|  +- Desktop/local (React UI, Python server, separate process) -> READ: electron-shm-viewer
|  +- Desktop/local (Python, simple) -> READ: ovui-local-viewer-recipe + local-viewer + ovrtx-rendering + stage-loading; add viewer-control-patterns when controls are visible
|  +- Desktop/local (Python, full editor) -> READ: streaming-vs-local + ovwidgets-editor-shell + viewer-control-patterns
|  +- Both/unsure -> READ: streaming-vs-local first
|
+- Viewer/UI work?
|  +- Broad UI/layout prompt -> READ: viewer-ux-workflow
|  +- Panels/drawers/responsive shell -> READ: viewer-layout-patterns
|  +- Toolbars/forms/actions/sliders/confirmations -> READ: viewer-control-patterns
|  +- Trees/asset grids/property inspectors -> READ: viewer-data-view-patterns
|  +- Loading/errors/stream status -> READ: viewer-feedback-status
|
+- Specific feature?
|  +- Object picking -> READ: viewer-input-routing + native-picking-selection + object-selection + selection-feedback
|  +- Pick changes a USD/material attribute -> READ: prim-pick-effects + object-selection
|  +- Object info panel -> READ: prim-info-display + stage-attribute-reads + stage-hierarchy
|  +- Camera navigation -> READ: viewer-input-routing + camera-controls
|  +- Transform gizmo/manipulator -> READ: transform-manipulator + prim-transform-safety
|  +- Tauri SHM client-rendered gizmo -> READ: tauri-shm-transform-gizmo + tauri-local-viewer + webgl-shm-transport
|  +- C++ GL viewport overlay/gizmo -> READ: gl-viewport-overlay + ovui-library + cpp-native-viewer
|  +- Scene switching -> READ: stage-management
|  +- Render quality/lighting -> READ: render-settings
|  +- AOV/render-var switching -> READ: aov-switching + ovrtx-rendering + streaming-messages
|  +- Viewport overlays -> READ: viewport-overlays
|  +- Animation -> READ: selection-animation
|  +- Custom messages -> READ: streaming-messages
|
+- Infrastructure?
|  +- Cloud assets -> READ: cloud-assets
|  +- Cloud deployment -> READ: cloud-deployment
|  +- Physics simulation -> Clone ovphysx, read its skills/
|  +- CAD file import -> Clone cad2usd, read its skills/
|  +- Windows -> READ: windows-native-setup
|
+- USD stage work?
   +- Loading scenes -> READ: stage-loading
   +- Hierarchy/queries -> READ: stage-hierarchy
   +- Native prim filters -> READ: stage-queries
   +- Native attribute values -> READ: stage-attribute-reads

Dependencies Model

When a selected reference tells you to install or configure a dependency, read dependencies/README.md first. It is the source of truth for the four primary NVIDIA dependencies: ovrtx, ovui, ovstream, and the ov-web-rtc browser client.

LibraryInstall methodNotes
ovrtxSee dependencies/nvidia-runtime.mdRTX USD renderer; RTX GPU required
ovstreamSee dependencies/nvidia-runtime.mdStreaming runtime
ov-web-rtc client / @nvidia/ov-web-rtcSee dependencies/nvidia-runtime.mdBrowser AppStreamer client for standalone ovstream Direct mode; do not use alternate package names, hard-coded client versions, or Kit/OVC/NVCF/GFN client connection profiles
ovuiSee dependencies/nvidia-runtime.mdNative UI toolkit
ovui-data-adaptersInstall from the same ovui package setLocal UI adapter contracts
Full editor UI packageInstall only when current ovui dependency guidance explicitly requires it, from the same ovui package setFull editor widgets
ovstorageInstall with the selected project manifest or pip install ovstorageCloud asset browsing and cache sync
ovphysxpip install ovphysx -i https://pypi.nvidia.comPhysics simulation; check external skills
cad2usdExternal checkoutCAD file conversion to USD
pxr / OpenUSDpip install usd-coreUse version pins from platform skills
numpypip install numpyArray operations
warppip install warp-langGPU kernels and CUDA buffer utilities

Supplemental Guidance

Use the selected references as the implementation contract. When a dependency reference provides supplemental documentation, use it to clarify API behavior without changing the selected viewer architecture.

ovui guidance     -> local UI package setup, widgets, overlays, and native UI conventions
ovstream guidance -> streaming runtime setup, SHM behavior, native input, lifecycle, and the ovstream repo's own skills/samples
ovrtx guidance    -> renderer setup, Python/C API behavior, AOVs, picking, and selection
ovstorage guidance -> resolver and asset management patterns
Clone ovphysx    -> check ovphysx/skills/    -> physics simulation, collider cooking, grab, drop
Clone cad2usd    -> check cad2usd/skills/    -> CAD conversion and batch processing

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