Ah, yes I see it now. Thanks for the quick suggestion/fix.
Btw, which sRGB color intensity do you recommend?
Ah, yes I see it now. Thanks for the quick suggestion/fix.
0%. Raising this value decreases the amount of clamping. 100% means no clamp.
Makes sense.RealNC wrote: ↑22 Mar 2026, 07:370%. Raising this value decreases the amount of clamping. 100% means no clamp.
In other words, 0% is sRGB colors, 100% is wide gamut colors. I don't know which color space KDE targets, so 100% might be completely unclamped or DCI-P3, no idea. What I do know is that you need 0% for sRGB colors. Unless of course you actually like an oversaturated look, in which case feel free to raise this value.
The whole point of this is that it doesn't change black levels. The monitor can clamp to sRGB colors itself. In the OSD, go to:
Nope.ExplodinFistz wrote: ↑05 May 2026, 14:37Does the new MCM108 firmware fix the banding/posterization issues?
There's better options now. I'd go with a latest-gen QD-OLED, which AFAIK do not have any gamma shift whatsoever, no black crush issues, and behave better in VRR (still not flicker-free, but better than the atrocious flicker of this one.) They also have caught up with the HDR brightness of this particular WOLED.xenphor wrote: ↑02 Jun 2026, 11:03So is this still a good option for a glossy WOLED monitor with the current mitigations in place? Since I always use a frame cap in games, even on an IPS display, will I notice the VRR flicker? Will games with shader compilation or traversal stutter cause flickering, even with a fps cap?
How is this monitor for consoles? Does the gamma shift at lower refresh rates that consoles use like 60 or 120hz help with black crush or is it still pretty bad? That would be my main concern since there's no way to force the correct values like on PC.
Is there another glossy WOLED monitor that fixes these problems?