Blender
3ds MaxArdy. Another one
behind the same protocol.
Runs inside
Blender
Motion Builder
3ds MaxSoon
Ardy is a motion model trained by NVIDIA. Animatica runs it alongside Kimodo behind the open MMCP protocol, so the plugins you already use can reach it.
It brings its own rig. ardy-core-rp publishes its own joint naming and a 27-joint layout, so the Motion Builder plugin builds that skeleton rather than the built-in SOMA one. Generate on a rig it does not know and the hierarchy travels with the request: the server retargets, and the motion comes back on that rig's joint names.
- Trained by
- NVIDIA. Animatica built the workflows around it, not the model.
- Canonical rig
- ardy-core-rp, a 27-joint layout with its own joint naming
- Runs in
- Blender, Motion Builder. The model list is read live from the server.
- Output
- Not published yet.
- Protocol
- MMCP, the same open protocol every Animatica plugin speaks
- Training data
- Outside Animatica's control. See the model index.
- Our commitments
- Apply to the models we train ourselves, not to Ardy.
What it does.
- 01
Its own skeleton
Pick Ardy and Create Skeleton builds ardy-core-rp — 27 joints under its own naming — instead of the built-in SOMA rig.
- 02
Retargeting
A rig Ardy does not know is sent with the request. The server retargets, and the motion comes back on that rig's joint names.
- 03
Pins and paths
Pins are checked against Ardy's own joint names: on a retargeted rig a Full Body pose drops the joints named differently, and a hand or foot pin on an unknown joint fails the request. Path constraints are not affected.