vRay 3.30 Color Temperature/White Balance bug

[luminancestudio]

Hi,
Why the color temperature in lights set to 5600K looks warm? It should be neutral white.

In older vRay versions, when I set 5600K in lights and Neutral White Balance in camera, the result of white balance was perfect grey. Now it is warm.
It is bug or...?

Best,
Tom

[vlado]

In newer builds the white point was moved to 6500K, since this is what most other software assumes; textures in the sRGB color space also assume that white is at 6500K.

You can switch back if you like using this line of MaxScript:

renderers.current.options_rgbColorSpace=0

Best regards,
Vlado

[luminancestudio]

Thank you,

Best,
Tom

[Joelaff]

So, assuming no color mapping or toning in the VRay Camera with 3.3 by default a light must be 6500K to be pure white?

I miss the film days of 5500K being daylight. 6500K is open shade cool.

[vlado]

So, assuming no color mapping or toning in the VRay Camera with 3.3 by default a light must be 6500K to be pure white?

Yes.

I miss the film days of 5500K being daylight.

Well, the problem was that it also made the sky and sun produce illumination with a slighly greenish tint which many users found unnatural.

Best regards,
Vlado

[Pixelab]

Ok, then if we want to render a scene with the same temperature as before, we have to remove 1000K from the temperature of our cameras WB to have more or less the same result, correct ?

(In order to be able to render an old scene with SP3 without changing the lights K)

[vlado]

Ok, then if we want to render a scene with the same temperature as before, we have to remove 1000K from the temperature of our cameras WB to have more or less the same result, correct ?

(In order to be able to render an old scene with SP3 without changing the lights K)

You can just revert to the old color space (see the post above).

Best regards,
Vlado

[Rens]

Hi Vlado, needed to switch back for some scenes and noticed that the script line should read

renderers.current.options_rgbColorSpace=0

Renderers with -s.
Cheers

[vlado]

Hi Vlado, needed to switch back for some scenes and noticed that the script line should read

renderers.current.options_rgbColorSpace=0

Renderers with -s.
Cheers

Yes, indeed! Thanks for the pointer - I updated my original post.

Best regards,
Vlado

[roysgi]

Is it not too much red? Maybe something in the middle between the new version to the old one?
What do you think?

[Richard7666]

I was struggling with this change in 3.30 too.

Everything seemed to feel as though it had a strong 'lavender/pruple/rose' filter applied when using the default Vray physical camera white balance presets/temperatures. Was getting results like this:




Ended up having to set my white balance to a sort of lavendar/purple to get natural results in 3.30, see image on left (pre- 3.30 colourspace on right for comparison)



(ball has diffuse of 200 in all renders, and just using sun&sky preetham et al defaults, GI saturation 0.6)

Reference photo

[^Lele^]

It'd make sense to update the settings for the WB, as those come from ages ago, and likely were never meant to work at 6.5k, or with Hosek, or with the newer versions of Preetham (they are REALLY old ones.).

As a workaround, i do this, normally:


which then gives me this (regardless of color space and sky model, provided we're under LWF.):

[AlexP]

It'd make sense to update the settings for the WB, as those come from ages ago, and likely were never meant to work at 6.5k, or with Hosek, or with the newer versions of Preetham (they are REALLY old ones.).

As a workaround, i do this, normally:

Can you explain a bit more what you have done here please?

[Richard7666]

Can you explain a bit more what you have done here please?

set the Vray physical camera's white balance to 'custom' and use that lavendar colour that Lele specifies in his screenshot.

[mitviz]

o heck i was always wondering about this, something just never looked correct to me so with the wb