Is the session running?
The big button at the bottom should read Finish AutoPose. If it reads Start AutoPose, press it.
Troubleshooting
Most AutoPose problems announce themselves in the status line at the top of the panel. Read it first - it usually names the fix.
When a status is an error, the panel turns it into a red box with two buttons: Save Support Bundle to capture a report at the moment it happened, and Report a Bug to open the Blaze creator page on Superhive, where you can send a message.
Start Here
Section titled “Start Here”Nine problems out of ten come down to one of these five things. Check them in order before digging further.
-
The right character is selected
Section titled “The right character is selected”Character Rig at the top of the panel decides what everything else applies to.
-
Every chain reads Valid
Section titled “Every chain reads Valid”Open Rig Setup → 2. Review Controller Mapping. A chain that reads Needs attention says exactly what is wrong underneath it.
-
The AutoPose rig is synchronized
Section titled “The AutoPose rig is synchronized”Step 3 of Rig Setup should say so. If it says Controller mapping changed, reconstruct.
-
The T-pose was actually finished
Section titled “The T-pose was actually finished”Cancelled T-pose setup means no reference pose. Reconstruct and complete both stages.
-
You are in AutoPose, not Manual Pose
Section titled “You are in AutoPose, not Manual Pose”In Manual Pose nothing solves. The panel says so plainly and offers a button back.
Setup Problems
Section titled “Setup Problems””Choose a Character Rig above to begin”
Section titled “”Choose a Character Rig above to begin””No armature is selected. Pick one in Character Rig.
”This rig cannot be set up by AutoPose”
Section titled “”This rig cannot be set up by AutoPose””The character is linked from another file or is a library override. Rig Setup writes properties onto the armature and builds sibling rigs, and neither works on a datablock owned by another file.
Use Object → Library Override → Make Local to make the rig fully local, then reopen the panel. The panel lists which specific part is linked - the object, its armature data, or both.
Reconstruct is greyed out
Section titled “Reconstruct is greyed out”The panel lists why underneath Before reconstructing:.
| Message | Fix |
|---|---|
| Map: … | Those chains are still empty. Fill them, or apply a preset. |
| Finish controller recording | A REC button is still on. Turn it off. |
A chain says “Needs attention”
Section titled “A chain says “Needs attention””| Message | Means | Fix |
|---|---|---|
| No controllers assigned | The chain is empty | Fill it with +, REC, or a preset |
| Missing: … | A mapped name no longer exists on the rig | The bone was renamed or removed. Remap that entry |
| Duplicate: … | The same controller appears in more than one chain | Remove it from all but the correct chain |
”No matching rig preset found”
Section titled “”No matching rig preset found””Auto Detect could not recognise the rig from its bone names. That is not a failure of the rig - it just is not one of the known families. Choose a preset manually if you know which family it is, or map the five chains by hand.
Reconstruct asks about locked or driven controllers
Section titled “Reconstruct asks about locked or driven controllers”This is expected on rigs that lock transform channels or drive them from other controls. Continuing unlocks the mapped channels and mutes their drivers so AutoPose can write a pose; cancelling leaves the rig untouched. Only the controllers in your five chains are affected.
Session Problems
Section titled “Session Problems””AutoPose rig is not ready”
Section titled “”AutoPose rig is not ready””The helper rigs do not exist for this character yet. Open Rig Setup and run Reconstruct AutoPose Rig.
”Controller mapping changed”
Section titled “”Controller mapping changed””The mapping and the helper rigs no longer agree, usually because a chain was edited after reconstruction. Press Reconstruct AutoPose Rig. It is safe and keeps the T-pose you already confirmed.
The handles are not showing up
Section titled “The handles are not showing up”Are they hidden?
Press Alt + H to bring back every hidden AutoPose handle, or use the show-all button in the Constraint Manager.
Are they too faint?
Raise Constraint Opacity and Constraint Size under Preferences → Viewport Controls.
Are they behind the mesh?
Turn off Mesh-aware Occlusion to draw every handle at full strength regardless of what is in front of it.
The pose feels stiff, or barely moves
Section titled “The pose feels stiff, or barely moves”Too many active constraints. AutoPose allows up to 16, but every active constraint reduces how freely it can adapt the rest of the body.
Press Clear. It deactivates every constraint without changing the pose you already have, and you can start placing them again from there. Aim for three or four.
A drag went somewhere I did not want
Section titled “A drag went somewhere I did not want”Press RMB while still dragging to cancel it, Ctrl + Z to undo the last AutoPose change, or Restore to return to the saved checkpoint.
”The world control does not condition the solve”
Section titled “”The world control does not condition the solve””You tried to activate or deactivate the world control. It moves the whole character in the scene rather than telling AutoPose anything about the pose, so those states do not apply to it.
Foot Contact Problems
Section titled “Foot Contact Problems”The foot moves more than expected
Section titled “The foot moves more than expected”Preserve Foot Contact does not lock a foot in place. A foot in Contact is considered planted, but the condition is soft. AutoPose balances it with the rest of the pose and any other active constraints, so a small amount of sliding or lifting can be normal.
If the movement is larger than expected, check the following:
-
Check the toggle
Section titled “Check the toggle”Preserve Foot Contact has to be on.
-
Check the state
Section titled “Check the state”The foot’s row should read Contact, not Free or Released. Press its Contact button to include it in ground support.
-
Check the plane
Section titled “Check the plane”Turn on Show Ground Plane under Ground Settings and confirm it is at the height you think it is. Fit Ground puts it under the lowest foot.
”Foot contact fitted, but no foot touches the ground plane”
Section titled “”Foot contact fitted, but no foot touches the ground plane””The plane was placed, but neither foot is within the contact tolerance of it. Either press Fit Ground to snap the plane to the lowest foot, or raise Contact Tolerance under Ground Settings.
Recording And Keying Problems
Section titled “Recording And Keying Problems””Start AutoPose before recording solves”
Section titled “”Start AutoPose before recording solves””Recording captures live solves, so a session has to be running first.
”Finish the active transform before baking”
Section titled “”Finish the active transform before baking””A drag is still in progress. Release the mouse, then stop the recording.
The panel buttons are greyed out mid-recording
Section titled “The panel buttons are greyed out mid-recording”That is deliberate. Copy Pose, Paste Pose, Clear, Restore, Set Base, and switching to Manual Pose are unavailable while a take is recording or baking. Let the bake finish.
A keyed pose does not come back the way I left it
Section titled “A keyed pose does not come back the way I left it”Check that you are on the exact frame you keyed. AutoPose stores the constraint state alongside the keyed pose, so returning to the frame should restore both. If the pose is right but the constraints are not, the frame is probably one off.
Reporting A Problem
Section titled “Reporting A Problem”If none of the above covers it:
-
Turn on Debug Logging
Section titled “Turn on Debug Logging”Preferences → Add-ons → Blaze AutoPose → Support → Debug Logging.
-
Reproduce the problem
Section titled “Reproduce the problem”Do the same thing again, so the detail lands in this session’s log.
-
Save a support bundle
Section titled “Save a support bundle”Press Save Support Bundle. It writes one text file with the version, your device, the rig setup summary, the recent status messages, and the tail of the log.
-
Send it
Section titled “Send it”Attach the file to your report. If you cannot share your scene’s naming, turn off Include Object Names in the save dialog and the report uses anonymous tokens instead.