RenderWhy

RenderWhy 1.0.0 · offline guide

Scope, limits and recovery

Version 1.0.0 targets official Blender 5.2.1 / Cycles / Linux x64. It explains supported static restrictions on original scene objects, not final visible pixels.

Animation stays explicitly unknown

Any animation data on an owner—actions, drivers, NLA or even a location-only keyframe—makes its animation-capable controls unavailable for current-value inference. Raw RNA may reflect another frame. Reports label that value as last observed and do not use it as a blocker or an open route. Independently static Collection/LayerCollection restrictions remain useful.

The adapter never requests or updates an evaluation graph, changes frame or view layer, enables a render layer, executes a render, changes trust settings, or evaluates generated geometry to recover a value. Refresh captures another snapshot; it does not remove this limit.

Coverage

Resource boundaries

Per inspected layer: 20,000 occurrences, depth 128 and 512 materialized paths. At most two layers. A cooperative five-second capture deadline stops before the next bounded unit; one native call can overrun it. Modal chunks process at most 200 occurrences and check an approximately eight-millisecond deadline between units. Escape cancels at the next check.

Scene search examines at most 2,000 candidates per continuation and retains 50 visible matches. Incomplete search exposes Continue searching. UI path rows page at 50. Direct-membership fallback examines at most 20,000 object references across a capture. Reports stop before replacing a file or clipboard if escaped UTF-8 would exceed 10 MiB.

Recovery

Limits are not performance guarantees. Public speed superiority or customer-demand claims are not made.