Installation

Blaze Puppeteer installs as a Blender extension and ships with the runtime wheels needed for local generation. During extension installation, Blaze Puppeteer installs that bundled runtime automatically on the same machine where Blender is running.

Local Generation Is Required

Signing in does not unlock a separate cloud-generation mode. Preset Prompts, Custom Prompts, Anchors, Waypoints, and Dense Path all still depend on a ready local runtime.

What You Are Setting Up

Blender Extension

Install the zip directly through Blender’s extension flow. You can drag the zip into Blender or use Install from Disk…. Do not unpack the archive first.

Panel And Preferences

Open preferences, under Blaze Puppeteer choose whether the panel lives in the Sidebar (N-Panel), the Properties Tab, or both.

Local Runtime

The bundled wheels are installed automatically during extension installation. Blaze Puppeteer validates the local Kimodo assets and selects the best provider available on your machine.

System Requirements

Platform	Local generation support	Notes
Windows x64	Yes	Uses NVIDIA CUDA when available, otherwise CPU fallback
Linux x64	Yes	Can use CUDA, ROCm, or CPU depending on the machine
macOS Apple Silicon	Yes	Uses Apple MPS when available, with CPU fallback
macOS Intel	No	Local generation is not supported on Intel macOS

Blender version: 4.2 or newer.

Local Processing with CPU

Blaze Puppeteer can still generate on CPU on supported platforms. The main difference is speed.

Step 1: Install The Extension

1. Download the zip

   Download the current Blaze_Puppeteer.zip build from your order page on Superhive Market.

2. Open Blender Preferences

   Open Edit → Preferences in Blender.

3. Install the zip

   Either drag the zip file into Blender, or open Get Extensions, open the top-right menu, choose Install from Disk…, and select the zip file.

4. Enable Blaze Puppeteer

   Confirm the extension is enabled, then select an armature in your scene and open the Blaze Puppeteer panel. You may need to disable and re-enable the extension to see the panel.

Installing and activating Blaze Puppeteer

Step 2: Choose Your Basic Preferences

Open Preferences → Add-ons → Blaze Puppeteer and review these first:

Setting	What it controls	Good default
UI Location	Shows the panel in the 3D Viewport sidebar, the Properties tab, or both	Sidebar
Keep Kimodo Warm	Keeps the local Kimodo worker alive between runs so subsequent generations start faster	Off unless you want faster results and don’t mind your gpu vram being used to keep the model loaded
Timeout (s)	Controls how long Blaze Puppeteer waits on login, credit, and Motion Refinement requests	Leave the default unless support asks you to change it

If support asks you to inspect logs, the same preferences page also exposes logging controls. Most users can ignore them.

Blaze Puppeteer preferences

Step 3: Automatic Runtime Install

During extension installation, Blaze Puppeteer installs the bundled local runtime automatically and validates the included model files.

What Blaze Puppeteer does automatically

1. Resolves the bundled setup that matches your platform and Blender Python version.
2. Installs the packaged Python dependencies and torch into the local generation environment.
3. Installs the bundled MotionCorrection wheel.
4. Validates the Kimodo model bundle and selects the best provider available on your machine.

Step 4: Confirm Readiness

After preparation, the Local generation line should settle into one of these labels:

Status	Meaning
Local generation: GPU (Torch CUDA)	Kimodo is using a CUDA-capable NVIDIA setup
Local generation: GPU (Torch ROCm)	Kimodo is using a ROCm-capable Linux setup
Local generation: GPU (Torch MPS)	Kimodo is using Apple Silicon acceleration
Local generation: CPU (Torch)	Kimodo is ready, but running on CPU

If you still see Local generation: checking… for too long or an error state, go to Troubleshooting.

The Motion panel also needs Rig Setup: Ready before you can generate against a character. Runtime readiness and rig readiness are separate checks.

Ready local generation state

the readiness area showing a completed Local generation label such as GPU or CPU.

Updating Blaze Puppeteer

When you install a new build:

1. Remove the current extension from Blender.
2. Restart Blender fully.
3. Install the new zip.
4. Open the add-on preferences and confirm the Local generation line still shows a ready label.

When to reinstall

If the bundled runtime installation was interrupted or the local environment becomes inconsistent, reinstall the extension cleanly before digging into Blender or Python state by hand.