Saves the geometry to disk with the last control settings.

Starts another copy of Houdini in the background and instructs that copy to cook and save the geometry. This allows one to continue working and load the .bgeo files as they complete.

Opens the control dialog to allow adjustments of the render parameters before rendering.

Controls whether this render node outputs the current frame or the image sequence specified in the Start/End/Inc parameters.

Specifies the range of frames to render (start frame, end frame, and increment). All values may be floating point values. The range is inclusive.

These parameters determine the values of the local variables for the output driver.

Uses the settings in a particular take while rendering. Choose Current to use the current take when rendering.

The SOP node, object, or SOP subnet to render from.

The file to save the geometry to (should end in .geo or .bgeo). Make sure to include $F in the filename to write out separate files for each frame.

Specifies whether the geometry should be transformed into world space before written out.

When turned on, creates intermediate parent directories for output files as needed. Currently only applies to generated scripts, images, and shadow maps.

Forces all simulation OPs to be reset. This includes DOP Networks, POP SOPs, and other OPs that cache their results.

This is the safest way to render out a simulation, because it starts the simulation from scratch and discards any partial simulations you might have done with different parameters.

A percentage complete value is printed out as files are written. This is in the style expected by Pixar’s Alfred render queue.

The number of bytes sent or received by the distributed simulation primitives during the cooks triggered by this geometry output is printed.

This does not track use by, for example, saving a file to an NFS mount. It only tracks the network communication of nodes such as the Gas Net Exchange Border DOP.

If saving the geometry to disk fails due to a disk writing error, Houdini will usually error the output node immediately. This is desirable for most cases where a failure to save means an illegal path, which is not recoverable. However, sometimes files fail to save due to network issues. If the number of save retries is non-zero, Houdini will re-attempt to save this number of times. Each time will be accompanied with an output to the console of the failure to save and a five second wait in the hopes that the network will clear up.

When saving more than one frame, save in a background thread. This can make saving faster for large file sizes, but may use more memory since it will retain the output geometry until the save completes.

Run this HScript after each frame’s data has finished writing to disk. This is always after the corresponding Post-Frame Script and always before the Post-Render script, but the order otherwise is undefined. When Save in Background is enabled this allows delaying script actions until the file has finished saving.