RenderWhy

RenderWhy 1.0.0 · offline guide

A complete visibility investigation

Pin one original object, understand its controls and paths, and hand off a readable explanation.

  1. Install the separately supplied full ZIP in official Blender 5.2.1, Cycles, Linux x64.
  2. Open the four-case synthetic scene deliberately through Blender File → Open.
  3. Choose 3D Viewport → Sidebar → RenderWhy → Choose scene object, or F3 → RenderWhy: Inspect Object. Search includes objects excluded from the active layer.
  4. Read Viewport restrictions and Camera-render restrictions separately. Open included routes as well as blocked ones.
  5. Use Show control for its exact native location. A card does not edit or navigate the scene.
  6. Optionally Compare layer. Both layers are captured at the same frame without switching or enabling either.
  7. After deliberate native edits, Refresh. Export Report first chooses an HTML destination, then recaptures and opens a fresh privacy preview. Copy Report recaptures and previews before copying.
Static controls and collection paths are the core. Any animation data—even position-only keys—can leave object controls unknown. Frame is snapshot context. Refresh does not remove this limitation.

Keyboard reading

Leave the pointer in a 3D View. F3 opens every main action: Inspect Object, Refresh Inspection, Compare Layer, Clear Comparison, Show Control, Full Details, Next Detail Page, Previous Detail Page, Export Report and Copy Report.

In the object-name dialog, type a name, Enter to commit the field, then Enter to find results. Choose the focused search result with arrows/Enter; Escape cancels. Continue Object Search resumes incomplete searches. Show Control accepts a stable row number. Reading dialogs wrap full names and paginate; Escape closes, and F3 Next/Previous Detail Page opens the adjacent page.

Pinned snapshots

Selection changes do not retarget a report. Its scene, layer, frame/subframe and capture time remain visible. A scene switch or deleted target clears it with a recovery action. Invalidation marks a snapshot stale; it is not proof that every external change was observed. Export recaptures after the file chooser returns; Copy recaptures immediately. Both show the fresh preview before any output changes.

Other routes

Native Outliner restriction columns and Object Visibility solve many ordinary cases. Free K-Tools Visibility Check offers a mismatch workflow. Other products already offer collection/layer management and reports; RenderWhy makes no exclusive-coverage or speed-superiority claim.