From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 96449] Dying Light reports OpenGL version 3.0 with mesa-git Date: Sun, 21 May 2017 05:50:25 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1708711370==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 450F76E035 for ; Sun, 21 May 2017 05:50:25 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1708711370== Content-Type: multipart/alternative; boundary="14953458250.a6F5B1.11879"; charset="UTF-8" --14953458250.a6F5B1.11879 Date: Sun, 21 May 2017 05:50:25 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D96449 --- Comment #16 from Adam Bolte --- Confirming, it works now - provided I set the MESA_GL_VERSION_OVERRIDE firs= t. 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=3D4.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 ru= n (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=3D4.5 seems to give me a f= ew 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 givi= ng 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? --=20 You are receiving this mail because: You are the assignee for the bug.= --14953458250.a6F5B1.11879 Date: Sun, 21 May 2017 05:50:25 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 16 on bug 96449<= /a> from Adam Bolte 
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=3D4.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 ru=
n (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=3D4.5 seems to give me a f=
ew
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 givi=
ng
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?

You are receiving this mail because:
  • You are the assignee for the bug.
= --14953458250.a6F5B1.11879-- --===============1708711370== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1708711370==--