http://bugs.winehq.org/show_bug.cgi?id=56486 Stian Low <wineryyyyy@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy@gmail.com --- Comment #26 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Ken Sharp from comment #25)
Created attachment 81131 [details] Wine 11.10 console output
libEGL warning: failed to open /dev/dri/renderD128: Permission denied libEGL warning: failed to open /dev/dri/card1: Permission denied
Not seen (or noticed) these before.
wine-staging recently had rendering/flickering related bugs fixed for Battle.net: https://bugs.winehq.org/show_bug.cgi?id=59631#c37 Tests are still ongoing but rendering bugs introduced by new dcomp support seems mostly fixed. Steam was similarly affected by dcomp with severe flickering which has also mostly been fixed by this patch now part of staging: - https://bugs.winehq.org/show_bug.cgi?id=58346#c4 - https://gitlab.winehq.org/wine/wine-staging/-/commit/84f4e6110415eb04b70c25c... Steam and Battle.net seem to depend upon dcomp as their default rendering method for their latest versions and both seem to fallback to alternative rendering methods that most wine users have become familiar with. Now that dcomp rendering has been introduced by staging user may experience new bugs but decent progress has been made so that users are less able to tell any difference between the old and new rendering which is the goal. Because Proton tends to depends on wine-staging fairly heavily so Steam may run best aligning with Proton and in turn Battle.net may run best aligning with how Steam runs best. Wine-staging has other patches besides dcomp that both apps seem to need to fix other bugs not just related to rendering such as crashing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.