writing-attributes

Write scalar and array USD prim attributes with dtype and shape validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables writing scalar and array USD prim attributes, allowing updates to properties such as colors, materials, visibility, or mesh data.

Core Features & Use Cases

  • Guides deterministic, typed attribute writes across Python and C/C++ workloads with proper dtype and shape validation.
  • Supports scalar and array attributes (colors, materials, mesh data) via attribute bindings and example snippets.
  • Provides lifecycle, data semantics, and troubleshooting guidance to ensure safe, authored attribute population.

Quick Start

Run a minimal attribute write example to modify a prim's color using the ovrtx API.

Frequently Asked Questions about writing-attributes

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

FAQPage Schema
How do I write attributes to USD prims in an Omniverse scene?

To write attributes to USD prims, you can use the ovrtx API to author scalar and array attributes, modifying parameters like colors, materials, and mesh data with strict dtype and shape validation.

Can I update both scalar and array USD prim attributes using Python and C++?

Yes, you can update scalar and array USD prim attributes using both Python and C++ workflows, applying attribute bindings and proper data layouts to ensure deterministic, typed attribute writes across Omniverse scene graphs.

What is the best way to ensure deterministic USD attribute writes?

The best way to ensure deterministic USD attribute writes is to enforce strict dtype and shape conformance alongside correct lifecycle handling and attribute bindings when modifying parameters on scene prims.

Why does writing USD prim attributes fail due to data layout or dtype issues?

Writing USD prim attributes fails when data layouts and dtypes lack strict conformance, which is why correct lifecycle handling and attribute bindings are required to ensure safe, authored attribute population.

Does writing attributes to Omniverse scene prims require specific lifecycle handling?

Yes, writing attributes requires correct lifecycle handling to ensure safe, deterministic changes to the scene graph, preventing errors during the modification of scalar and array prim properties.

What are the limitations when modifying USD prim attributes via the ovrtx API?

Limitations include the strict requirement for dtype and shape conformance for array and scalar attributes, meaning incorrect data semantics or lifecycle handling will prevent safe, authored attribute population.