Quick Start

Use this page to confirm the core workflow end to end: install the extension, let the bundled runtime install automatically, map one rig, and generate a first motion with Preset Prompts.

Prepare Once

Install the extension, choose the panel location you want, and let Blaze Puppeteer install the bundled runtime automatically. Nothing else in Motion mode matters until the local runtime is ready.

Map Once Per Character

Rig Setup is a character-specific pass. Once the chain lists, root decision, and T-pose are correct, you normally only revisit it when the rig changes.

Review Per Generation

Generate, compare results in History, then keep the best result, retry, or clean it up with PostPro.

First launch reference

Pick Your Starting Path

Fastest Local Path

This is the shortest route to a first result and the clearest way to confirm that both your machine and your rig are ready.

1. Install the extension

   Follow Installation and confirm the Blaze Puppeteer panel is visible in Blender.

2. Let the runtime finish installing

   After installation, wait until the readiness area shows a usable Local generation: label such as GPU (Torch CUDA) or CPU (Torch).

3. Set up the rig

   Switch to Rig Setup, choose the correct Target Armature, fill the five body chains, choose Root Controller or No Root Controller, and click Reconstruct.

4. Finish the T-pose

   On the generated _TPOSE helper rig, use Confirm Front View, then switch to the top check and use Finalize T-Pose.

5. Generate your first motion

   Switch to Motion, stay on Preset Prompts, choose a preset, choose the task you want to test, add only the guides that task needs, and click Generate.

6. Review and polish

   Review the result in History. If the generated motion is close, open PostPro for root extraction or unbaking. If it is not close, change the setup and generate again.

First successful run

When To Sign In

An account is helpful when you want:

• Custom Prompts instead of the local preset library.
• Motion Refinement on an existing generated motion.
• Credit, purchase, and account actions inside the Motion panel.

If you plan to stay on Preset Prompts, you do not need to sign in.

Generations are always local

Signing in does not replace local generation. Blaze Puppeteer still runs the actual generation locally after it fetches remote text embeddings for Custom Prompts or transmits skeletal motion data for Motion Refinement.

See Account & Remote Features for the full login and data-boundary guide.

First-Generation Checklist

Before you judge the result, confirm these basics:

1. The correct character is selected in Target Armature.
2. The readiness area shows Rig Setup: Ready and a working Local generation: label.
3. The selected task matches the guides you actually set.
4. If you are using Inbetweening, the start and end poses are really marked as anchors.
5. You review the generated motion in History before changing the setup.

Start simple

For a first baseline test, use a short range, a clear idle or locomotion preset, and as few guides as possible. Add Prompt Sequencer, Waypoints, or Dense Path after the baseline run works.

First run reference