Certain static controls
StaticHero
Show in Renders is off and camera-ray visibility is off. Both supported object restrictions are certain. Each control card shows its owner and native location.
A quieter way to investigate
Explain static visibility controls and collection paths.
Inspect a named object without changing scene settings. Any animation data—even position-only keys—can leave object controls unknown.
Scene and guide only; inspecting it requires the full extension.
ONE OBJECT · EVERY CAPTURED PATHBLENDER 5.2.1
Four cases, one honest workflow
Keep the intentional settings.
Understand the rest.
Choose the excluded object by name. Read why each route is restricted, find its native control, compare one other layer, then hand off the explanation.
Two collection paths
SharedHero
Parent A is excluded; Parent B provides an included route. See both occurrences of Shared and avoid treating one exclusion as the whole explanation.
Intentional role
IntentionalHoldout
A deliberate holdout stays exactly as it is. Render roles are context for investigation, with no automatic fix or repair recommendation.
Useful partial result
MovingHero
The same raw flags as StaticHero, plus one location keyframe. Object controls remain unknown; its static parent exclusion is certain. Refresh preserves that limit.
A reference, not a repair button
From the explanation to the exact native control.
Open a read-only card with the full owner, ancestor path, scope and property reference. The guide distinguishes a global monitor from a layer-local eye, and shows how to expose hidden restriction columns.
If Blender cannot expose a descendant under exclusion, the card identifies the accessible blocking ancestor. You decide whether to make any native change.
Read the native-control guide →
A handoff you can actually read
Local reports, with names removed by default.
Preview the fresh snapshot before saving HTML or copying text. Reports retain causes, all captured paths, comparison and uncertainty. Name removal preserves relationships, so it is not irreversible anonymization.
Static explanation
A real exported report from StaticHero, showing the two certain supported object restrictions.
Open static report →Animated partial explanation
A real MovingHero report preserves unknown object controls and the independently certain parent exclusion.
Open partial report →What it checks
- Object monitor, render and temporary eye controls.
- Every bounded root-to-membership path, including shared collections.
- Cycles camera-ray visibility and effective render-role context.
- One other layer at the same frame, without switching it.
What stays outside
- Evaluated animation, even when only position is keyed.
- Occlusion, material transparency and final visible pixels.
- Generated geometry, instances and modifier evaluation.
- Automatic edits, fix-all, render execution and uploads.
Inside the extension
One investigation, a complete trail.
Native and free options remain useful.
The Outliner and Object Visibility controls solve ordinary cases directly. K-Tools Visibility Check provides a free mismatch workflow; other tools already offer collection management and reporting. RenderWhy packages a focused path explanation, exact-control handoff and readable report.
Prepared for review · distribution pending
Try the evaluation materials.
Full extension distribution is not open yet; the planned $12 package will be supplied through the approved delivery route.
Read installation guide · Sample notes and license · Public file hashes
No checkout or store listing is active. No account, telemetry, scene upload or license server is part of the extension.