Motion Capture Sample Data for Rig Tests

Need a motion capture sample? Compare captured datasets with generated drafts, then produce a test clip to validate a rig, importer, or retarget setup.

Mocap samples workflow preview
Pipeline testing

motion capture sample

A new rig or importer has to be proven before production data touches it, and one captured example rarely covers the speeds, directions, and grounded poses your test needs.

Hunyuan Motion from one sentence, then preview the clip

A 3D animator who needs a human motion clip types one sentence in the browser and previews the motion when the job finishes. Sign in before the job can start. The Generate click checks credits: Fast uses 60 and Standard uses 80. If the balance is short, the credit purchase opens then. A daily claim adds 50 credits; from a zero balance, two claims cover one motion.

From one sentence

A text prompt in the browser

Preview the clip

Watch the motion when it finishes

60 / 80 credits

Fast / Standard, checked at generate

50-credit daily claim

Two claims cover one motion from zero

Why a pipeline needs test motion before production data

Captured datasets against generated drafts, side by side

A small validation set covering speed, turns, and balance

What to measure while you validate

What people mean by a motion capture sample

The phrase covers at least three things, and mixing them up wastes time. It can mean a short clip of performer data recorded on a stage, a public dataset published for research, or a synthetic stand-in used only to exercise a pipeline. A validation task usually needs the third kind: cheap, disposable, and varied enough that a broken importer fails loudly. Decide which you need before shopping, because licensing, accuracy, and file conventions differ sharply between a studio capture and a generated draft.

Where captured samples come from

Real capture data arrives from a studio archive, a commercial motion library, or an academic release, and each brings conditions. Stage data may be tied to a specific performer, rig, and session, and its license may restrict redistribution or commercial use. Research datasets are usually free for study but often ship in skeleton conventions that differ from your engine, which turns a simple test into a conversion project. Read the license and the skeleton documentation first; a sample you cannot legally ship is not a sample you can test with.

What a generated draft gives you instead

A generated draft is not captured data and does not pretend to be. There are no markers, no performer, and no ground-truth skeleton; instead you get movement built from a written description, which means you can order exactly the action you want to test. That is useful for importer and mapping checks because you can request a fast turn one minute and a slow walk the next without booking anything. Treat it as synthetic test footage for your own rig, and never present it as recorded performance or biomechanical reference.

Build a small validation set

Five short clips will expose most mapping and scale problems: a walk, a run, a turn in place, a jump with a landing, and a grounded gesture. Add one variation of each in a different speed or direction so you can see whether the problem follows the motion or the rig. Keep every clip short, because you are testing a pipeline and not producing a shot, and download both FBX and JSON once so you can compare how each represents the same movement. Store the prompt, mode, duration, and seed beside the files.

What to measure while you validate

Import each clip into a sandbox scene and log specific observations: do bones map by name, does scale match the character, is forward axis correct, does the root travel when it should not, do the feet slide, and do the first and last poses blend into neighboring states. Record how long each repair took, because cleanup time is the real cost of a motion source. A test that ends with a written failure list is worth more than one that ends with a clip that merely looks acceptable in a viewport.

Limits and honest scope

Generated drafts contain one humanoid action each, cannot include a second performer or a prop, do not carry facial, eye, lip, or finger animation, and do not promise seamless loops or in-place playback. There is no marker or joint-angle ground truth to compare against a scientific reference. If your validation genuinely depends on recorded performance, sensor accuracy, or a published dataset with a known skeleton, arrange that data separately and use a generated clip only to rehearse the import and mapping steps beforehand.

Workflow

  1. 1Write down what the test must prove: mapping, scale, axis, travel, or contact.
  2. 2Assemble a short action set covering fast, slow, turning, and grounded movement.
  3. 3Generate the drafts and download FBX or JSON for the test rig.
  4. 4Record each failure so the cause can be traced to the rig, the importer, or the motion.

Questions

Is a generated draft the same as captured motion capture data?

No. It is synthetic motion built from a written description, with no performer, no markers, and no ground-truth skeleton to compare against.

Can I download a video or a side-view recording as a sample?

The tool returns motion files such as FBX and JSON plus a browser skeleton preview, so it does not produce a video or a filmed side view of a capture.

How many clips should a rig test use?

About five varied actions, covering walking, running, turning, a jump with a landing, and one grounded gesture, will expose most mapping, scale, and root-motion faults.

Do test samples cost credits?

Yes. Every generation spends credits, so keep each test clip short and use Fast mode when the goal is only to exercise an importer or rig.

Related motion workflows