Troubleshooting

Having trouble? You’re in the right place. Here are the most common issues and how to fix them.

Setup Issues

You’re missing bones in one or more of the required lists.

Open the Rig Setup panel.
Check Legs (R/L), Hands (R/L), and Spine. Every list needs at least one bone (Legs need at least two).
Make sure you’ve either assigned a Root Controller or checked No Root Controller.

You’ve modified the bone lists after the last reconstruction, so the proxies are out of sync.

To apply your changes: Click Reconstruct to rebuild the proxies.
To undo your changes: Click the Restore button (↩) to revert the lists back to what the proxies expect.

The addon couldn’t reach the server or didn’t get a response in time.

Make sure your network allows outbound HTTPS traffic.
If you’re on a VPN, try disconnecting temporarily.
Go to Edit > Preferences > Add-ons > Blaze Puppeteer and increase the Timeout setting (default is 60 seconds).

Your login session has expired.

The T-Pose calibration is probably off, or root motion isn’t enabled.

Go back to Rig Setup and click Reconstruct.
During the Front/Top view stages, make sure _TPOSE is perfectly aligned with no rotation on the root.
If the character is traveling through space, enable Extract Root Motion in the Inbetweening tab.

Puppeteer may be prioritizing overall motion flow, or your anchors are tagged as Soft.

Use F to tag frames as Hard Anchors (Red) for strict enforcement.
Make sure Enforce Anchors is toggled ON in the panel.
Double-check that your start and end poses are physically realistic. Impossible stretches confuse the solver.

No IK controllers are mapped yet.

Double-check that IK mode is selected (the toggle next to Generate) before generating.
In Rig Setup, confirm every joint’s IK column actually has a bone assigned.
On your original rig, make sure the IK constraints are active and the chain lengths are correct.

The proxy system handles non-identity transforms automatically. Just run Reconstruct again and the proxies will regenerate correctly.

Blender 4.x introduced “slotted” actions. If an action’s slot is unassigned, keyframes exist but don’t drive anything.

Puppeteer handles this automatically, but if you’ve been manually editing actions:

Select your armature.
Open the Action Editor (Dopesheet > Action Editor mode).
Check the action’s slot. If it says “Unassigned”, click it and select your armature name.

Code	What it means	What to do
`ERR_NO_CREDITS`	Not enough credits for this duration.	Add credits at blazeanimation.com.
`ERR_AUTH_INVALID`	Session expired or corrupt.	Logout and login again.
`ERR_UPSTREAM`	Processing server is busy or down.	Wait a few minutes, then retry.
`ERR_FETCH`	Can’t reach the server.	Check your firewall or internet.
`ERR_SIGNUP_FAILED`	Problem with Order ID or email.	Make sure your Superhive Order ID is valid and unused.

Check the system console for details:

Go to Window > Toggle System Console (Windows) or start Blender from a terminal.
Look for log entries starting with [Blaze].
Include these logs and any error codes when reaching out at blazeanimation.com.