RenderWhy 1.0.0 · offline guide
Four synthetic cases to inspect
renderwhy-demo-1.0.0.blend from the public homepage, or use the identical scene in the separately supplied full delivery. Open it deliberately with Blender File → Open and follow Blender’s native unsaved-work handling. RenderWhy never replaces your document.The sample uses only original synthetic meshes and static controls, plus MovingHero’s single location keyframe. No executable scene script, external library or real customer data is embedded. Set no trust exception. The guide’s names correspond to the scene; exported examples use default aliases.
1. StaticHero — the certain static control
Inspect StaticHero in Main at frame 1. It has no animation data, constant hide_render=True and visible_camera=False. Both object-wide camera-render reasons are certain. Read Show control for Show in Renders and Ray Visibility / Camera. Included collection paths do not bypass an object-wide restriction.
2. SharedHero — keep both routes
Inspect SharedHero. Shared appears under Parent A and Parent B. Main / Parent A is excluded; Main / Parent B / Shared is included. Both paths must appear. The excluded branch alone does not hide every route. Open its Include card, then the surviving path. Compare Alternate at the same frame; this does not switch or enable it.
3. IntentionalHoldout — preserve its role
Inspect IntentionalHoldout. Its static holdout role is deliberate and remains unchanged. The explanation is neutral: intentional roles may be in use. Do not treat it as something to repair.
4. MovingHero — useful partial coverage
MovingHero has the same constant raw object flags as StaticHero, plus only a location keyframe. Its parent collection Moving Excluded is statically excluded in Main. The object flags are last observed / current evaluation unavailable; the independently static parent exclusion is a certain cause. Compare this with step 1. Refresh preserves the animation limit.
The UI explains: “This object has animation data, so v1 cannot confirm its object visibility controls—even if only its position is animated. Known collection restrictions are listed separately. Refresh takes a new snapshot; it does not remove this limit.”
Make a readable handoff
Choose Export Report, select an HTML destination in the native file chooser, then review the freshly captured privacy preview. Confirm Save report; replacing an existing file requires Continue to replace and the separate Replace Existing Report confirmation. Copy Report opens a fresh preview directly. Project-name replacement starts enabled each time; Cancel changes no output. The public StaticHero and MovingHero HTML examples are real exports of this fixture with aliases enabled. Frame/subframe is snapshot context, not certification of evaluated animation or final pixels.
Original synthetic scene/assets: CC0-1.0. Reports and guides: CC0-1.0. Code is supplied separately under GPL-3.0-or-later.