Apple Shake 4 New Features - Manual (Page 44)

44 Chapter 2 Major Features and New Nodes
The total cache memory limit has been exceeded.
The second possibility is that the amount of memory needed by all the Cache nodes in
your script exceeds the memory assigned to the cache by the diskCache.cacheMemory
global plug. In this case, no additional Cache nodes may be cached without increasing
the diskCache.cacheMemory global plug.
Caching and Updating Frames
The Cache node updates whenever the playhead moves, caching additional frames if
necessary because of changes that have been made in the preceding nodes. If
necessary, you can also render one or more Cache nodes and cache a range of frames
in advance using the Render Cache Nodes command.
If you later make changes to one or more nodes in a section of the node tree that’s
been cached, the affected cached frames are discarded, and can be re-cached.
To use the Cache node:
1 Insert a Cache node after the last node of a section of the node tree that you want to
cache.
2 Load the Cache node’s parameters into the Parameters tab.
3 Select an option from the forceCache parameter. The disk+memory option is the
default forceCache setting, and is almost always the preferred setting to use.
4 If you want to immediately cache that section of the node tree for a specified duration,
choose Render > Render Cache Nodes.
5 The Cache Render Parameters window appears, which automatically updates the
timeRange to the Global timeRange.
6 Click Render to render the Cache node. A Flipbook appears, allowing you to view the
progress of the render, and play through the cached image sequence.