https://bugs.winehq.org/show_bug.cgi?id=38921
--- Comment #14 from Linards linards.liepins@gmail.com --- (In reply to Gregor Münch from comment #13)
I dont think that any Windows program checks for the exact driver string. Especially because AMD does extensive rebranding. The driver string on Windows Catalyst driver package can change with every release and in fact it did in the past numerous times. e.g. Radeon HD 7970 was identified as Radeon HD 7900 Series while it became in newer driver versions Radeon R9 200 / HD 7900 Series
Anyway I dont think that anything would change if wine would report what Catalyst would report: Radeon HD 7700 Series The reason why Crysis 2 does say non-supported is that it very likely just see's what Steam see's: Nvidia Geforce 8600 GT
So either you did something wrong with your registry and you should try with a clean .wine or wine fails to detect your card and hits a fallback path.
Hi Gregor,
Yes, these are fair points, jet they highlight quite a chain of issues community can experience, in particular: - There is either almost-working solution (used by fwupd / lspci for my particular video card) due to the way AMD handles their GFX ecosystem/market - There is fallback mechanism that is basically breaking some amount of applications to work normally ("fallback" is nor really a fallback, but rather default / constant vendor string if value == null ) - There is chance that Windows Registry implementation can be compromised since I have done that only to get my CS:GO kicking in Steam); the rest of changes are happening only via winetricks UI.
In summary I can make with my understanding, I, as basic/power-user, even with proper implementation of wine, cannot fully do stuff due to missing underlying Mesa infrastructure. And that SUCKS big big big time. If there is supereset of the issue we can link to this ticket, please do so.