This node allows text to be written to a file. It can optionally append to an existing file.
Work Item Generation
Whether this node generates static or dynamic work items. You should generally leave this set to "Automatic" unless you know the node’s work items can be computed statically, or that they need to be generated dynamically.
This node always creates dynamic work items: it waits until the upstream work items are known, and generates new work items from the upstream work items.
This node always creates static work items: it creates the number of work items it thinks it needs based on the parameters (and any upstream static items) before the network runs.
If the input is static (a static processor, or a partitioner with only static inputs, or a mapper), this node generates static work items, otherwise it generates dynamic work items.
How the processor node handles work items that report expected file results.
If the expected result file exists on disk, the work item is marked as cooked without being scheduled. If the file does not exist, the item is scheduled as normal.
If the expected result file exists on disk, the work item is marked as cooked without being scheduled. Otherwise the work item is marked as failed.
Work items are always scheduled and the excepted result file is ignored, even if it exists on disk.
When to write the text
The file will be written during the work item generation stage. When this is on, the file is written whenever the node generates items (when the network starts cooking, or when you explicitly ask to generate static items).
The file will be written during the cook and within the graph cooking process.
The full path to the file to be created or appended to.
The result data tag to apply to the file result.
When File Exists
What to do if there is an existing file. This option is only available if the Cache Mode is set to Write Files, since append is not possible when file caching is enabled.
Overwrite: An existing file will be overwritten.
Append: An existing file will be appended to.
The text to be written to the file.
A list of files that should be copied to the PDG working directory before the first work item in this node is executed. This can be used to ensure that supporting files like digital assets and custom scripts are available for the work item job.
The specified paths can be absolute or relative to HOUDINI_PATH.