Light Mix ****BUG****

[Alex Abarca]

Hi Corona Team,

When lightmix is enabled and if the user sets a Kelvin color (e.g., 4800K) using the Corona Color Picker, closing and reopening the color picker causes it to default back to 1700K.

[TomG]

Does it keep the same color as you set though, now specified via other parameters in the color picker?

[Aram Avetisyan]

Hi Corona Team,

When lightmix is enabled and if the user sets a Kelvin color (e.g., 4800K) using the Corona Color Picker, closing and reopening the color picker causes it to default back to 1700K.

I believe this was reported earlier and this is just how the color picker works - the RGB values are kept and not the temperature equivalent, even if the color is set with temperature (it gets converted to RGB)

[Alex Abarca]

This seems like a bug, let me explain why.

If you select a color, say 4800K, and then reopen the color picker, it should stay at 4800K. This consistency is important for artists who might want to make subtle adjustments to the Kelvin color. For example, if it was 4800K and you want to bump it up to 5000K, you’d need the original value as a reference.

While this might not seem like a big deal at first, you would expect that numerical parameters like these should remain consistent in most Windows applications, right?

[Aram Avetisyan]

This seems like a bug, let me explain why.

If you select a color, say 4800K, and then reopen the color picker, it should stay at 4800K. This consistency is important for artists who might want to make subtle adjustments to the Kelvin color. For example, if it was 4800K and you want to bump it up to 5000K, you’d need the original value as a reference.

While this might not seem like a big deal at first, you would expect that numerical parameters like these should remain consistent in most Windows applications, right?

Yes, but it is how, unfortunately, the Color picker works now.

In the meantime, here is a good workaround for you using OSL maps. Please see attached image.
Hope this helps.