NVIDIA-Omniverse
- 362 skills
- 0 followers
- last week last updated
- ▌ Caches Ddcs Deploy · nvidia-omniverse bundleDeploy DDCS as a shader cache for Kit/write-render-worker on GKE. Produces Kubernetes manifests, the Helm values override for write-render-worker (drivercachewrapper + UJITSO), and optionally runs a proof-of-life test. Use when setting up DDCS for MEGA shader caching (replacing GX cache).
- ▌ AWS Iam Vpc · nvidia-omniverse<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
- ▌ Eks Cluster · nvidia-omniverseGenerate Terraform for the EKS control plane, OIDC provider, cluster IAM role, system node group, and kubeconfig handoff. Use after aws-iam-vpc and before eks-nodes in the aws-infra workflow.
- ▌ Eks Storage · nvidia-omniverseInstall the aws-ebs-csi-driver EKS managed addon and create a default gp3 StorageClass. Use after eks-nodes and before ecr or eks-gpu-operator. Closes the gap where eks-nodes sets IMDS hop-limit=2 for the driver but nothing installs it.
- ▌ Aks Nodes · nvidia-omniverseGenerates a bash or Terraform snippet that adds additional node pools to an existing AKS cluster — GPU pool (single-zone, NV/NC SKU) and optional compute pool (for LLS streaming-proxy or other CPU-heavy workloads). Use as Stage 03 of `aks-bootstrap`, after `aks-cluster`. Trigger when the user mentions "GPU node pool", "add node pool", "compute pool", "aks-nodes", or asks "how do I add a GPU pool to AKS".
- ▌ Eks Validate · nvidia-omniverseGenerate a validation script for an AWS KAS/NVCF EKS foundation. Checks AWS account identity, VPC/subnets, EKS state and OIDC, node group composition, ECR pull permissions, optional S3 RBAC/probe, GPU Operator readiness, GPU resources, and an ephemeral CUDA smoke pod.
- ▌ Acr Mirror · nvidia-omniverseGenerates a bash script that bulk-mirrors NVCF images (and optionally helm charts) from NGC to Azure Container Registry by iterating an `image-manifest/manifest.yaml` SBOM. Resolves the NGC source path **per manifest group** from a built-in mapping table that mirrors `image-manifest/source-registry-config.yaml` (see the per-group source mapping below), overridable per-group via `streaming-env.sh`. Two emit modes — `regsync` (declarative, idempotent, parallel; preferred) or `az acr import` loop (no extra deps). Handles scalar and list tag values, skips `helm-*` keys for the image pass, and applies the `<acr>.azurecr.io/<sub-path>/<image>:<tag>` convention so NVCF helm charts (which concatenate `<registry>/<repository>/<image>`) don't render double-slash paths. Use after the `acr` foundation skill has provisioned the ACR and before `nvcf-self-managed-installation`. Trigger when the user mentions "mirror images", "populate ACR", "regsync", "az acr import", "NGC → ACR", "bulk mirror", "image-manifest sync", or "s
- ▌ Nvcf Self Managed CLI · nvidia-omniverse bundleInstall, operate, and tear down self-hosted NVIDIA Cloud Functions (NVCF) deployments with nvcf-cli. Use for control-plane or compute-plane install, status checks, cluster registration, function deploy/invoke, task create/list/cancel/delete, API keys, admin tokens, JWKS rotation, failed-install diagnosis, and uninstall or down workflows. Trigger keywords: nvcf, nvcf-cli, self-hosted nvcf, self-managed nvcf, NVCFBackend, NVCA, NCP, ICMS, helmfile, control plane, compute plane, LLM function, OpenAI-compatible invocation, Responses API, embeddings, batch task, task monitor, cluster rotate, cluster delete, helm task, helm-based task, task secrets, update task secrets, retrieve task results, bulk fetch tasks, task results.
- ▌ Orchestrate Streaming Stack · nvidia-omniverseOrchestrate an end-to-end NVIDIA self-managed streaming stack across AWS or Azure. Use when planning, generating, sequencing, deploying, or validating the full path from CSP base infrastructure through NVCF self-managed control plane, NVCF auxiliary services, caches, storage APIs, and post-deploy readiness gates. Trigger when the user asks for orchestration, full-stack setup, bring-up order, runbook, dependency sequencing, AWS/Azure streaming deployment, csp-infra plus NVCF, caches, or storage API coordination. Do not use for a single component task when the user explicitly asks only for one child skill.
- ▌ Aks Cluster · nvidia-omniverseGenerates a Terraform module (AVM resource module) that creates an AKS Standard cluster with a system node pool, AAD + Azure RBAC, OIDC issuer + workload identity, Azure CNI Overlay (Cilium NetworkPolicy), API server VNet integration, and an optional corp-egress allowlist. Does NOT create the GPU node pool — that's `aks-nodes`. Use as Stage 02 of `aks-bootstrap`, after `iam-vpc`. Trigger when the user mentions "create AKS cluster", "aks-cluster", "AKS control plane", or asks to "spin up an AKS cluster".
- ▌ Aks Validate · nvidia-omniverseGenerates a read-only validation script that confirms an AKS cluster bootstrapped via iam-vpc → aks-cluster → aks-nodes → acr → blob-storage → gpu-operator is healthy end-to-end. Checks RG, VNet, AKS provisioning state, node pool composition, ACR + AcrPull role, Storage + Blob Data Contributor role, GPU operator pods, GPU resource advertisement, a CUDA smoke pod, and a Blob auth probe. Emits PASS/WARN/FAIL plus a JSON report. Emitted as Stage 07 by `aks-bootstrap`; can be run standalone after the stack is up. Trigger when the user mentions "validate the cluster", "is the cluster ready", "smoke test the bootstrap", "kick the tires", or after any stack change.
- ▌ Blob Storage · nvidia-omniverseGenerates a bash or Terraform snippet that creates an Azure Storage Account (StorageV2, LRS, hot tier) with one or more Blob containers, and grants the AKS kubelet identity (or a workload-identity service account) `Storage Blob Data Contributor` on it. For passwordless access from cluster workloads via workload identity. Optional private endpoint for hardening. Use as Stage 05 of `aks-bootstrap`, after `aks-cluster`. Trigger when the user mentions "create storage account", "blob container", "blob storage", "Storage Blob Data Contributor", or "passwordless blob access from AKS".
- ▌ Gpu Operator · nvidia-omniverseGenerates a bash script that installs the NVIDIA GPU Operator on an existing AKS cluster via Helm, with AKS-specific values. Covers the two AKS-only gotchas the upstream docs don't surface — split NFD CRDs and the AKS-pre-installed driver. Use as Stage 06 of `aks-bootstrap`, after `aks-nodes`. Trigger when the user mentions "install GPU operator", "NVIDIA GPU operator", "DCGM", "nvidia-smi pod", or asks "how do I install the GPU operator on AKS".
- ▌ Aks Bootstrap · nvidia-omniverseOrchestrates the full mandatory AKS setup in one pass — reads iam-vpc, aks-cluster, aks-nodes, acr, blob-storage, gpu-operator, and aks-validate skills; generates a Terraform module for Stage 02 and stage-prefixed scripts for the remaining stages. Infers intent from the user prompt to either generate artifacts for review or generate-and-deploy (executes sequentially; Stage 02 runs Terraform and writes the downstream env handoff, stages 01 and 03–06 stop on failure, stage07 is tolerant and reports without failing the run). Use when setting up a new AKS cluster end-to-end. Collects all required inputs once from `streaming-env.sh`, then delegates each stage to its canonical skill. Trigger when the user says "bootstrap a cluster", "deploy AKS", "set up the cluster end-to-end", "spin up Azure base", or "run all stages".
- ▌ Eks Gpu Operator · nvidia-omniverseGenerate a Helm-based NVIDIA GPU Operator install script for EKS clusters whose GPU node group uses the AWS GPU-optimized AMI. Use after eks-nodes and before eks-validate.
- ▌ Tf Conventions · nvidia-omniverseProject-specific Terraform rules for the Azure base stack. Use when writing or reviewing Terraform code in this repo. Trigger when editing *.tf files, reviewing TF diffs, picking an AVM module, deciding on naming, or before terraform apply. Captures the AKS module choice, exact-version pinning policy, naming conventions, API server access posture, NSG hygiene, and the rules that the skills in this repo all follow.
- ▌ AWS Tf Conventions · nvidia-omniverseProject-specific Terraform rules for the AWS KAS/NVCF EKS foundation. Use when writing or reviewing AWS Terraform for VPC, EKS, node groups, IAM, ECR, state, tags, provider configuration, or before terraform apply.
- ▌ Caches Ovcontentcache Deploy · nvidia-omniverse bundleDeploy NVIDIA Omniverse Content Cache (OVCC) alongside a MEGA simulation stack. Covers evaluation, sizing (NGINX queue-depth model), configuration for GCS/S3/Azure backends, Helm install from NGC (chart ovcontentcache v4.0.4), TLS setup, in-place upgrade from UCC 3.0.3, and wiring to write-render-worker and storage-service. MEGA does not use Nucleus; always disable it. Use when deploying OVCC for MEGA — whether exploring fit, sizing replicas, or ready to install.
- ▌ Nvcf Self Managed Installation · nvidia-omniverse bundleInstall and operate NVCF self-hosted control-plane and separate compute-plane stacks. Covers Helmfile values and CLI profile installation flows, teardown, values overrides, pull secrets, and troubleshooting. Use for nvcf-self-managed-stack, nvcf-compute-plane-stack, split compute-plane installation, control-plane installation, CLI-generated control-plane profiles, Helmfile, self-managed, or self-hosted deployments. Do NOT use for local k3d environments; use the local k3d development workflow instead.
- ▌ Nvcf Self Managed Prerequisite · nvidia-omniverse bundleInstall the prerequisites the NVCA operator / compute plane needs before nvcf-nvca-install can succeed: the operator tool nvcf-cli (required by the compute-plane stack's register-cluster step), KAI Scheduler (for the KAIScheduler feature gate), and the SMB CSI driver (for the sharedStorage Samba sidecar PVCs). The two cluster components are cloud-neutral helm installs at the NVCF-validated version pins; same install on AKS, EKS, GKE, k3d, or bare metal. Use when the user mentions NVCA prereqs, nvcf-cli, "nvcf-cli not found", ensure-nvcf-cli, register-cluster, KAI Scheduler, SMB CSI, csi-driver-smb, queue quotas, default-parent-queue, NVCA shared-storage PVCs stuck Pending, or asks how to prepare a cluster before installing the NVCA operator.
- ▌ Interpreting Lidar Pointclouds · nvidia-omniverseInterpreting already-read lidar PointCloud tensors: channel meanings, units, valid point ranges, coordinate-frame implications, flags, IDs, normals, velocity, and visualization values. Use reading-sensor-pointclouds when the user needs to map or fetch the tensors first.
- ▌ Interpreting Radar Pointclouds · nvidia-omniverseInterpreting already-read radar PointCloud tensors: channel meanings, units, valid detection ranges, RCS, signed radial velocity, time offsets, flags, counts, and visualization values. Use reading-sensor-pointclouds when the user needs to map or fetch the tensors first.
- ▌ Adding Doc Snippets · nvidia-omniverseAdding new tested code snippets for documentation pages. Use when adding code examples to RST docs, creating new doc pages, or migrating inline code blocks to tested snippets.
- ▌ Ovrtx Post Cutsheet · nvidia-omniversePost-process rendered variant permutations: browse a results folder of stills/videos, burn variant-label plates onto renders (originals untouched), assemble frame sequences into MP4, and compose a labeled contact sheet ("cut sheet"). Pure PIL/OpenCV/ffmpeg, off the render thread. Use when adding a Results / labeling / contact-sheet feature to a variant presenter.
- ▌ Renderer Feature Validation Matrix · nvidia-omniverse bundleCreate and maintain renderer feature validation matrices for correctness, performance, backend parity, and test coverage. Use when Codex plans renderer milestones, delegates subagent work, compares against Kit/Hydra/reference output, or decides whether a renderer feature is implemented, degraded, missing, or untested.
- ▌ Usda Value Parser · nvidia-omniverseUse this skill when implementing or verifying USDA right-hand-side values and attribute type validation.
- ▌ Simready Addon Install And Authoring · nvidia-omniverse bundleInstall or verify the official SimReady Blender add-on, author one physics-ready prop through its real operators and properties, run available validators, export and reopen USD, and verify compatibility with the pinned public OVRTX uni-body conversion. Use for SimReady asset preparation; never substitute plain Blender custom properties or generic USD export for add-on authoring.
- ▌ Renderer Target Architecture Design · nvidia-omniverse bundleDesign renderer features from the target-quality architecture first, including radical subsystem replacement when incremental slices are exhausted. Use when Codex implements or plans path tracing, denoising, lighting, sampling, acceleration structures, scene residency, instancing, texture systems, material systems, render graphs, or major renderer features where state-of-the-art/proven production techniques are needed.
- ▌ Usd Document Model · nvidia-omniverseUse this skill when implementing or verifying USD layer/spec/field storage.
- ▌ Usdc Binary Format · nvidia-omniverseUse this skill when implementing or verifying the low-level USDC Crate binary reader.
- ▌ Usdc Value Decoder · nvidia-omniverseUse this skill when implementing or verifying USDC Crate value representation decoding.
- ▌ Physically Based Renderer Validation · nvidia-omniverse bundleDesign, debug, or validate physically based renderer behavior against a reference renderer. Use when Codex works on PBR materials, USD light semantics, shadows, transparency, GI, emissive sampling, tone mapping, AOVs, stochastic sampling, path tracing, ray tracing, or Omniverse Kit/Hydra/OVRTX visual parity.
- ▌ Usda Lexical Format · nvidia-omniverseUse this skill when implementing or verifying the USDA text-format substrate.
- ▌ Usdz Package Format · nvidia-omniverseUse this skill when implementing or verifying USDZ package indexing and entry byte access.
- ▌ Ovrtx Projects Session · nvidia-omniversePersist a Variant Presenter workspace: named PROJECTS (bundle a stage with its base variant selection, display/optics, selected camera, per-camera looks/framing, and saved timeline views) and an automatic crash-recovery SESSION checkpoint that restores the live state after a server restart. Use when adding save/reopen + resilience to a variant presenter.
- ▌ Ovrtx Turntable Camera · nvidia-omniverseAuthor a turntable camera that orbits a chosen pivot one full revolution, into a SIDECAR USD layer (never touching the source), preserving the user's exact framed pose as frame 0, and play/scrub/render it correctly in ovrtx (where time-sampled xforms are NOT moved by update_from_usd_time — you must pxr-evaluate + fabric-write per frame). Use when adding a turntable / orbit-camera feature to a variant presenter.
- ▌ Usd Layer Stack Open · nvidia-omniverseUse this skill when implementing or verifying recursive local sublayer loading from resolved layer resources into a layer-stack namespace source.
- ▌ Usd Listops Authored · nvidia-omniverseUse this skill when implementing authored list operation values as they appear in a single layer.
- ▌ Usd Stage Population · nvidia-omniverseUse this skill when implementing or verifying population of a stage hierarchy from a namespace source.
- ▌ Usd Value Resolution · nvidia-omniverseUse this skill when implementing or verifying USD value resolution over already composed opinion stacks.
- ▌ Ovrtx Grid Batch Render · nvidia-omniverseBatch-render combinatorial USD variant permutations to disk with an ovrtx renderer: one-at-a-time and full-Cartesian matrix modes, a combinatorial-explosion guard, a {set}-{variant} naming convention, optional animation-range frame sequences, progress events, and cancel. Use when adding a grid/matrix/batch still-render feature to a variant presenter.
- ▌ Usd Remote Stage Mirror · nvidia-omniverseOpen a USD stage from an http(s):// URL by mirroring it and its full dependency closure (sublayers, references, payloads, textures) into a local cache, then opening the local copy — because pxr has no HTTP asset resolver. The remote source is never written; the stage's user-facing identity stays the URL. Use when a viewer must accept a pasted URL to a cloud-hosted USD (e.g. the NVIDIA ConceptCar S3 sample).
- ▌ Usd Resource Protocol · nvidia-omniverseUse this skill when implementing or verifying USD resource protocol support after asset resolution.
- ▌ Usd Variant Scan Classify · nvidia-omniverseScan a USD stage for variant sets and cameras, and classify each variant set by HOW its variants differ (shader-input = live "fast path" vs transform/visibility/binding/ structural = needs a reopen) so a live viewer can switch most variants without reloading. Also extract a representative color swatch per variant. Use when building variant switching / a configurator on top of an ovrtx viewer.
- ▌ Usd Composed Stage Open · nvidia-omniverseUse this skill when implementing runtime stage-open orchestration for composed USD stages.
- ▌ Usd Foundational Values · nvidia-omniverseUse this skill when implementing or verifying USD value storage independent of USDA syntax.
- ▌ Usd Variant Live Switching · nvidia-omniverseSwitch USD variants live in an ovrtx viewport WITHOUT reloading the stage when possible — replaying shader-input attribute writes for the "fast path", and falling back to a heartbeated composite reopen for transform/visibility/binding/structural variants. Use when wiring variant chips to a live RTX stream (the configurator experience).
- ▌ Nanousd Readonly Backend · nvidia-omniverseUse this skill when implementing or verifying a generated read-only backend for nanousd's C API.
- ▌ Usd Identifiers And Names · nvidia-omniverseUse this skill when implementing or verifying USD identifier and name handling.
- ▌ Usd Composition Arbitrator · nvidia-omniverseUse this skill when implementing or verifying the central composition arbitrator that forms composed prim and property opinion stacks before stage population.
- ▌ Nanousd Benchmark Reporting · nvidia-omniverseUse this skill when presenting benchmark results that compare the generated skillgraph nanousd backend against nanousd's default backend or another baseline backend.
- ▌ Usd Schema Namespace Source · nvidia-omniverseUse this skill when implementing or verifying schema-derived prim definitions, schema-defined properties, and schema fallback values over an already composed namespace source.
- ▌ Usd Payload Namespace Source · nvidia-omniverseUse this skill when implementing or verifying the first direct loaded payload opinion source backed by supplied payload arc sites and already-opened payload layers.
- ▌ Usd Variant Namespace Source · nvidia-omniverseUse this skill when implementing or verifying the first variant-composition namespace source backed by a base namespace source.
- ▌ Omniverse Dev Variant Presenter · nvidia-omniverse bundleBuild a browser-based, RTX-streamed app for exploring and rendering USD VARIANT PERMUTATIONS — a live ovstream/WebRTC viewport plus instant variant switching, cameras, a turntable rig, grid/batch stills, a multi-track timeline, projects, post, and remote-stage mirroring. Use when asked to build a "variant presenter / configurator" — or a "variant studio", the name used in the walkthrough video and earlier releases — a permutation render tool, or to add variant/timeline/batch features on top of an Omniverse realtime viewer.
- ▌ Usd Inherits Namespace Source · nvidia-omniverseUse this skill when implementing or verifying the first inherits-composition namespace source backed by a composed base namespace source.
- ▌ Usd Reference Namespace Source · nvidia-omniverseUse this skill when implementing or verifying the first reference-composition namespace source backed by a base namespace source and already-opened referenced layers.
- ▌ Usd Relocates Namespace Source · nvidia-omniverseUse this skill when implementing or verifying the first relocates-composition namespace source backed by a composed base namespace source.
- ▌ Omniverse Dev Variant Presenter UI · nvidia-omniverseThe visual design + layout for the Dev Variant Presenter frontend — the GitHub-dark + NVIDIA-green theme, the header / viewport+timeline / right-side tabbed control panel layout, and the component styles (pill chips with swatches, segmented buttons, blocks, the NLE timeline strip). Use when building or styling the Variant Presenter browser UI — also known as the "variant studio" UI in the walkthrough video and earlier releases — so it looks and feels like the product, not just functions like it.
- ▌ Usd Layer Stack Namespace Source · nvidia-omniverseUse this skill when implementing or verifying the first composed namespace source backed by a root document-model layer and its already-opened recursive sublayers.
- ▌ Usd Specializes Namespace Source · nvidia-omniverseUse this skill when implementing or verifying the first specializes-composition namespace source backed by a composed base namespace source.
- ▌ Usd Single Layer Namespace Source · nvidia-omniverseUse this skill when implementing or verifying the degenerate namespace source that wraps one document-model layer for stage population.
- ▌ Warmup · nvidia-omniverseWarming up the renderer before capturing output. Use when user asks about warmup frames, image quality, texture streaming, path tracing convergence, or why renders look noisy/incomplete.
- ▌ Sketch Stage · nvidia-omniverse bundleUse to generate or densify an OpenUSD stage from sketch-stage inputs (bounds / scale / densification mode / asset pack / intent), with the LLM driving placement one object at a time through collision-gated spatial-query tools while the user watches a live 2D+3D browser viz. Trigger phrases include "generate a USD stage", "densify a scene", "fill an area with assets from <pack>", "scene generation with LLM", "watch placement live", "incremental placement", "absorb a USD as a sketch template".
- ▌ Loading Usd · nvidia-omniverseLoading USD scenes into the renderer from files, URLs, or inline USDA strings. Use when user asks to load a USD scene, compose USD content, add cameras or RenderProducts to an existing USD layer, add referenced content, or create runtime geometry.
- ▌ Ovrtx Hero Render · nvidia-omniverse bundleProduce a polished native OVRTX still from a user Blender scene with explicit camera framing, materials, lighting, sample bounds, color ownership, and a low-cost smoke through the registered OVRTX Blender engine. Use for product, portfolio, or presentation hero frames; do not substitute another Blender engine while claiming OVRTX output.
- ▌ Cuda Interop · nvidia-omniverseGPU interop patterns for CUDA arrays, timeline semaphores, and Vulkan shared memory. Use when user asks about CUDA interop, GPU rendering pipelines, Vulkan interop, shared memory, or timeline semaphores.
- ▌ Cloning Prims · nvidia-omniverseCloning USD subtrees to create copies at new paths. Use when user asks to clone, duplicate, copy a prim, or create instances of existing geometry.
- ▌ Stage Queries · nvidia-omniverseDiscovering prims on the runtime stage and inspecting their attribute schemas. Use when user asks to find prims by type, filter by attribute, list all prims, or look up attribute types before reading or writing them.
- ▌ Error Handling · nvidia-omniverseError checking patterns for both C and Python. Use when user asks about error handling, checking errors, debugging ovrtx failures, or troubleshooting.
- ▌ Status Queries · nvidia-omniverseQuerying progress for asynchronous ovrtx operations. Use when user asks how to monitor long-running operations, show loading progress, inspect OperationStatus counters, use Operation.query_status(), or call ovrtx_query_op_status()/ovrtx_release_op_status().
- ▌ Update 0 2 0 3 · nvidia-omniverseUpgrade skill to migrate an existing ovrtx codebase from 0.2.0 to 0.3.0. Use when the user asks to "upgrade from 0.2 to 0.3", migrate ovrtx API usage, update 0.2 projects to 0.3, or fix code after moving from ovrtx 0.2.x to 0.3.x.
- ▌ Contract First Ffi · nvidia-omniverse bundleMaintain C ABIs and language bindings as exact, testable contracts. Use when evolving public headers, ctypes/cffi/pybind/Rust/JS bindings, shared libraries, struct layouts, GPU/native APIs, or any cross-language boundary where drift can cause crashes or silent corruption.
- ▌ Ovrtx Sensor Capture · nvidia-omniverse bundleCustomize and validate OVRTX sensor declaration, selection, stepping, and native readback for one or multiple render products. Use when developers add camera-like sensors or debug sensor identity and output routing in the add-on. This skill probes capabilities and does not claim every sensor family is already implemented.
- ▌ Usd Copy And Flatten · nvidia-omniverse bundleMake a reproducible, self-contained USD handoff from a Blender scene or existing USD layer by copying inputs, closing relative dependencies, and flattening into a derived USDA/USDC. Use when preparing an OVRTX, OVPhysX, SimReady, or downstream DCC handoff; never mutate the user's source asset. Requires the installed Blender/USD tooling and supported add-on/runtime.
- ▌ Project Setup C · nvidia-omniverseSetting up a new CMake C/C++ project that uses ovrtx. Use when user asks to create a new C project, set up CMake with ovrtx, scaffold a C++ app, or configure build dependencies.
- ▌ Render Settings · nvidia-omniverseWriting render settings to control rendering behavior. Use when user asks to change render settings, set max bounces, configure path tracing, change render quality, or modify RTX settings on a RenderProduct.
- ▌ Semantic Labels · nvidia-omniverseAssigning USD SemanticsAPI class and label metadata for semantic segmentation and ground-truth annotation outputs. Use when user asks to label objects, assign semantic class/label metadata, configure semantic segmentation labels, or author SemanticsAPI overrides.
- ▌ String Handling · nvidia-omniverseWorking with ovx_string_t in C and C++. Use when user asks about printing, comparing, or converting ovx strings.
- ▌ Ovrtx Render Sequence · nvidia-omniverse bundleDevelop and validate contiguous OVRTX sequence capture with stable session identity, explicit frame/sample boundaries, native readback, reset behavior, and deterministic output ordering. Use when developers customize the add-on for animation or multi-frame capture; the public render-spike baseline is one frame and does not itself prove sequence support.
- ▌ Ovrtx Render Settings · nvidia-omniverse bundleProbe and configure the registered OVRTX Blender scene settings for sample bounds, color-presentation mode, viewport-camera sync, and engine selection through exact Blender RNA. Use when changing supported OVRTX scene controls or diagnosing a setting that may not exist in the installed add-on version.
- ▌ Simready Prop Journey · nvidia-omniverse bundleTake one Blender prop through a concise SimReady workflow: preserve the source, author and validate it with the official SimReady add-on, check the supported OVRTX conversion boundary, run a native OVPhysX drop/contact test when appropriate, and prepare a portable USD handoff. Use when an artist wants an end-to-end physics-ready prop workflow rather than an infrastructure or validation-report project.
- ▌ Application Flow · nvidia-omniverseHigh-level overview of a typical ovrtx application lifecycle. Use when user asks how to structure an ovrtx program, what the main steps are, or how the pieces fit together.
- ▌ Async Operations · nvidia-omniverseAsynchronous operation patterns including polling, timeouts, and non-blocking workflows. Use when user asks about async rendering, non-blocking operations, polling, timeouts, or parallel rendering.
- ▌ Renderer Gpu Interop · nvidia-omniverse bundleShare renderer output zero-copy across GPU APIs and runtimes (Vulkan↔CUDA, Metal/MPS, DLPack to Warp/PyTorch) and own GPU resource lifetime and teardown across that boundary. Use when Codex wires external-memory/-semaphore interop, hands a render target to a training/compute consumer without a CPU bounce, or debugs interop fd ownership, cross-API sync, double-buffered overlap, ARC/handle lifetime, or teardown-order crashes.
- ▌ Blender Camera Framing · nvidia-omniverse bundleFit a named set of evaluated Blender objects into a perspective or orthographic render camera with correct render aspect, lens shift, margin, target, clipping, and JSON verification. Use when an MCP or background-Blender task must frame an object reliably rather than merely frame an interactive 3D viewport.
- ▌ Blender Mesh Authoring · nvidia-omniverse bundleCreate, modify, parent, and validate Blender mesh objects with stable names, direct data APIs, explicit modifier order, evaluated geometry checks, and reversible MCP transactions. Use for primitives, custom vertex/face meshes, transforms, parenting, bevel/solidify/subdivision modifiers, or topology repair when an out-of-box agent needs exact bpy mechanics rather than general modeling advice.
- ▌ Binding Materials · nvidia-omniverseBinding materials to prims at runtime. Use when user asks to assign a material, change a material, set material binding, or swap materials on a prim.
- ▌ Picking Selection · nvidia-omniverseViewport picking, marquee selection, pick-hit decoding, pickability, and selection outline drawing. Use when implementing click picking, drag selection, printing picked prim names, or highlighting selected prims.
- ▌ Renderer Creation · nvidia-omniverseCreating and configuring an ovrtx renderer instance. Use when user asks to create a renderer, initialize ovrtx, configure renderer options, or set up ovrtx.
- ▌ Renderer Backend Port · nvidia-omniverse bundlePort an existing nanoUSD renderer to a new GPU backend or API (e.g. Vulkan to Metal, DX12, or WebGPU) or stand up a second backend behind the shared renderer contract. Use when Codex adds a backend, translates shaders and RHI calls across graphics APIs, decides what to share versus reimplement versus stub, keeps backends at ABI and feature parity, or hits cross-API transform, struct-alignment, command-encoder, or resource-residency pitfalls.
- ▌ Ovrtx Materialx Openpbr · nvidia-omniverse bundlePrepare Blender materials for the add-on's OVRTX MaterialX/OpenPBR conversion and diagnose failures without renderer source access. Use for source textures, OpenPBR graphs, black/red/flat OVRTX materials, missing bindings, UV/normal-map issues, or Blender-versus-OVRTX material comparisons.
- ▌ Attribute Bindings · nvidia-omniverseCreating persistent attribute bindings for efficient repeated writes to the same prims and attribute. Use when user asks about persistent bindings, repeated writes, efficient animation loops, bind_attribute, or updating transforms every frame with caller-owned tensors. Use mapping-attributes when the hot path needs zero-copy direct writes into ovrtx buffers.
- ▌ Camera Outputs Rt2 · nvidia-omniverseAvailable camera render outputs for Real-Time Path-Tracing (RT2) mode. Use when user asks what AOVs/render vars are available, what format or dtype an output has, or how to read a specific output like depth, normals, albedo, or distance.
- ▌ Mapping Attributes · nvidia-omniverseZero-copy attribute map/unmap for direct memory access to ovrtx internal buffers. Use when user asks about zero-copy writes, map attribute, direct memory access, Warp/CUDA kernel writes into mapped tensors, or GPU attribute updates. Use attribute-bindings for repeated writes with caller-owned tensors when a copy is acceptable.
- ▌ Reading Attributes · nvidia-omniverseReading scalar or array attributes from prims into CPU or GPU tensors. Use when user asks to read an attribute value, fetch mesh data (points, faceVertexCounts, etc.), inspect a render setting, or sample transforms.
- ▌ Writing Attributes · nvidia-omniverseWriting scalar and array attribute data to prims. Use when user asks to write an attribute, set a property, change a material, set a color, or modify mesh data.
- ▌ Writing Transforms · nvidia-omniverseWriting 4x4 transform matrices to move, rotate, or scale prims. Use when user asks to move an object, set a transform, update position, animate a transform, or set a camera transform.
- ▌ AI Agent Orchestration · nvidia-omniverse bundleCoordinate multiple AI agents or subagents on software work without duplicating effort or causing conflicts. Use when Codex is explicitly asked to delegate exploration, implementation, review, testing, integration, or parallel analysis across a codebase.
- ▌ Graphics Debugging Lab · nvidia-omniverse bundleDebug rendering, viewer, shader, material, camera, lighting, and GPU integration bugs with reproducible visual evidence. Use when scenes render blank, only appear after camera motion, show incorrect shading, diverge across backends, crash in GUI mode, or need pixel/screenshot verification.