https://bugs.winehq.org/show_bug.cgi?id=41711
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
--- Comment #27 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Chris Rankin from comment #25)
(In reply to Matteo Bruni from comment #24)
So if I understand it correctly, WoW works fine for you with d3d9 and no overrides? If that's the case there is nothing to fix here.
Not setting MESA_GL_VERSION_OVERRIDE sounds like just another workaround to me :-|. Because as I've already said, it also works with MESA_GL_VERSION_OVERRIDE=4.0COMPAT.
How is not setting any override a workaround? Wine, like any reasonable OpenGL application, checks what features are available with the current driver / GPU and uses only those that are supported. If you override the GL version reported by the Mesa driver you effectively break that kind of checking, since the driver now reports a bunch more features as supported which they really aren't (that environment variable doesn't magically add features to the driver). Wine goes to use them, they don't work and you get GL errors and broken rendering.
By overriding the GL version to 4.1 compatibility you enable a number of extensions flags in Wine without the driver being able to support them, breaking things. FWIW it's probably ARB_viewport_array the relevant extension.