dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106287] 18.0.1 introduced glitches in Dying Light
Date: Wed, 21 Nov 2018 21:39:16 +0000	[thread overview]
Message-ID: <bug-106287-502-CaCSfafH6Z@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106287-502@http.bugs.freedesktop.org/>


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

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

--- Comment #12 from Henrik Holst <henrik.holst2@gmail.com> ---
I upgraded to Ubuntu 18.04LTS a while back in order to test newer versions of
Mesa since Padoka PPA stopped supporting 14.04LTS and that broker the game
completely just as it previously had done for people on Arch and Manjaro.

However the recent discovery from
https://www.reddit.com/r/linux_gaming/comments/9jd2y0/how_to_play_dying_light_in_arch_linux/
that turned out that if you recompiled libgl.so.1.2.0 (this is in fact the
single lib that have to be replaced) without support for glvnd and then either
DL_PRELOAD:ing it or renaming it to libgl.so.1 and putting it in the game
folder of Dying Light makes it work again.

So now that I'm on both 18.2.4 and with the fix above the problem is completely
gone. Hard to tell if it's the mesa version or if it's the omission of glvnd
that fixed this very issue but considering that the game bugs out completely
without the glvnd-workaround I would guess that this was also the culprit
behind the original problem of mine.

So the problem lies probably in DL itself and not in mesa, just that 18.0.1
somehow exposed the problem.

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

[-- Attachment #1.2: Type: text/html, Size: 2174 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:[~2018-11-21 21:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-28  0:41 [Bug 106287] 18.0.1 introduced glitches in Dying Light bugzilla-daemon
2018-04-28 17:24 ` bugzilla-daemon
2018-05-07  1:58 ` bugzilla-daemon
2018-05-11 21:47 ` bugzilla-daemon
2018-06-02  2:35 ` bugzilla-daemon
2018-06-05 17:28 ` bugzilla-daemon
2018-06-05 23:29 ` bugzilla-daemon
2018-06-05 23:32 ` bugzilla-daemon
2018-06-11  2:40 ` bugzilla-daemon
2018-06-11 17:26 ` bugzilla-daemon
2018-06-15 19:28 ` bugzilla-daemon
2018-08-13 14:19 ` bugzilla-daemon
2018-09-12  5:38 ` bugzilla-daemon
2018-11-21 21:39 ` bugzilla-daemon [this message]
2018-11-29  4:21 ` bugzilla-daemon

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-106287-502-CaCSfafH6Z@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).