write_cache
Run a Houdini file cache node to render frames and verify the write actually succeeded on disk, reporting errors from the internal ROP with clear success or failure status.
Instructions
Execute a cache node, and report whether a cache actually appeared.
Foreground by default: Houdini shows its own progress dialog and the user can cancel. The call holds until the write finishes, however long that is; a client that hands a long call to a background task notifies you with the verdict when it lands. Do nothing else in Houdini meanwhile (every other call queues behind the write) and never poll the disk.
success and wrote_files reflect the files on disk and the errors of the
node that did the writing -- a filecache delegates to an internal ROP and
stays silent itself, so a failed write used to be reported as success.
Errors are named with the node they came from.
Args: ctx: MCP context. node_path: Path to the cache node. frame_range: [start, end] frame range to render. Overrides the node's $FSTART/$FEND expressions for this and later writes. background: Save from a separate Houdini process (File Cache's own "Save to Disk in Background") so Houdini stays usable, at the cost of the user seeing no progress there. Saves the hip first, returns at once with status "launched"; follow it with get_cache_status. Use it only when asked to keep working while a cache writes. A verified foreground write turns the node's Load from Disk on.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| node_path | Yes | ||
| background | No | ||
| frame_range | No |