Troubleshooting

Use this page when the panel does not look ready, the bundled runtime install did not complete cleanly, or a generated result is not reacting to the guides you authored.

Setup And Readiness

”No armature selected”

Pick the character in the Target Armature field first. Blaze Puppeteer does not guess which rig you mean.

”Rig not configured” or “Rig setup incomplete”

Check these items in Rig Setup:

• All five required chains have entries
• The chain order is correct
• You either picked a Root Controller or enabled No Root Controller
• You finished the T-pose workflow

”Reconstruction needed”

Blaze Puppeteer cannot find the helper rigs it expects for the selected armature. Run Reconstruct again.

”Bone lists changed since last reconstruction”

Your current Rig Setup lists no longer match the data stored on the helper rig.

• Use Reconstruct if the new lists are the right ones
• Use Restore if you want to return to the previous reconstructed state

Local Runtime

”Local generation: checking…”

This is normal for a short time while Blaze Puppeteer checks the local runtime on your machine. If it never settles, reopen Blender and check the same status line in the add-on preferences.

”Local generation: unavailable”

Something went wrong beyond the normal unprepared state. Common causes:

• Unsupported platform for local generation
• Interrupted bundled runtime install
• Missing or damaged local runtime files
• Missing or damaged model files

Reinstall the extension cleanly first. If the machine is on Intel macOS, move the generation workflow to a supported platform.

Installation completes but local generation stays unavailable

Check these:

1. The machine has enough free disk space for the runtime files.
2. Security software is not blocking Blender’s runtime files.
3. You restarted Blender after installing a fresh build of the add-on.
4. The installed build matches your platform and Blender version.

Reinstall before deep debugging

If the bundled install stopped halfway through or the local environment looks inconsistent, a clean reinstall is usually faster than trying to manually patch the runtime state.

Local generation is slow

If the Local generation line settles on a CPU label, Blaze Puppeteer is running on CPU instead of GPU. The workflow still works, but it will be slower.

I logged in, but generation still will not run

Login does not replace the local runtime. Even Custom Prompts still depend on Local generation being ready.

Account And Remote Features

Login does not complete

Check that:

• The browser flow finished successfully
• Blender still has network access
• Blender can save the returned sign-in session on your machine

If login still fails, log out completely and try again after reopening Blender.

Credits look wrong or stale

Use Refresh in the account bar. If the value still looks wrong after a completed purchase, sign out and back in.

Custom Prompts are unavailable

Custom Prompts requires both:

1. A valid login session
2. A ready local runtime for the actual generation

If either one is missing, Blaze Puppeteer cannot run the typed-prompt workflow.

Motion Refinement is missing

Refinement only appears when:

• You are logged in
• A generated History action is selected

If you are signed in but nothing is selected in History, the refinement controls stay hidden.

Refinement also works from the selected History motion only. It does not use the current anchors, waypoints, prompt strips, prompt text, or Dense Path.

Authoring Problems

Anchors are not shaping the result

Check these:

• The blocked keyframes were actually turned into anchors
• The important start and end moments are anchored
• You are looking at the same armature the panel is targeting

Prompt strips are not doing anything

Prompt strips only work when Multi-Prompt is enabled. Also make sure the strips were created through Blaze Puppeteer’s own Sequencer workflow, not as unrelated text strips.

Waypoints are ignored

Waypoints only affect the result when:

• Waypoint is the active task, or
• Use Waypoints is enabled while another task is active

Remember that a waypoint is tied to the current frame when you place it.

Dense Path is ignored

Dense Path only affects the result when:

• Dense Path is the active task, or
• Use Dense Path is enabled on another task

If the curve was deleted or the draw stroke was never finished into a curve, there is no path for Blaze Puppeteer to use.

Blaze Puppeteer warns about locked or driven controls

If you see Animation Restrictions Detected, Blaze Puppeteer found important controls with locked transforms or driven channels. The dialog lets you choose Override All or Skip Restricted.

History And Action Issues

The generated motion exists in History but the rig does not move

The selected action may not be bound to the armature correctly in Blender’s Action system. Re-select the generated motion from Blaze Puppeteer History first, then inspect the Action Editor if needed.

History is cluttered with experiments

Use the right cleanup button for the job:

• Remove Selected for just one entry
• Remove Family for a whole branch
• Purge Derived to keep the base generation and drop its retries or refinements
• Clear Armature to wipe the generated History for that rig

Still Stuck?

Open Blender’s system console or launch Blender from a terminal and check the Blaze Puppeteer log output.

• Windows: Window → Toggle System Console
• Linux / macOS: start Blender from a terminal

When contacting support, include:

1. The exact message shown in the Blaze Puppeteer panel
2. What task you were running
3. Whether you were using presets, Custom Prompts, or refinement
4. The relevant console lines