<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - Dying Light reports OpenGL version 3.0 with mesa-git" href="https://bugs.freedesktop.org/show_bug.cgi?id=96449#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - Dying Light reports OpenGL version 3.0 with mesa-git" href="https://bugs.freedesktop.org/show_bug.cgi?id=96449">bug 96449</a> from <a class="email" href="mailto:abolte@systemsaviour.com" title="Adam Bolte <abolte@systemsaviour.com>"> Adam Bolte</a> <pre>Confirming, it works now - provided I set the MESA_GL_VERSION_OVERRIDE first. Failure to set this causes a blank screen (but audio can be heard from the intro video). The following game launch option can be set in Steam: MESA_GL_VERSION_OVERRIDE=4.1 %command% 4.1 is the minimum that works and does not throw the warning box (shown in Jan's attached image). Setting the override to 3.3 also gets the game to run (I didn't bother testing any lower than that), but with the warning. The game still runs too slow to be enjoyable - it's borderline unplayable. I was never able to hit 30 FPS (quite bad for this type of game), but at least it's running. Having said that, using MESA_GL_VERSION_OVERRIDE=4.5 seems to give me a few extra in-game FPS. My overclocked i7-6700k and Fury X at 2560x1440 with high detail settings and maximum draw depth (but no AA and motion blur) was giving me on average around 26 FPS in the camp where I restored my save point from (running back and forth), whereas I was never able to get past 23 FPS in the same area by setting the override to 4.1. I tested that twice to be sure. Would be great if there were a way to take care of these overrides automatically in drirc - which is what this bug was originally about. Are we certain this is still WONTFIX?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>