Re: Octane 2026.2 for Cinema4D - v1.8.4
Posted: Wed May 20, 2026 1:45 pm
@ChrisHekman: Thank you for shedding more light on this!
So in a clean, default C4D scene - what settings should users typically change so that it works with the current iteration of the plugin?
From what I understand, we would usually want to stick with the new C4D default (ACEScg) render space, with View Transform kept as ACES 1.0 SDR-video - and then we set the LV to the same, so ACES 1.0, which becomes available when the config.ocio is linked via settings / color management? Should the color space in the Octane Render Settings (under buffer type) also be changed from sRGB to ACEScg for EXR export?
The official guide (https://help.otoy.com/hc/en-us/articles/44305077770139-Fixing-C4D-2026-Octane-Color-Mismatches) used to give a straightforward answer to this, but that answer seems to be outdated (stills says "switch color management to legacy").
So in a clean, default C4D scene - what settings should users typically change so that it works with the current iteration of the plugin?
From what I understand, we would usually want to stick with the new C4D default (ACEScg) render space, with View Transform kept as ACES 1.0 SDR-video - and then we set the LV to the same, so ACES 1.0, which becomes available when the config.ocio is linked via settings / color management? Should the color space in the Octane Render Settings (under buffer type) also be changed from sRGB to ACEScg for EXR export?
The official guide (https://help.otoy.com/hc/en-us/articles/44305077770139-Fixing-C4D-2026-Octane-Color-Mismatches) used to give a straightforward answer to this, but that answer seems to be outdated (stills says "switch color management to legacy").