gordonrobb wrote:I have this problem if I use an RGB colour. If I want to find the colour for (in this instance) Caterpillar Yellow, I can 'only' find the RBG, or Hex colour. That's the problem. And if i'm must picking a colour in the colour picker based on what looks good, that is not how it renders (unlike in Standalone, where what you see is what you get). Do you see what I mean? And the difference is greater the darker you go. To get a dark brown, I almost have to go totally black. And tiny differences make massive differences in the render.
The problem is always the same: the LW color picker is working in linear space, and the picked/shown color are not color corrected for a 2.2/sRGB gama output rendering.
The only way I know to enable the color correction in the LW pickers without affect the Octane rendered images is to set the output Display Color Space to sRGB, and enable the Affect Color Picker option, like you can see in the attached image, leaving all the other settings disabled and linear.
The problem: all is going to work fine with this configuration, but when you render with F9, LightWave is going to enable a sRGB color correction over the already color corrected and tonemaped Octane rendered image. This overcorrection doesn't affect the IPR, the rendering preview window, or the buffers exported from the Octane passes node or saved from LW. It only affects the LW render display window, but you can set it to Linear again in the top menu bar, as you can see in the attached image.
Try to work with this configuration and let me know if you get side effects in the Octane rendered images.
-Juanjo
