Re: Octane 2026.3 for Cinema4D - v1.9.3
Posted: Thu May 28, 2026 1:28 pm
Hey Beppe, thank you for replying! Of course, I agree that LV color dropdown shouldn't have an actual effect on the exported Output AOVs. But when showing an Output AOV within the LV, what would be the harm if the LV view transform was respected? That is the behavior for all the other passes. (EDIT: excluding the "info" ones, but reflection, refraction, etc.)bepeg4d wrote: Thu May 28, 2026 10:41 am
Sorry, I cannot reproduce the issue.
Output AOVs are untonemapped, so you need to apply the same color conversion with layers, to obtain the same result you have in Main pass, and Live View color dropdown menu shouldn't have any effect on Output AOVs![]()
Could you share an example scene that shows the issue?
ciao,
Beppe
The context is: I'm trying to do some grading directly in Octane, so I'm running the Main Pass into an Output AOV. As a clean starting point, with no grading applied, I need these two to match when viewed in the LV under a sRGB: ACES view transform. That is currently not possible, as the LV transforms one but not the other.
The solution, as you say, is to add a "convert for SDR display" node in the Output AOV graph, so I can accurately preview my composite in the Live Viewer. The problem is: That transform is then permanently baked into the final EXR on render. So I need to disable the node before any export, then later enable it again for further look dev.
So I was looking for a way to avoid this type of workflow and/or hear that I misunderstood something about how the plugin currently handles this, which is very possible. I can share a scene, but we may be describing the exact same behavior. : )