ROBOT MOTION

Motion data for robotics teams

AIMoCap separates animation output from robot motion output so robotics teams can evaluate the right target.

For robotics teams that need motion data, not only character animation files.

Short answer

AIMoCap supports robot-oriented video mocap workflows when the job target is selected for robot motion output rather than animation-only export.

Use AIMoCap when robotics motion datasets should be reviewed from uploaded video and kept separate from animation FBX output.

Do not treat animation FBX as robot-ready control data without downstream robot-specific validation, simulation, and safety checks.

Robotics teams often search for motion data, not just character animation. AIMoCap keeps robot targets conceptually separate from animation targets.

The public product currently documents Unitree G1 as the main robot output path, with custom robot requirements treated as integration planning.

Unitree G1 is the publicly documented robot output target.
Robot motion output is separate from animation-oriented FBX output.
AIMoCap is not a replacement for robot safety validation or hardware-specific control logic.
Custom robot support should be planned as an integration topic.

Select Unitree G1 or use the API target list when the job should produce robot-oriented output.

Use preview and result pages to inspect the processed motion before downstream robotics work.

Robot motion should be tested in the appropriate simulation or control environment before real hardware use.

Yes, when the workflow fits uploaded source video and a documented robot output target such as Unitree G1.

No. FBX is animation-oriented; robot motion output is a separate target path.

Treat robot output as a downstream engineering artifact that still requires validation, simulation, and safety checks.

Continue through this topic cluster to compare output formats, API options, and workflow boundaries.