AIMoCap

Documentation

Quick start, Studio workflows, API guidance, output formats, pricing, and FAQ.

AIMoCap Docs

Output Formats

Understand the FBX and robot motion data that AIMoCap generates today.

FBX output

AIMoCap currently produces FBX animation output for:

  • the built-in default target
  • published custom humanoid characters

This FBX output is character animation data. It is suitable for downstream review, cleanup, retargeting, and scene integration in tools such as:

  • Maya
  • MotionBuilder
  • 3ds Max
  • Unity
  • Unreal Engine

Robot motion data

Robot motion output currently supports:

  • Unitree G1

More robot targets are planned for later updates.

If you need custom robot adaptation, contact support@aimocap.net.

Mujoco JSON structure

The Unitree G1 robot output is a Mujoco-oriented JSON motion file.

A simplified example looks like this:

{
  "version": 1,
  "robotType": "unitree_g1",
  "fps": 30,
  "frameCount": 120,
  "root_pos": [[0.0, 0.0, 0.79]],
  "root_rot_xyzw": [[0.0, 0.0, 0.0, 1.0]],
  "dof_pos": [[0.0, 0.1, -0.2]]
}

Field reference:

  • version: format version
  • robotType: robot identifier
  • fps: motion sampling rate
  • frameCount: total frame count
  • root_pos: per-frame robot base translation
  • root_rot_xyzw: per-frame robot base rotation quaternion in xyzw order
  • dof_pos: per-frame joint position array

In practice, this file represents a frame-by-frame sequence of:

  • robot base position
  • robot base orientation
  • joint positions

It is intended for downstream Mujoco and robot motion pipelines rather than DCC character animation tools.