When sending objects to a remote application (Maya, 3ds Max), MotionBuilder recognizes the constraints that the other application
does not support. Dynamic baking ensures that these unsupported constraints get recorded in objects to produce an accurate
animation in the remote application.
In general, a constraint will be baked in the following scenarios:
- If it is not supported by the remote application.
- If it's source object was not sent to the remote application.
When sending objects to Maya, MotionBuilder will bake constraints in the following scenarios:
- If a character's source is an actor.
- If a character's source is another character that is not being sent to the remote application.
- If a character does not use an HIK solver.
Note3ds Max does not support any of the same constraints as MotionBuilder. As a result, when sending objects to 3ds Max, all constraints
are baked, even if the source object is also being sent. Maya supports many of the same constraints as MotionBuilder. If you
send a constraint from MotionBuilder that is natively supported in Maya, it does not need to be baked.
Except where otherwise noted, this work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
