RenderWhy

RenderWhy 1.0.0 · offline guide

Install the complete versioned package

Full extension distribution is not open yet. This guide requires the privately coordinator-supplied or later approved merchant-supplied renderwhy-1.0.0.zip. The public scene and reports do not contain an executable inspector.

Exact operating prerequisite

Official Blender 5.2.1 LTS, build 9e2066aef7ef, Linux x64, using Cycles. The extension manifest permits 5.2.1 up to but excluding 5.2.2. Other Blender versions, custom builds, Windows, macOS and other render engines have no v1 support claim. There are no runtime pip packages, accounts or network requirements.

Install

  1. Keep the distribution bundle and verify its SHA-256 inventory. Extract the delivery bundle; leave the extension ZIP itself zipped.
  2. Open Blender. In Edit → Preferences → Get Extensions, open the repository/options menu and choose Install from Disk.
  3. Select renderwhy-1.0.0.zip, install into a local repository and enable RenderWhy. Do not install the delivery/source ZIP as an extension.
  4. Return to the 3D View, press N for the Sidebar and choose RenderWhy. F3 → RenderWhy: Inspect Object is the keyboard entry.

If the host is rejected, use the exact supported official release. Do not edit version bounds or bypass a failed check. Installation writes Blender preferences only when you explicitly install/enable the extension; investigation operators do not modify scene data.

Update, disable and uninstall

Close any RenderWhy dialog or pending operation. Keep your old package. Disable RenderWhy in Preferences, install the replacement ZIP from disk, then enable it and take a new snapshot. If a replacement fails, reinstall the prior tested ZIP. To uninstall, disable/remove RenderWhy through Preferences; it leaves no Scene/Object custom properties or report datablocks behind. Exported reports remain your local files.

Fixed draft purchase unit

The planned $12 one-time RenderWhy 1.0.0 distribution package contains the complete GPL-3.0-or-later extension/source, matching source/build/test archive, synthetic scene and reports, offline guides, licenses, changelog and hashes.

The draft includes 30 calendar days after purchase of installation and documented-core-workflow assistance through the seller’s eventual real support contact, plus any 1.0.x corrective replacement builds actually issued during that period. It promises no response-time SLA, new feature release, future Blender/OS compatibility, recurring support, lifetime updates or private client-scene investigation. The delivered version has no runtime expiry or activation check and remains usable afterward.

No seat, machine or client-work restriction is added beyond the bundled licenses. GPL recipients retain redistribution rights. Your scenes and reports remain yours. Seller identity, support contact, lawful refund terms, approved listing and tested delivery must be confirmed before sales activation; no checkout, store badge or support address is invented here.

Any animation data—even position-only keys—can leave object controls unknown. The frame is snapshot context; Refresh cannot verify those animated controls in v1.