<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Civilization VI - Artifacts in mouse cursor" href="https://bugs.freedesktop.org/show_bug.cgi?id=108355#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Civilization VI - Artifacts in mouse cursor" href="https://bugs.freedesktop.org/show_bug.cgi?id=108355">bug 108355</a> from <a class="email" href="mailto:freedesktop@psydk.org" title="Hadrien Nilsson <freedesktop@psydk.org>"> Hadrien Nilsson</a> <pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=108355#c17">comment #17</a>) > Unfortunately, I had to revert these changes due to <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - In some games cursor is either invisible or with artifacts" href="show_bug.cgi?id=108650">bug 108650</a>. Please test > <a href="https://gitlab.freedesktop.org/daenzer/xf86-video-amdgpu/commit/">https://gitlab.freedesktop.org/daenzer/xf86-video-amdgpu/commit/</a> > d4f250aecabd07a524bf6df3d8eb9e00e589dcf0 instead. It's sad the situation is so confusing. Maybe a new mouse cursor API could be created that accepts normal alpha, as this is the common way to store it (in PNG files for example)? With a conversion to what the hardware expects, of course. It looks like a lot of developers are unable to correctly use an API that expects premultiplied alpha, with the additional difficulty that the documentation does not say it explicitly. Regarding Wayland, I opened a ticket to ask for a documentation update, as an attempt to avoid the same confusion we have now with X. Hopefully the documentation maintainer will be sensitive to the problem. Anyway, I tested your branch (cursor-unpremultiply-overflow-no-gamma) and unfortunately it freezes my system as soon as the Civilization VI cursor is about to be shown.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>