Dynamics can also be baked. The corresponding settings can be found in the Project Settings’ Cache tab as well as in every Dynamics Body tag’s Cache tab and Connector (i.e. all Dynamics objects that can themselves affected by Dynamics). This means that you can bake all Dynamics at once or on a per-object basis (does not apply to Connectors).
You should first bake your Dynamics when you are ready to create your final render over Team Render. The position, rotation, etc. of all corresponding objects will be saved internally. You can then jump back-and-forth in the Timeline, play the simulation backwards and so on.
The functionality of this Cache differs somewhat from the MoGraph Cache tag. The latter can also bake the effects of the MoGraph Effectors, which the Dynamics Cache tag cannot, and should not, do.
The Dynamics Cache bakes all Dynamics-related effects. Note that the next three settings described below also exist in the Dynamics Body tag where they can each be defined at object level.
Click on this button to bake the Dynamics within the (temporal) preview range. After the baking process has been completed the Dynamics Body tags involved will be made passive and will serve only as collision partners and no longer be affected by Dynamics.
The memory required will be displayed at the bottom, i.e., your .c4d file size will increase by this amount.
Clears all Caches; the Dynamics Body tags will be activated and will again be included in the Dynamics calculations.
Displays the memory requirements of the Cache files. Your .c4d file size will increase by this amount if the Cache is baked.
Use this option to temporarily disable the Cache; the normal Dynamics calculations will again take effect.
If enabled, cached objects will be ignored with regard to Dynamics calculations, i.e., other objects will not collide with these objects.
This option lets you define special time stops or even time markers. This setting simply defines at which point the Cache will be displayed. The fact that this setting can be animated means that the temporal factor can even be reversed. If, for example, you set the Playback Time from 60 to 40 the Cache will play backwards for this stretch. If this option is disabled, 1 frame in the Timeline represents 1 frame in the Cache; both will be played back at equal speed.
Note that this parameter key can currently only be interpolated linearly or stepped (The Set Driver/Set Driven parameter can be used as a workaround, with which you can, for example, set a Driver with which the Playback Time can be controlled).