Blender addon. Incorrect work of node "OCIO color space"

A public forum for discussing and asking questions about the demo version of Octane Render.
Forum rules
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
Post Reply
User avatar (Default)
s7unned
Posts: 2
Joined: Mon Sep 21, 2020 11:43 pm

Image



Hello. Blender octane node "OCIO color space" works incorrect when set to "Output SRGB". As you can see on the screenshot, it produces artifacts on bright areas, like its some sort of clamping happening. Under is a picture of how it should work (tested in cycles). You can easily try to reproduce this bug youself.
Top
User avatar (Default)
linograndiotoy
OctaneRender Team
Posts: 1496
Joined: Thu Feb 01, 2018 7:10 pm

Which version are you using?

Also, could you please share your scene with us?

Thanks.
Top
User avatar (Default)
linograndiotoy
OctaneRender Team
Posts: 1496
Joined: Thu Feb 01, 2018 7:10 pm

Most important thing: please check if View Transform in your Color Management options is correctly set to Raw.
Top
User avatar (Default)
s7unned
Posts: 2
Joined: Mon Sep 21, 2020 11:43 pm

Thank you for answer. Version 30.7.0. View transform was set to Raw.

As far as i understand, the problem was that i set IDT as "Output sRGB", which makes bright areas of texture exceed 1. Which is not physically correct, since albedo in octane cant exceed 1. If i set same texture with same IDT as emission, then all clamping is gone. Right IDT to use for 8bit textures should be "Utility - texture - SRGB". Correct me if Im wrong.
Last edited by s7unned on Tue Oct 07, 2025 2:02 pm, edited 1 time in total.
Top
User avatar (Default)
Merc25
Posts: 1
Joined: Fri Oct 10, 2025 7:32 am

the “Output sRGB” mode seems to clamp highlights incorrectly. Definitely worth reporting as a bug to the Octane devs for a fix.
Top
User avatar (Default)
s7unned
Posts: 2
Joined: Mon Sep 21, 2020 11:43 pm

That is why it was confusing to me, because in other renderers "Output SRGB" on albedo works fine.
Top
User avatar (Default)
johnholcomb
Posts: 1
Joined: Tue May 12, 2026 2:34 am
Contact:
Contact johnholcomb

I can reproduce this issue too. When the Octane “OCIO Color Space” node is set to “Output sRGB”, highlights get clipped and produce visible artifacts/banding, especially in bright emissive or overexposed areas. The same setup in Blender Cycles behaves correctly, so it looks like Octane is applying an incorrect transform or clamping values internally during the Output sRGB conversion. Definitely seems like a bug rather than expected behavior.
Top
Post Reply

Return to “Demo Version Questions & Discussion”