Dingbat wrote:hi Paul, it may only happen when adjusting an existing material
try this:
open default template scene
create slab
apply any textured material
select diffuse node and hit Copy
add CC node - i can already see the CC gamma is 2.2
select Diffuse Input node, choose RGB Image, cancel the window that appears and hit Paste to re-apply the diffuse with the same mapping as before
Material is now darker as gamma 2.2 is applied twice
on a related note, as you can see from the process above when i use the CC node i always need to paste the diffuse back in and cancel the window that appears. is it possible to automatically keep the diffuse w/mapping when adding a CC node?
Thanks
I have had a good look into this and found some issues with the way the plugin is handling gamma since the Octane OCIO functionality was added to the Octane render engine. In summary:
1) The "Color Space" pin for an RGB Image node cannot be set in the plugin, and the plugin automatically sets this pin to "Linear sRGB + legacy gamma" when rendering. Therefore whatever gamma you have set in the Legacy Gamma field (which will be 2.2 for .PNG files) will apply. The plugin is not correctly doing this (it is leaving the gamma at 1.0), so I will fix this in the next release (which I will post in the next hour).
2) When you change a node type, the plugin attempts to copy across the pin values for pin names that are present in both the old and new node. Unfortunately, the "Legacy Gamma" pin (which has an internal node name of "gamma") is present on both the RGB Image and Color Correction nodes, so the gamma value gets copied from the RGB Image node to the Color Correction node, which results in the 2.2 gamma setting being applied twice. I have raised this issue with OTOY, who ideally need to have a different node name for the Legacy Gamma pin, although it this this would be problematic for them to do at this late stage. So instead, the next release of the plugin will not copy the "gamma" pin when converting a node to a Color correction node type.
> is it possible to automatically keep the diffuse w/mapping when adding a CC node
I don't think this level of automation would be easy to implement, sorry.
Thanks
Paul