Render Settings

Render Settings

When to Use

Use this skill when the user asks to change render settings, set max bounces, configure path tracing, change render quality, or modify RTX settings on a RenderProduct.

Inputs

Resolve inputs in this order: existing repository files and referenced snippets, explicit user request, then broader agent context.

• Target API surface: Python, C/C++, USD, or a combination.
• RenderProduct prim path and the exact omni:rtx:* setting attribute to author or update.
• Desired setting value, USD type, runtime/write timing, and whether reset/warmup behavior matters.
• Existing scene or snippet that already owns related RenderProduct settings.
• Repository source snippets referenced below. Treat these snippets as the API source of truth.

Prerequisites

• Use an ovrtx checkout that contains the referenced examples and docs tests.
• Read the relevant > **Source:** snippet before writing or explaining API usage.
• Confirm the setting belongs on the RenderProduct prim, not on a Camera, RenderVar, or renderer creation option.
• Use writing-attributes when the setting is changed through runtime APIs.

Instructions

1. Identify the RenderProduct path and the exact RTX setting attribute to change.
2. Write settings on the RenderProduct prim, not on the Camera or RenderVar prim.
3. Match the value type to the USD attribute schema and preserve existing authored settings that are unrelated to the request.
4. Apply the writing-attributes skill when setting values through runtime APIs rather than static USD.
5. When changing code, run the render-settings docs test that owns the setting snippet whenever practical.

Output Format

• For explanations, cite the relevant API names, source snippets, and caveats.
• For code changes, summarize the files changed, snippets affected, and validation run.

Scripts

This skill has no scripts.

Limitations

• The referenced snippets remain the source of truth; update or add tested snippets before documenting new API usage.

Overview

Render settings in ovrtx are written as attributes on the RenderProduct prim. To change a setting, use write_attribute() in Python or ovrtx_write_attribute() in C, targeting the RenderProduct prim path (e.g., /Render/Camera) with the setting's attribute name.

Settings use the omni:rtx: namespace prefix. For example, to set the maximum number of path tracing bounces, write omni:rtx:rtpt:maxBounces as an int32 attribute.

After changing a render setting, call reset() and run warm-up frames to allow the renderer to converge with the new setting.

Python

Set a render setting on a RenderProduct

Source: tests/docs/python/test_base.py snippet doc-set-render-setting

C

Set a render setting on a RenderProduct

Source: tests/docs/c/test_base.cpp snippet doc-set-render-setting-c

Key Types / Functions

Render Mode Selection

Real-Time Path-Tracing Settings (rtpt:)

Sampling and Caching

Ray Bounces and Shading

Firefly Filter

Gaussian Splatting

Path Tracing Settings (pt:)

Path Tracing

Denoising

Sampling and Caching

Firefly Filter

Spectral Rendering

Non-Uniform Volumes

Multi-GPU

Global Volumetric Effects

Anti-Aliasing

Minimal Settings

Troubleshooting

• Render settings are attributes on the RenderProduct prim, not on a separate RenderSettings prim. Write them to the same prim path you pass to step() (e.g., /Render/Camera).
• The dtype must match exactly -- omni:rtx:rtpt:maxBounces is int32, not int64.
• After changing a setting, call reset() and run warm-up frames before capturing output. The renderer needs time to reconverge.
• Settings use the omni:rtx: namespace prefix, with subsystem prefixes like rtpt: (real-time path tracing), post: (post-processing), etc.

References

• Use the > **Source:** directives in this skill to locate tested snippets before reusing API patterns.
• Keep related skills, docs, and snippets synchronized when changing the workflow.