What this workflow does
The generator turns a written action into a humanoid motion draft that you can preview in the browser and download as an FBX animation or JSON motion data. It supplies movement only. Your mesh, your texture, your rig, and your scene stay exactly where they are, and nothing is overwritten. Think of the result as blocking that arrives in seconds: something an animator can accept, edit, or throw away without booking a stage.
Get the character ready first
Before prompting, open the character and note the skeleton type, the rest pose, the unit scale, the forward axis, and how the root bone is named. Any mismatch between those details and the draft creates visible work later: an enormous or microscopic import, a character facing sideways, or a rig that refuses to map at all. Decide whether the controller or the animation should carry forward travel. A checklist now saves a retarget pass longer than keying the shot by hand.
Write one action per prompt
Prompts work best when they read like a stage direction. Name the performer, then the beats in order, then the direction, then the tempo, then the finish. For example: a person walks three steps, stops, turns to the right, and settles into a relaxed stance. Vague requests such as cool walking produce equally vague timing. Keep the description under roughly sixty words and keep it to one person, because the model is built around a single humanoid action and cannot stage partners, props, or camera moves.
Use Fast as a gate, then Standard
Treat the two modes as a gate rather than a lottery. Fast spends fewer credits, so use it to test whether the action order, direction, and ending pose are readable. Write the pass criteria down before generating: the beats must appear in sequence, the turn must be obvious, and the final pose must be stable. If a draft misses those, rewrite the prompt instead of paying for a stronger mode. Only a draft that already reads should be regenerated in Standard for a cleaner review clip, which gives every credit a specific question to answer.
Retarget, then clean up
Import a downloaded file into a scratch scene rather than the working project. Map bones to your skeleton, check frame rate and unit scale again, and watch the feet for sliding and the hips for unwanted drift. Decide whether root travel belongs on the clip or on the controller, then trim or blend the first and last poses so the movement can transition into neighboring states. JSON suits a technical artist who wants to inspect channels, timing, or rotation values before importing. Keep the untouched original beside a note of prompt, mode, seed, and date.
Where it stops being useful
This generator does not rig a character, does not build a face rig, and does not animate eyes, lips, fingers, or dialogue. It cannot hand a prop to a partner, react to a collision, or honor a camera framing, and it does not promise seamless loops or true in-place playback. Output is a draft, so budget review and cleanup time before a clip reaches a milestone build. For signature performances, close contact between characters, or movement that must carry the identity of a specific performer, plan a capture session or hand animation and use the draft as reference instead.