Overview

Blaze Puppeteer

Rig-aware motion generation for Blender with local Kimodo generation, anchor-driven inbetweening, path guides, and optional account-backed prompt embeddings and refinement.

Read These Pages In Order

1. Install and prepare the local runtime. Start with Installation to install the extension, choose the panel location, and run Prepare Runtime.
2. Teach Blaze Puppeteer your rig. Use Rig Setup to fill the five chain lists, choose Root Controller or No Root Controller, then run Reconstruct and finish the T-pose pass.
3. Generate your first motion. Use Quick Start for the shortest first-generation workflow, then Motion Generation for the full Motion panel reference.
4. Clean up or branch the result. Use Post-Processing for root extraction and unbaking, and Troubleshooting whenever the panel state or the result does not match what you expected.

What You Can Do In Motion Mode

• Start with the bundled 125-preset Kimodo library or switch to Custom Prompts after signing in.
• Use Inbetweening, Text to Motion, Waypoint, or Dense Path as the active task.
• Guide motion with Anchors, Prompt Sequencer, Waypoints, and Dense Path.
• Compare results in History, then run Motion Refinement when you want a variation, a different length, or a loop.
• Keep cleanup non-destructive with Extract Root Motion, Extract Rotation, Ground Tracking, and Unbaking.

Getting Started

Quick Start

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

Fastest Local Path

1. Install the extension. Confirm the Blaze Puppeteer panel is visible in Blender.
2. Prepare the local runtime. Run Prepare Runtime and wait until Local generation shows GPU or CPU readiness.
3. Set up the rig. Switch to Rig Setup, choose 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.

When To Sign In

An account is useful when you want Custom Prompts instead of the local preset library, Motion Refinement on an existing generated motion, or credit, purchase, and account actions inside the Motion panel. If you plan to stay on Preset Prompts, you do not need to sign in.

First-Generation Checklist

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.

Getting Started

Installation

Blaze Puppeteer installs as a Blender extension, but the extension alone is not enough. Motion generation depends on the local runtime being prepared on the same machine where Blender is running.

What You Are Setting Up

System Requirements

Blender version: 4.2 or newer.

Step 1: Install The Extension

1. Download the current Blaze_Puppeteer.zip build from your order page on Superhive Market.
2. Open Blender Preferences from Edit > Preferences.
3. Drag the zip file into Blender, or open Get Extensions, open the top-right menu, choose Install from Disk, and select the zip file.
4. Confirm the extension is enabled, then select an armature in your scene and open the Blaze Puppeteer panel. You may need to disable and re-enable the extension to see the panel.

Step 2: Choose Your Basic Preferences

Step 3: Prepare The Local Runtime

• Open the Motion panel and use the readiness box, or open the add-on preferences.
• Click Prepare Runtime.
• If a previous setup was interrupted or damaged, use Repair in the Motion panel or Repair Runtime in preferences.

During setup, Blaze Puppeteer resolves the bundle that matches your platform and Blender Python version, installs shared Python dependencies plus torch, installs the bundled MotionCorrection wheel, validates the Kimodo model bundle, and selects the best provider available on your machine.

Step 4: Confirm Readiness

The Motion panel also needs Rig Setup: Ready before you can generate against a character. Runtime readiness and rig readiness are separate checks.

Updating Blaze Puppeteer

1. Remove the current extension from Blender.
2. Restart Blender fully.
3. Install the new zip.
4. Open the add-on preferences and confirm the Local generation line still shows a ready label.

Getting Started

Rig Setup

Rig Setup is where you assign rig controllers of different chains in a specific order. You do this once per rig.

Chain Order

Step-By-Step Setup

1. Choose the correct character in Target Armature.
2. Leave Auto Mirror on unless the rig is asymmetrical. When Auto Mirror is enabled, adjustments to one side are mirrored to the other side.
3. Fill the five chain lists. Use Add Selected after selecting bones in Pose Mode, or REC to capture bones one by one in the order you select them.
4. Set Root Controller or No Root Controller. Blaze Puppeteer blocks reconstruction until one of those two choices is made.
5. Click Reconstruct. This rebuilds the helper rigs from your current lists and immediately moves into T-pose calibration.
6. Confirm the T-pose. Adjust the pose so the arms are extended horizontally and legs are straight. Use Confirm Front View first, then check the top view and use Finalize T-Pose.

What Reconstruct Creates

After the T-pose workflow is finalized, Blaze Puppeteer hides the helper collection so your scene stays cleaner. Treat these helpers as internal assets.

Root Controller vs No Root Controller

Ready For Motion When

1. Every required chain has at least one entry.
2. The list order reads correctly through the body.
3. Your Root Controller or No Root Controller choice is set.
4. The T-pose workflow is finished.
5. Motion mode reports Rig Setup: Ready.

Guides

Motion Generation

The Motion tab is where you set prompts, add guides, generate motion, review History, and optionally run Motion Refinement or PostPro.

Read The Panel From Top To Bottom

Choose A Prompt Mode

Pick A Task

Text to Motion

Use Text to Motion when you want to start a new clip from a preset or custom prompt.

Inbetweening And Anchors

Use Inbetweening when you want to block important poses and let Blaze Puppeteer fill the motion between them. Anchors are the guide poses Blaze Puppeteer actually uses during inbetweening. Regular keyframes do not become anchors until you mark them.

The anchor editor includes current-frame add/remove, Clear Anchors, Badges for timeline indicators, and Ghost visual indicators of anchored poses in the 3D Viewport. Shortcuts: F toggles the current-frame anchor using the active anchor scope. D creates or removes a manual hands-and-feet anchor in most animation editors; in the Sequencer, D is reserved for prompt strips.

Prompt Sequencer

1. Turn on Multi-Prompt with the three-dot toggle next to the prompt field.
2. Open the Sequencer helper with Prompt Sequencer.
3. Press D to create a Blaze Puppeteer prompt strip at the current frame.
4. Press E to edit the prompt text at the current frame.
5. Move or trim strips with normal Sequencer tools. Avoid overlapping strips because that may cause unexpected results.

Waypoints

• Click Place to enter waypoint placement mode.
• Left-click in the 3D Viewport to place a waypoint at the current frame.
• Right-click or press Esc to leave placement mode.
• If a waypoint already exists on that frame, the new click replaces it.
• When Waypoint is not the active task, enable Use Waypoints if you want placed waypoints layered onto another task.

Dense Path

1. Click Draw.
2. Sketch the path in the viewport with the Annotation tool Blaze Puppeteer activates for this mode.
3. Right-click or press Esc to finish and convert the stroke into an editable curve.
4. Use Edit to adjust the curve later. When Dense Path is not the active task, enable Use Dense Path to layer the trajectory curve onto another task.

Combining Tasks

History And Motion Refinement

Motion Refinement only appears when you are logged in and a generated History action is selected. Variation requests alternate versions of the selected source motion. Extend/Shorten fits it to a new duration. Loop makes it loop. Refinement works from the selected History entry only and does not read the current anchors, waypoints, prompt text, prompt strips, Dense Path, or current task setup.

Seed, PostPro, And Advanced

Before You Click Generate

1. The readiness area shows Rig Setup: Ready and a working Local generation label.
2. Your guides match the active task: anchors for Inbetweening, prompt and timing for Text to Motion, waypoints for Waypoint, or a dense path for Dense Path.
3. The prompt mode, prompt content, and timing match the motion you want.
4. The active armature is the character you intend to animate.

Generate runs the current setup. Retry reuses the last cached generation setup to create another generated motion. Cancel only appears while generation is running.

Guides

Account And Remote Features

An account is optional until you need Custom Prompts, Motion Refinement, or account actions such as refreshing credits and opening the purchase flow.

What Login Unlocks

Without Login vs With Login

The Account Bar

If you sign out while Custom Prompts is active, Blaze Puppeteer returns the prompt mode to Preset Prompts.

Browser Login Flow

1. Click Login in the Motion panel account bar.
2. Finish sign-in in your browser. Blaze Puppeteer does not ask for your password inside Blender.
3. Return to Blender. Once the session is confirmed, the account bar updates automatically.

Data Boundaries

Guides

Post-Processing

Post-processing is where you adjust generated motion without running generation again.

Root Extraction

Root extraction is only available when Rig Setup includes a real Root Controller. If the rig was set up with No Root Controller, Blaze Puppeteer can still generate motion, but separate root extraction controls do not appear.

Root extraction helps with shots that need cleaner locomotion on the root control, export pipelines that expect movement on a root controller, and review passes where body motion should be separated from larger trajectory changes.

Unbaking

Generated motion usually arrives with baked keyframes. Unbaking simplifies the curves and reduces keyframes without affecting the motion.

How PostPro Relates To History

• New generated motion receives the PostPro settings active at creation time.
• Selecting another History action restores that action's own cleanup state.
• Retry and refinement results also keep their own saved PostPro state.
• Cleanup is part of evaluating each generated motion, not a single global setting for the whole rig.

A Good Review Order

1. Watch the raw motion first.
2. Test Extract Root Motion first if the motion contains trajectory changes.
3. Turn Unbaking on and compare Low, Mid, and High on the same motion.
4. Keep, retry, or branch based on the cleaned result.

Reference

FAQ

Common questions about Blaze Puppeteer, local generation, credits, rig setup, motion controls, limitations, and Kimodo.

Local, Login, And Credits

Rig Setup FAQ

• Does it retarget motion? No. Blaze Puppeteer is not a retargeting workflow. You run Rig Setup once, then generated motion is transferred back onto that character's own rig controls.
• Which rigs work? Rigify, Auto-Rig Pro, CloudRig, Mixamo, Blender Studio rigs, and custom rigs can work when the required controller chains are mapped correctly.
• Do I need a root controller? No. Enable No Root Controller if the rig does not have one. Generation still works, but Root Extraction needs a root controller to write into.
• What helper rigs are created? Rig Setup creates YourRig_Blazed for generation/source skeletal data and YourRig_TPOSE for calibration.

Limits And Best Practices

• Each generated motion can be up to 10 seconds. Split longer actions into multiple generated segments or Prompt Sequencer strips.
• Keep constrained frames under 20 per constraint type, excluding Dense Path root trajectory guidance.
• Use direct, medium-detail prompts that describe one clear behavior, or at most two closely related behaviors.
• Avoid contradictory prompts, Anchors, Waypoints, or Dense Path curves.
• Finger animation is not generated. The model focuses on full-body motion.

Kimodo

Kimodo is NVIDIA's kinematic motion diffusion model for controllable human and humanoid motion generation. Blaze Puppeteer uses Kimodo concepts inside a Blender addon workflow and transfers motion back onto your rig controls. For underlying model concepts, see NVIDIA's Kimodo documentation and Best Practices.

Reference

Troubleshooting

Use this page when the panel does not look ready, the local runtime will not prepare, or a generated result is not reacting to the guides you authored.

Setup And Readiness

• No armature selected: Pick the character in Target Armature first.
• Rig not configured or Rig setup incomplete: Confirm all five required chains have entries, the chain order is correct, Root Controller or No Root Controller is set, and the T-pose workflow is finished.
• Reconstruction needed: Blaze Puppeteer cannot find the helper rigs it expects. Run Reconstruct again.
• Bone lists changed since last reconstruction: Use Reconstruct if the new lists are right, or Restore if you want to return to the previous reconstructed state.

Local Runtime

• Local generation: checking... Normal for a short time. If it never settles, reopen Blender and check the same status line in the add-on preferences.
• Local generation: setup required The runtime has not been prepared yet. Run Prepare Runtime.
• Local generation: unavailable Possible causes include unsupported platform, interrupted dependency install, missing runtime files, or damaged model files. Use Repair or Repair Runtime first.
• Prepare or Repair fails Check internet access, free disk space, security software, and whether Blender was restarted after installing a fresh build.
• Local generation is slow If the status line settles on CPU, the workflow still works but will be slower.

Account And Remote Features

• Login does not complete: Check that the browser flow finished successfully, Blender still has network access, and Blender can save the returned sign-in session.
• 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 require both a valid login session and a ready local runtime.
• Motion Refinement is missing: Refinement only appears when you are logged in and a generated History action is selected.

Authoring Problems

• Anchors are not shaping the result: Confirm blocked keyframes were turned into anchors, important start and end moments are anchored, and 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 and strips were created through Blaze Puppeteer's Sequencer workflow.
• Waypoints are ignored: Waypoints affect the result when Waypoint is the active task or Use Waypoints is enabled while another task is active.
• Dense Path is ignored: Dense Path affects the result when Dense Path is the active task or Use Dense Path is enabled on another task.
• Animation Restrictions Detected: Blaze Puppeteer found important controls with locked transforms or driven channels. Use the dialog to choose Override All or Skip Restricted.

History And Action Issues

• Generated motion exists in History but the rig does not move: Re-select the generated motion from Blaze Puppeteer History first, then inspect Blender's Action Editor if needed.
• History is cluttered: Use Remove Selected for one entry, Remove Family for a whole branch, Purge Derived to keep the base generation and drop retries/refinements, or Clear Armature to wipe 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. On Windows, use Window > Toggle System Console. On Linux or macOS, start Blender from a terminal.

When contacting support, include the exact message shown in the panel, what task you were running, whether you were using presets, Custom Prompts, or refinement, and the relevant console lines.