https://bugs.winehq.org/show_bug.cgi?id=43748
--- Comment #11 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Tod Jackson from comment #10)
When I saw it was a multisampling issue this came to mind, something I've always seen in chrome://gpu: Multisampling is buggy in Intel IvyBridge: 116370 Applied Workarounds: disable_chromium_framebuffer_multisample http://crbug.com/116370
Unclear but probably not related.
Sorry, what's this GPU override mean? I probably didn't do it on purpose.
I looked that up again in the older Wine sources and it looks like, contrarily to what I thought previously, that trace was always printed at the time. Nothing to see here, sorry for the noise.
Also, any clue why the game works with MESA_EXTENSION_MAX_YEAR=2010?
Right, I forgot about that part. The patch causing this regression essentially started asking the driver for detailed per-format, per-sample-count multisampling support. For that it uses the ARB_internalformat_query extension which is marked in the Mesa sources with the 2011 year. So by setting the environment variable you're practically disabling the new "detailed" codepath and falling back to the previous behavior, which is to advertise all the multisample levels up to MAX_SAMPLES. If the game later on wants to create a texture with sample count 2, which is apparently unsupported by your GPU, that is automatically "upgraded" to the lowest supported count (probably 4) and everything SHOULD keep working.
So good catch and probably a good workaround for this bug.