https://bugs.kde.org/show_bug.cgi?id=521803
Oleg <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #31 from Oleg <[email protected]> --- (In reply to Zamundaaa from comment #30) > That's a shame, but fixing the multiplier should help slightly at least. > Is the banding noticeable in any specific places, with specific settings or > similar? I drove around a bit in Cyberpunk, and the only case I found where > there's a visible difference between compositing and direct scanout on my > hardware is with night light enabled. I only get banding issues in parts with low luminances. You can see on my screenshots banding appears on gradients towards black color. I'm not using night light. > The MR helps for that, but it might not have the same effect for your > banding problem if the cause is different. I've compiled kwin 6.7.1 with reverted https://invent.kde.org/plasma/kwin/-/commit/9079a417b821f80c0d9e3bc5014a388e0e340f82 and patched https://invent.kde.org/plasma/kwin/-/merge_requests/9477 yet still got banding (see attachments). > In addition to the MR, I also have another hacky patch to test. If the named > curve, matrix or multiplier are at fault, just using 1D + 3D LUT should be > fine. I've compiled kwin 6.7.1 with reverted https://invent.kde.org/plasma/kwin/-/commit/9079a417b821f80c0d9e3bc5014a388e0e340f82 and your hack to only use 1D + 3D LUT without patching MR, and it did solve banding issue! See the attachment. -- You are receiving this mail because: You are watching all bug changes.
