render-product-device-pinning

Pin RenderProducts to CUDA-visible GPUs using the USD deviceIds attribute.

201|25|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/NVIDIA-Omniverse/ovrtx --skill render-product-device-pinning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: render-product-device-pinning
Source: https://github.com/NVIDIA-Omniverse/ovrtx/tree/main/.agents/skills/render-product-device-pinning
Command: npx skills add https://github.com/NVIDIA-Omniverse/ovrtx --skill render-product-device-pinning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restricting RenderProducts to CUDA-visible device indices with the USD deviceIds attribute ensures deterministic rendering and reliable testing in multi-GPU environments.

Core Features & Use Cases

  • Constrain a RenderProduct to a specific CUDA-visible GPU or set of GPUs to support deterministic CI runs or viewport picking.
  • Align rendering workloads with CUDA-visible device remapping to prevent cross-GPU contention.
  • Simplify scenario testing by pinning render paths to known GPUs in complex scenes.

Quick Start

Pin a RenderProduct to a CUDA-visible GPU by setting its deviceIds in USD before loading the scene.

Frequently Asked Questions about render-product-device-pinning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does viewport picking fail in multi-GPU environments?

Pinning RenderProducts to specific CUDA-visible GPUs using the USD deviceIds attribute prevents cross-GPU contention. This device constraint alignment ensures reliable viewport picking in complex multi-GPU scenes.

Does USD support assigning render workloads to specific CUDA devices?

Yes, USD supports assigning render workloads to specific CUDA devices by authoring the RenderProduct deviceIds attribute. This restricts rendering to designated CUDA-visible device indices and respects CUDA_VISIBLE_DEVICES remapping.

What is the best way to ensure deterministic CI runs in multi-GPU environments?

Constrain RenderProducts to specific CUDA-visible GPUs using the USD deviceIds attribute. This aligns rendering with CUDA_VISIBLE_DEVICES remapping to prevent cross-GPU contention and ensures deterministic CI runs.

How do I set the deviceIds attribute on a RenderProduct in USD?

Author the deviceIds attribute on the RenderProduct in USD before loading the scene. This pins the RenderProduct to a specific CUDA-visible GPU or set of GPUs, enforcing device constraints during rendering.

When do I need to restrict RenderProducts to CUDA-visible device indices?

Restrict RenderProducts to CUDA-visible device indices when scenarios require deterministic rendering, reliable viewport picking, or simplified testing in multi-GPU environments. This prevents cross-GPU contention during rendering.