A dash can look correct in Blender and travel the wrong distance in a game because both the animation and gameplay code move the character. Decide who owns displacement before debugging the exported clip.
State the movement contract
For an in-place clip, gameplay determines travel while animation communicates the motion. For a root-motion workflow, the game consumes movement from the animation according to the engine setup. The important part is a clear contract, not a universal preference.
Record the intended root bone or object, forward direction and how the game handles collisions and interruption. These details matter more than the name of an export preset.
Test one short action in isolation
Import a single dash into an empty test scene. Observe the character with gameplay movement disabled, then enable the intended movement system. Watch for double travel, a stationary collision body or a visual mesh that snaps back at the end.
Compare the clip’s start and end transforms and test an interruption midway through. A dash that works only when it finishes uninterrupted may not meet your game’s needs.
Verify loops and transitions separately
Blend into idle or locomotion and inspect orientation and position at the boundary. Check that the chosen root convention remains consistent across clips.
Save a short implementation note with the asset so another developer does not add code movement on top of consumed animation movement. Treat the final game behavior as the acceptance test.
For the bigger picture, use our free Rigify migration workflow and three-engine import test plan.
Official references and scope
Sources checked October 18, 2026. Interface names and capabilities can change; use the documentation for your installed version. The workflow above is an editorial checklist, not a published hands-on benchmark.

