From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110658] MXGP3 (Steam, native Linux port, UE4): graphical glitches
Date: Wed, 29 May 2019 15:12:22 +0000 [thread overview]
Message-ID: <bug-110658-502-oDeu14AxRY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110658-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 738 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110658
--- Comment #5 from Alexander Mezin <mezin.alexander@gmail.com> ---
(In reply to Timothy Arceri from comment #3)
> Are you able to test with llvm 9?
I won't have time for that until weekend
(In reply to Timothy Arceri from comment #4)
> I've run it on llvm 8 and mesa 19.0.5 and was unable to reproduce the issues
> seen in the screen capture on my Vega 64.
Just re-tested with mesa 19.0.5+llvm 8, the issue is still there.
It seems to be track-specific. At least it doesn't happen on "Compound", for
example.
Also the game runs fine under Proton/SteamPlay (no glitches/artifacts).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1721 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-29 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 5:13 [Bug 110658] MXGP3 (Steam, native Linux port, UE4): graphical glitches bugzilla-daemon
2019-05-27 3:28 ` bugzilla-daemon
2019-05-27 4:04 ` bugzilla-daemon
2019-05-27 4:58 ` bugzilla-daemon
2019-05-29 5:33 ` bugzilla-daemon
2019-05-29 15:12 ` bugzilla-daemon [this message]
2019-05-31 23:19 ` bugzilla-daemon
2019-09-25 18:49 ` 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-110658-502-oDeu14AxRY@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