Reusable target
A published avatar can be selected again in Studio, which makes the upfront binding and test step useful for repeated jobs.
CUSTOM AVATAR
Custom avatar retargeting for video mocap
Upload, bind, test, and publish custom avatars in AIMoCap so video mocap jobs can reuse them as output targets.
For animation teams looking for custom character retargeting in a video mocap workflow.
Short answer
AIMoCap lets teams upload, bind, retarget-test, publish, and reuse custom avatars as Studio output targets.
When to use AIMoCap
Use it when repeated mocap jobs should target your own character instead of only a default animation target.
When not to use AIMoCap
Do not skip binding and retarget testing; source asset quality and skeleton structure still determine whether the avatar is reusable.
AIMoCap includes a custom avatar workflow for teams that need motion output on their own character rather than only a default target.
After upload, A-pose editing, binding, retarget testing, and publish, a custom avatar can be reused inside Studio.
This page is about the reusable target lifecycle, not only file upload. The important decision is whether the character has passed enough setup and test steps to become safe for repeated mocap jobs.
What this enables
- Published custom avatars become reusable Studio output targets.
- Retarget testing is required before a custom avatar is used as a reliable target.
- The custom avatar workflow is separate from Unitree G1 robot motion output.
- A-pose editing and skeleton binding are setup steps; they do not by themselves prove the character is ready for production mocap jobs.
- Publishing is the handoff point where a tested avatar becomes selectable for future Studio work.
Custom-avatar workflow facts
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
Quality gate
A retarget test acts as the practical quality gate before an uploaded character becomes a reusable mocap target.
Separate from robot targets
Custom avatars are animation-character targets; Unitree G1 remains a separate robot-motion target.
Lifecycle boundary
A draft avatar can contain source assets and mapping work, while a published avatar is the version intended for repeated Studio job selection.
Search-intent boundary
Users searching for custom avatar retargeting usually need upload, A-pose, binding, test, publish, and reuse details, not only a generic video mocap pitch.
Custom avatar workflow
01
Upload the character
Start by creating a character profile and uploading the source FBX asset.
02
Bind and test
Edit the A-pose when needed, map the skeleton, and run a retarget test before publishing.
03
Publish and reuse
Once the retarget result is approved, publish the avatar so it can be selected for future mocap jobs.
04
Keep draft and published states separate
Treat uploaded or partially bound characters as draft assets until the retarget test proves the target is ready for reuse.
Common questions
Can I use my own character in AIMoCap?
Yes. A custom avatar can be uploaded, bound, tested, published, and then reused as an output target.
Why is a retarget test needed?
The retarget test helps confirm that the skeleton mapping and motion result are usable before the avatar becomes a reusable target.
Can custom avatars be used with video mocap jobs?
Yes. Published custom avatars can be selected as output targets in Studio.
Is uploading an FBX enough to make a reusable target?
No. Upload is only the first step. The avatar still needs A-pose review, skeleton binding, and a retarget test before it should be published for reuse.
What is the difference between draft and published avatars?
A draft avatar is still being prepared or tested. A published avatar has passed the workflow and can be selected again as a Studio output target.
Related AIMoCap guides
Continue through this topic cluster to compare output formats, API options, and workflow boundaries.