Development

Diagnose rendering and performance

Inspect each result and qualify the first failure. Distinguish an unsupported backend or missing provider from an invalid handle, stale frame, missing pass preparation, and incomplete GPU work. Report the renderer error and enough context to identify the profile, terminal, and view being used.

Black frame or incorrect output

  1. Verify frame admission, a valid view and extent, the live target, and a ready profile.

  2. Compile or inspect the actual terminal. Confirm that selected resources have writers and the expected formats and ownership.

  3. Inspect object/material preparation, light and shadow inputs, and the color and display routing. Use a raw producer output before post.

  4. For resize or replacement, confirm that submitted work still owns the previous images, that the new surface format matches the new output path, and that histories follow the correct view identity.

Measure three clocks

GPU elapsed time from completed timestamps measures GPU work. Wall-clock presentation cadence measures how often frames are presented at the observed application boundary. CPU-side work and pacing can change cadence even when GPU work is unchanged. Compare regular cadence, unpaced work, and per-pass GPU timestamps separately. Timestamp values arrive after their recording frame and can be missing during startup or on unsupported configurations.

To compare passes, hold the view and extents steady, confirm the actual active options and GPU capabilities, warm the scene, and use a range of completed samples. For startup, track scene import and geometry cooking, material translation and upload, shader compilation/linking, driver pipeline preparation, and first usable publication independently. A compatible cache hit should be established by observing the work it avoids.