warmup

Warm up the renderer to stabilize initial frames and reduce texture streaming gaps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Warming up the renderer before capturing output helps ensure stable image quality by allowing textures to stream in and path-tracing accumulation to start.

Core Features & Use Cases

  • Guided warmup workflow: provides a recommended number of frames and the sequence to prime textures and convergence.
  • Texture streaming awareness: explains how initial frames load lower mip levels and progressively sharpen as data streams.
  • Use Case: QA checks or demonstrations where consistent render output is required after opening a scene or changing render settings.

Quick Start

Run the warmup sequence after loading USD data or altering render settings to prime the pipeline before capturing outputs.

Frequently Asked Questions about warmup

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

FAQPage Schema
How do I warm up a renderer to fix texture streaming and path-tracing convergence issues?

Warm up the renderer by stepping through multiple frames after loading USD data or changing render settings. This allows path-tracing convergence to accumulate and texture streaming to load higher mip levels for stable image quality.

Why do my initial rendered frames look blurry or low quality after loading a scene?

Initial frames look low quality because the renderer loads lower mip levels while texture streaming is active. Running a warmup sequence primes the pipeline and progressively sharpens the image as data streams in.

What is the correct renderer lifecycle order for capturing converged frames?

The correct renderer lifecycle order is to initialize the renderer, load USD data, step warmup frames, then capture outputs and release resources. This ensures path-tracing accumulation stabilizes before capture.

When should I run a warmup sequence for path-tracing convergence?

Run a warmup sequence immediately after loading a scene or changing render settings. This enforces the correct renderer lifecycle order and stabilizes path-tracing convergence before you capture outputs.

Do I need to warm up the renderer every time I change render settings?

Yes, you need to warm up the renderer after changing render settings to allow path-tracing convergence to restart and texture streaming to stabilize. This ensures consistent render output for QA checks or demonstrations.

Can I capture outputs immediately after loading USD data without warming up the renderer?

No, capturing outputs immediately after loading USD data bypasses the warmup sequence, resulting in unstable image quality. You must step warmup frames to allow texture streaming and path-tracing convergence to stabilize.