Octane Render AOV Save Path Requires Manual Folder Selection (Cannot Be Set via Python/API)
Posted: Tue Sep 09, 2025 12:43 am
Description
When working with Octane in Cinema 4D, we can enable the Save dialog, Multi-Pass, and Render AOV Manager programmatically. We can also toggle formats (e.g., 16-bit DWAB EXR) without issue.
However, the Render Pass path field has a critical limitation:
If you manually click the folder button next to the path field and select a directory, Octane accepts the path and rendering works as expected.
If you try to set the path programmatically (writing a string directly into the parameter), Octane does not recognize it.
Without this manual folder selection, Octane either defaults back to a standard Multi-Pass EXR output or refuses to render multilayered EXRs properly.
This forces a redundant manual step in an otherwise automated pipeline.
Expected Behavior
The Render Pass path should be settable via Python/SDK, the same way we can toggle checkboxes and formats. Scripts should be able to define the save directory without requiring a GUI folder-picker confirmation.
Actual Behavior
Octane ignores programmatically set paths and requires a manual folder selection before it will save multilayered EXRs correctly.
Why This Matters
This breaks automation workflows (e.g., versioned save/iteration systems like “I Like It”) because users are forced to manually re-select a directory each time instead of letting scripts manage it.
Request
Please allow the Render Pass save path to be set programmatically via Python/API, without needing the folder-picker dialog.
When working with Octane in Cinema 4D, we can enable the Save dialog, Multi-Pass, and Render AOV Manager programmatically. We can also toggle formats (e.g., 16-bit DWAB EXR) without issue.
However, the Render Pass path field has a critical limitation:
If you manually click the folder button next to the path field and select a directory, Octane accepts the path and rendering works as expected.
If you try to set the path programmatically (writing a string directly into the parameter), Octane does not recognize it.
Without this manual folder selection, Octane either defaults back to a standard Multi-Pass EXR output or refuses to render multilayered EXRs properly.
This forces a redundant manual step in an otherwise automated pipeline.
Expected Behavior
The Render Pass path should be settable via Python/SDK, the same way we can toggle checkboxes and formats. Scripts should be able to define the save directory without requiring a GUI folder-picker confirmation.
Actual Behavior
Octane ignores programmatically set paths and requires a manual folder selection before it will save multilayered EXRs correctly.
Why This Matters
This breaks automation workflows (e.g., versioned save/iteration systems like “I Like It”) because users are forced to manually re-select a directory each time instead of letting scripts manage it.
Request
Please allow the Render Pass save path to be set programmatically via Python/API, without needing the folder-picker dialog.