Get started

Use a MiniMax H3 motion clip as an Unreal reference
Separate the video reference from the animation you ship.

Plan a MiniMax H3 video-to-video motion reference for an Unreal character. Specify the source action, camera, and timing, then review the clip for contact and continuity before building or retargeting animation in your project.

Get started with
  • Free starter credits
  • No coding required
  • Review cost before generating
  • Runs in your browser

How it works

From motion clip to Unreal review

Choose one action, inspect the video, and plan the engine checks required for the character.

  1. Choose the action
    A bright spark representing the start of a game idea

    Pick one continuous movement

    Use a short source segment that shows the start, contact, and finish.

  2. Prepare the shot
    A prompt being written to describe a game idea

    Keep the subject and feet visible

    Avoid cuts, occlusion, and camera moves that hide the motion.

  3. Describe the change
    Game components assembled into a playable world

    Say what should stay and what should move

    Keep the action order explicit and avoid changing several scene details.

  4. Review the clip

    The game could not be loaded.

    Check contact, timing, and drift

    Compare the output against the source and flag visible mismatches.

  5. Plan Unreal work

    Test the motion on the project character

    Confirm skeleton, root motion, graph, collision, and camera behavior in the actual build.

Pick a starting point

Choose the motion question to solve

Work on the source shot, movement timing, Unreal handoff, or gameplay validation.

Choose a clean reference moment

Use one continuous action with the subject and contact points in view.

Prompt

Prepare a motion-reference brief for a single performer turning, taking two steps, and pointing toward a doorway. Keep the camera fixed, show the full body and feet, and avoid cuts or another person crossing the frame. State what should remain unchanged in the scene and what part of the movement the video reference is meant to convey.

  • Single continuous action
  • Full body and feet visible
  • Camera stays fixed
Editorial motion-study concept showing a character pose sequence, joint landmarks, and trajectory cues for Unreal animation validationChoose a clean reference moment ↗

Why SEELE

What to inspect in a motion reference

Choose a reference with visible contact

Keep the subject, feet, and interaction point inside one continuous shot.

Preserve the camera and scene

A steady view makes it easier to compare the source action with the generated clip.

Review timing and body motion

Look for foot sliding, missed contact, pose drift, and changes in action order.

Keep video and skeletal animation distinct

A motion-transfer clip is visual reference; it does not establish a retargeted Unreal animation asset.

Plan the engine checks explicitly

List skeleton mapping, root motion, animation graph, and collision questions for the project.

Validate the result in gameplay

Check the motion with the project character, camera, controls, and movement rules.

Who it’s for

Who can use a MiniMax H3 motion reference

A concise handoff lets animators and technical artists separate visual reference from engine work.

Compare

Keep the video reference separate from engine animation

MiniMax H3 produces video; an Unreal animation asset requires a separate, verified workflow.

FeatureA reviewed motion-reference workflowA video output assumed to be an Unreal animation
InputOne clear action with full-body contact visibleA crowded clip with cuts and hidden feet
Motion transferA video reference whose scene and action are reviewedAn assumed direct skeleton or animation export
Unreal handoffSkeleton, root motion, and animation graph checked in projectA video clip treated as an engine-ready asset
ValidationContact, timing, and movement tested with the project characterVisual resemblance treated as proof of gameplay fit
ScopeOne motion segment and a defined review questionA long sequence with several changing actions

Reviews

Creator videos about SEELE AI

Watch creator videos about SEELE AI and confirm current editor options before relying on a specific capability.

FAQ

MiniMax H3 Unreal workflow questions

What does MiniMax H3 video-to-video motion transfer provide?

MiniMax describes H3 as a multimodal video model with video-to-video motion transfer. Treat the result as a video clip and verify its movement before using it as a reference.

Does MiniMax H3 export an Unreal animation asset?

The official H3 material describes generated video, not a retargeted Unreal skeletal animation file. Plan a separate animation handoff and test it on the project skeleton.

What makes a good motion-reference clip?

Choose one continuous action with the full body, feet, and contact point visible. A fixed camera and uncluttered background make the movement easier to inspect.

Can I transfer motion from a real performer?

Use footage you have permission to use and check the model provider’s terms. Keep identity and likeness rights in mind when the performer is recognizable.

What should I specify in a motion-transfer prompt?

Name the source action, what should stay consistent, what movement should change, and how the result will be reviewed. Avoid combining several actions in one pass.

How do I check foot sliding?

Compare foot contact with the source timing and watch the character against the floor. Then test the movement with the target rig and Unreal movement settings.

What does root motion mean for an Unreal handoff?

Root motion controls whether character movement comes from the animation or from gameplay code. Decide how the project handles it and test the chosen setup in Unreal.

Can a video clip be retargeted directly to my character?

A rendered video is not itself a skeletal animation to retarget. Any conversion or reconstruction step needs its own tools and validation.

Which Unreal checks should follow a motion reference?

Review skeleton compatibility, pose, foot and hand contacts, root motion, animation graph behavior, collision, and the gameplay camera.

Does motion similarity guarantee the animation will work in a game?

No. Visual similarity does not confirm timing, collisions, control response, or compatibility with the project skeleton. Test the animation in the playable build.

Can I use a reference with camera cuts?

A single continuous shot is easier to evaluate. If a clip contains cuts, separate the actions and specify which segment should guide the motion.

How long should the source action be?

Keep the reference to the shortest segment that shows the action and its contact. Check the current MiniMax H3 input limits before preparing a clip.

Can I use MiniMax H3 inside SEELE AI?

This page does not establish a MiniMax H3 integration in SEELE AI. Check the current Workspace options and use the video model through a supported provider workflow.

What should I document for an animation handoff?

Include the source clip, action timing, reference frame, target skeleton, root motion choice, expected contacts, and the Unreal tests that remain.

Start with one motion and one Unreal check

Describe the source action and what the project character needs to do.

Plan a motion reference →