[RF] RenderFlow

[RF] RenderFlow – 1 per pass, Preset

Submits the current pass to Pulze RenderFlow via rfcli. When a pass has a RenderFlow pmodifier assigned, the Net Render button will submit to RenderFlow instead of the default network render manager.

Options

• • Job name – The name of the RenderFlow job. Supports tokens. Default: <SceneName>_<Timestamp>
  • Priority – Job priority (0–100). Default: 25.
  • Initial Job Status – Whether the job starts as pending (active immediately) or suspended. Default: pending.

How It Works

• • When Net Render is triggered, renderStacks detects the RenderFlow pmodifier on the pass and routes submission through rfcli.
  • The current scene is saved to a timestamped subfolder inside the Network Submission Temp path.
  • Frame range and resolution are read from the current render settings (after all pmodifiers have been applied).
  • Output path is read from the resolved main render output.
  • rfcli is called with jobs submit and the job ID is returned on success.

Notes

• • Only one RenderFlow pmodifier per pass is supported (multi = false).
  • This pmodifier runs last in the pmodifier chain (runLast = true).
  • Preview render (Net Seq Preview) appends (Preview) to the job name.

Requirements

• • RenderFlow must be installed and rfcli.exe must be set in renderStacks Preferences (Preference menu > RenderFlow section).
  • rfcli version 1.3.0 or above is required. renderStacks will check the version at submission time and report an error if the requirement is not met.
  • Network Submission Temp .max File Path must be set in Preferences. RenderFlow submission saves the scene to this path before calling rfcli.