https://bugs.kde.org/show_bug.cgi?id=506212
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/-/commit/d70ee5efc9 |ma/kwin/-/commit/6acc3934dc |d6b856a067ed284896481cd59a9 |cf5b4d2618ab04cca064b3d67bd |1ac |1c2 --- Comment #4 from Zamundaaa <[email protected]> --- Git commit 6acc3934dccf5b4d2618ab04cca064b3d67bd1c2 by Xaver Hugl. Committed on 05/11/2025 at 17:43. Pushed by zamundaaa into branch 'Plasma/6.5'. opengl/colormanagement: also clip after tonemapping With night light, the maximum luminance that can be represented in the buffer without color shifts is lower than the value represented by 1.0. When writing into the buffer, OpenGL implicitly clips for us to 1.0, so we end up with an out of bounds value, which ends up causing color shifts when the result is converted to a different white point. To avoid that, explicitly clip to the maximum luminance after tonemapping. (cherry picked from commit d70ee5efc9d6b856a067ed284896481cd59a91ac) Co-authored-by: Xaver Hugl <[email protected]> M +1 -0 src/core/colorpipeline.cpp M +5 -3 src/opengl/colormanagement.glsl https://invent.kde.org/plasma/kwin/-/commit/6acc3934dccf5b4d2618ab04cca064b3d67bd1c2 -- You are receiving this mail because: You are watching all bug changes.
