domains / families / design / omniverse-realtime-viewer

omniverse-realtime-viewer

separate

Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.

When to use

• Omniverse Realtime Viewer USD app requests
• focused viewer reference documents
• choosing delivery path and focused references
• implementing render path, interaction, and UI behavior
• capturing validation evidence

When not to use

• substituting WebGL, Three.js, Babylon.js, PlayCanvas, A-Frame, model-viewer, react-three-fiber, glTF browser viewers, or other client-side 3D renderers
• adding a browser-renderer fallback when local validation cannot run

Skill page

Source