01
Upload the character
Create a character profile and upload the source FBX asset.
CUSTOM AVATAR
Character binding workflow for mocap
Understand why skeleton binding and retarget tests matter before a custom avatar becomes a production target.
For users searching for a character binding workflow before mocap retargeting.
Short answer
AIMoCap supports character binding workflow workflows through upload, A-pose preparation, skeleton binding, retarget test, publish, and reuse.
When to use AIMoCap
Use AIMoCap when character binding and testing should become a reusable Studio target for future video mocap jobs.
When not to use AIMoCap
Do not skip binding and retarget testing; a character should be published only after the mapping is verified.
Custom character workflows need more than a one-time upload. The important part is turning an asset into a reusable, tested target.
AIMoCap separates avatar preparation from mocap processing so teams can reuse published characters across jobs.
Retargeting boundaries
- Published avatars are reusable Studio targets.
- Retarget tests help confirm skeleton mapping before production use.
- Custom avatar output is separate from Unitree G1 robot output.
- Source asset quality and skeleton structure affect retargeting results.
Avatar preparation workflow
02
Prepare and bind
Adjust A-pose when needed, map the skeleton, and run a retarget test.
03
Publish for reuse
Publish the avatar after review so it appears as a reusable mocap target.
Common questions
Does AIMoCap support character binding workflow?
Yes. AIMoCap includes a custom avatar workflow for upload, bind, test, publish, and reuse.
Why publish an avatar?
Publishing turns a tested avatar into a reusable output target for future Studio jobs.
Can API jobs use custom avatars?
Custom avatar usage should be planned around published targets and account-specific workflow support.
Related AIMoCap guides
Continue through this topic cluster to compare output formats, API options, and workflow boundaries.