From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106287] 18.0.1 introduced glitches in Dying Light
Date: Tue, 05 Jun 2018 17:28:23 +0000 [thread overview]
Message-ID: <bug-106287-502-RB1vQ7ipM1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106287-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 465 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106287
--- Comment #5 from stupot@gmail.com ---
Adding more, barely useful information.
Sometimes, I can start the game and the issues aren't there. Sometimes I
start the game and they are there. It's apparent at the start (the menu screen
actually). Seems like there's some luck as to initialization/threading
involved to me.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1206 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
next prev parent reply other threads:[~2018-06-05 17:28 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 [this message]
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
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-RB1vQ7ipM1@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).