All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96449] Dying Light reports OpenGL version 3.0 with mesa-git
Date: Sun, 21 May 2017 05:50:25 +0000	[thread overview]
Message-ID: <bug-96449-502-DnCt6aHIeY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96449-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1508 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=96449

--- Comment #16 from Adam Bolte <abolte@systemsaviour.com> ---
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?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2355 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2017-05-21  5:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09  9:42 [Bug 96449] Dying Light reports OpenGL version 3.0 with mesa-git bugzilla-daemon
2016-06-09  9:43 ` bugzilla-daemon
2016-06-09 10:53 ` bugzilla-daemon
2016-06-09 12:39 ` bugzilla-daemon
2016-06-09 13:34 ` bugzilla-daemon
2016-06-10 10:09 ` bugzilla-daemon
2016-06-10 12:34 ` bugzilla-daemon
2016-09-18 23:40 ` bugzilla-daemon
2016-09-19 11:40 ` bugzilla-daemon
2016-09-20  0:37 ` bugzilla-daemon
2016-10-14  9:38 ` bugzilla-daemon
2016-10-17 22:24 ` bugzilla-daemon
2016-10-17 22:27 ` bugzilla-daemon
2016-10-17 22:48 ` bugzilla-daemon
2016-10-17 22:52 ` bugzilla-daemon
2017-05-20 15:34 ` bugzilla-daemon
2017-05-21  5:50 ` bugzilla-daemon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-96449-502-DnCt6aHIeY@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.