Skip to content

Troubleshooting

Most AutoPose problems announce themselves in the status line at the top of the panel. Read it first - it usually names the fix.

An error status in the panel with its action buttons
An error status
a red status box offering Save Support Bundle and Report a Bug.

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.

Nine problems out of ten come down to one of these five things. Check them in order before digging further.

  1. Character Rig at the top of the panel decides what everything else applies to.

  2. Open Rig Setup → 2. Review Controller Mapping. A chain that reads Needs attention says exactly what is wrong underneath it.

  3. Step 3 of Rig Setup should say so. If it says Controller mapping changed, reconstruct.

  4. Cancelled T-pose setup means no reference pose. Reconstruct and complete both stages.

  5. In Manual Pose nothing solves. The panel says so plainly and offers a button back.

”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””

A direct read-only link cannot be posed. In 1.1.0, editable library overrides are supported: create an override for the linked character and select its armature in the panel. See Linked Characters.

If AutoPose reports that the linked rig’s rest structure changed after an asset update, run Reconstruct AutoPose Rig to update the setup.

The panel lists why underneath Before reconstructing:.

MessageFix
Map: …Those chains are still empty. Fill them, or apply a preset.
Finish controller recordingA REC button is still on. Turn it off.
MessageMeansFix
No controllers assignedThe chain is emptyFill it with +, REC, or a preset
Missing: …A mapped name no longer exists on the rigThe bone was renamed or removed. Remap that entry
Duplicate: …The same controller appears in more than one chainRemove it from all but the correct chain

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.

The helper rigs do not exist for this character yet. Open Rig Setup and run Reconstruct AutoPose Rig.

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.

Is the session running?

The big button at the bottom should read Finish AutoPose. If it reads Start AutoPose, press it.

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.

Too many active constraints can restrict the pose. AutoPose has 16 constraint slots, with Rotation using two; every active constraint reduces how freely the body can adapt.

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.

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.

AutoPose 1.1.0 ends the session when you leave Pose Mode and keeps the current pose. Press Start AutoPose to resume.

Check the FK toggle beside Manual Pose. With FK off, AutoPose restores the rig’s existing manual pose instead of transferring the visible result. Leave FK on to carry that result into Manual Pose. Before returning from IK posing, snap to FK and activate the rig’s FK controls.

Rig controls do not work after switching to Manual Pose

Section titled “Rig controls do not work after switching to Manual Pose”

Update to AutoPose 1.1.1 and restart Blender. This version restores the temporary rig locks, drivers, and constraints used during an AutoPose session, including when saving, reopening, or recovering a scene.

If an older version already changed those settings and you saved the file, AutoPose cannot determine what their original values were. Start from an untouched copy of the rig, then use version 1.1.1 or newer.

Undo or Redo crashes, or changes the pose unexpectedly

Section titled “Undo or Redo crashes, or changes the pose unexpectedly”

Update to AutoPose 1.1.1 and restart Blender. This release fixes Undo/Redo crashes and unexpected pose changes while AutoPose is active.

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:

  1. Preserve Foot Contact has to be on.

  2. The foot’s row should read Contact, not Free or Released. Press its Contact button to include it in ground support.

  3. 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.

”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.

If none of the above covers it:

  1. Preferences → Add-ons → Blaze AutoPose → Support → Debug Logging.

  2. Do the same thing again, so the detail lands in this session’s log.

  3. 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.

  4. 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.