omniverse-realtime-viewer

To route Omniverse Realtime Viewer prompts, this skill directs your requests to focused reference families such as usd-viewer-app, streaming-viewer-recipe, and local-viewer. It enforces the RTX rendering contract and consolidates delivery patterns across browser, desktop, and native UI paths.

Production-grade Omniverse viewer applications are supported across browser streaming, local desktop paths, and native UI routes. The skill provides routing guidance for camera controls, input routing, picking, AOVs, and stage management to ensure consistent end-to-end delivery.

Yes, Omniverse viewer routing enforces ovrtx-based RTX rendering across all supported deployment targets. Whether you are using browser streaming or local desktop paths, the routing mechanism validates that the RTX rendering contract is maintained consistently.

The best way to manage stage management and AOVs in a streaming Omniverse viewer is by routing prompts to the applicable focused references. This approach consolidates validation artifacts and dependencies, ensuring your implementation aligns with production-grade delivery patterns.

Validating dependencies and delivery patterns for an Omniverse local viewer is handled by routing prompts to focused references like tauri-local-viewer. The skill consolidates validation artifacts and documents dependencies to enable end-to-end, production-grade viewer implementations.

Limitations are not explicitly documented, but the routing scope covers both native UI paths and browser streaming with specific reference families. Enforcing the ovrtx-based rendering contract ensures consistent behavior, though delivery patterns and dependencies may vary between deployment targets.