Getting a dance to play on a second character is a rig-compatibility problem. A file extension and a clean model import don't prove the animation will retarget. Start with an inspected source asset, identify the target skeleton, and agree on what successful playback looks like. mvntSTUDIO currently offers GLB for eligible 3D downloads; BVH and FBX exports are planned.
This checklist prepares a file-based animation handoff to Unity or Unreal Engine. It doesn't cover a native MVNT connector, and it doesn't assume an arbitrary GLB becomes an engine-ready Humanoid clip. For product context, see the Unity and Unreal overviews. This page covers what the animator and engine developer should agree on.
Establish three separate milestones
First, verify the asset: does the downloaded file contain the expected mesh, skeleton, and motion? Second, verify the import: does your toolchain preserve those contents in the destination project? Third, verify the retarget: does the source motion drive the target rig with acceptable contacts and travel? Passing one stage says nothing about the next.
Inspect the GLB in Blender before you choose an importer or a conversion, and document its skeleton hierarchy, rest pose, clip range, units, and facing direction. Any package or DCC conversion you add is another toolchain decision: record its version and check what it imports. Unity's glTFast feature matrix, for example, notes that Mecanim-compatible clip playback needs extra work, so don't expect a GLB to drop straight into an Animator Controller. An FBX you export from Blender is your own conversion, not the planned native MVNT FBX export.
Unity: decide whether reuse needs Humanoid
Unity's animation system documentation distinguishes Humanoid and Generic animation. Humanoid retargeting maps a skeleton to Unity's humanoid definition through an Avatar. Generic animation keeps its own hierarchy and offers no cross-character humanoid mapping. Choose based on how you actually need to reuse the clip.
For Humanoid, validate both the source and target Avatars: check the required bone assignments and the rest pose instead of accepting the automatic mapping unseen. Unity's Avatar configuration guide walks through this. A valid Avatar is necessary but not sufficient; a clap or a hand-on-hip pose can still look different on characters with different proportions.
Agree whether the dance should move the character object or stay in place. Unity offers per-clip root transform settings and Animator root motion; use its root motion documentation to match your gameplay or cinematic setup. Judge turns and travel in the scene, not just in the import preview.
Unreal: define source and target chains
Unreal's IK Rig retargeting documentation transfers animation between skeletons with IK Rigs and an IK Retargeter. Define matching chains on the source and target rigs, set the retarget root, and check the chain mapping and retarget pose. Importing a file doesn't do this setup for you.
Choose the import route and the retarget route separately. Unreal's glTF support documentation covers format support, not a promise that every GLB yields the skeletal animation assets your project needs, so confirm the behavior for your engine version and importer. Epic's Datasmith import process supports object-transform animation but excludes skeletal-rig animation: the Level Sequence it produces is not the Skeletal Mesh and animation asset that IK retargeting needs.
Review the result in the IK Retargeter and in the actual sequence or runtime context. Check the feet, hands, pelvis height, and major turns. When proportions differ, decide which contacts matter most for the shot. Don't fix one mismatch by quietly changing the whole motion or moving the gameplay character unexpectedly.
Shared acceptance matrix
| Boundary | Evidence to save | Acceptance question |
|---|---|---|
| Source file | Untouched GLB and inspection notes | Are skeleton and animation actually present? |
| Import | Tool versions, conversion settings, imported assets | Was the intended clip preserved? |
| Rig mapping | Avatar or IK Rig/Retargeter configuration | Are required mappings and poses valid? |
| Root behavior | In-place or traveling decision | Does the object move as intended? |
| Contact review | Problem timestamps and comparison views | Are feet and hand contacts acceptable? |
| Playback | Scene or runtime setup and clip range | Does the intended target character play the full section? |
For cross-character reuse, review a second target character at representative moments. Log corrections by timestamp and severity so the animator can tell a broken mapping from an artistic cleanup request. Keep the original source and any intermediate converted asset for diagnosis.
Frequently asked questions
Can I skip rig setup because the file is GLB?
No. Importing a file, supporting skeletal animation, and retargeting are separate capabilities. Check the actual asset and your engine toolchain.
Should I wait for the planned MVNT FBX or BVH exports?
Plan with the current GLB. Native FBX and BVH exports are planned but have no release date, so don't build a deadline around them.
Sources and next step
For implementation details, see Unity Avatar configuration, Unity root motion, and Unreal IK Rig retargeting. To start, create a draft in Studio and run it through the GLB inspection guide before sharing an engine handoff.
Workflow and references reviewed October 7, 2026.
