|On this page|
The File Cache SOP combines a File SOP and a Geometry ROP to provide a simple way to cache out an intermediary stage of a SOP network to a sequence of disk files.
Load from Disk
Switches between passing through the input geometry and loading the geometry from disk.
If you start a render, it will always use the input geometry, ignoring this parameter.
How this node reads/writes the geometry to/from the disk file.
This parameter is only enabled when Load From Disk is disabled.
Writes the file if it doesn’t exist, reads it if it does exist.
This is useful for caching, where the node will write the cache to disk the first time it cooks, and use the cache file from then on.
To force a refresh of the cache, manually delete the file on disk.
Reads the geometry from the file. If the node’s input is connected, it’s ignored.
Writes the input geometry to disk.
No file access will occur. Pass through the input geometry to the output, like a Null surface node.
Where to load the geometry from when in Load from Disk mode. This also controls where the Geometry ROP will save the geometry.
Export to File
See the Geometry ROP help for these parameters.
Further subdivide the frame increment by this number of substeps, often
used when caching geometry as input to a substepped simulation. Note that
if this parameter is greater than 1, the Geometry File parameter should
take into account fractional frames via use of
$FF in its expression.
When importing simulation data, you may have extra attributes or groups that you do not need to save to disk. The Delete Attributes and Delete Groups parameters will cull this extra data.
If you do not require the full precision of 32 bit float attributes, you can down cast them at this point as well. See the AttribCast SOP help for more information.
When loading the cached file back from disk, this controls the behavior. The File SOP help has more details for these parameters.