https://bugs.kde.org/show_bug.cgi?id=500144
Zamundaaa <xaver.h...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO
CC| |xaver.h...@gmail.com
--- Comment #3 from Zamundaaa <xaver.h...@gmail.com> ---
(In reply to bugreports61 from comment #0)
> My settings in display settings:
>
> Max SDR Brightness: 100
> Brightness: 40
That's pretty dark, resulting in a reference luminance of 43 cd/m². It is
expected that games will be rather dark with that.
> Sadly i don't know how the Brightness slide interacts with my monitor. In
> HDR mode the monitor locks the brightness setting, but still using that
> display setting brightness sliders changes display brightness ?
>
> I honestly dislike having that setting at all , as changing things there do
> not get reflected in the monitors brightness settings. Same in sdr mode.
It doesn't interact with the monitor at all, because the vast majority of
displays indeed lock their internal controls in HDR mode.
The setting configures paper white for both SDR and HDR content.
> [HDR Layer] VkHdrMetadataEXT: mastering luminance min 0.000000 nits, max
> 10000000.000000 nits
That's suspicious, and might be causing the problem.
When HDR metadata is completely nonsensical like that, KWin just ignores it.
Brightness of the game will be limited to SDR levels, causing this issue.
This logic isn't new at all, but maybe the new brightness logic makes its
effect more obvious.
If you put KWIN_DISABLE_TONEMAPPING=1 into /etc/environment and reboot, does it
work more like expected then?
--
You are receiving this mail because:
You are watching all bug changes.
