From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110370] Rendering artifacts in Enter The Gungeon on Both RX 590 and Radeon 7
Date: Wed, 10 Apr 2019 18:04:07 +0000 [thread overview]
Message-ID: <bug-110370-502-ZWqsorZmOB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110370-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 914 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110370
--- Comment #2 from andrew.m.mcmahon@gmail.com ---
I don't seem to suffer with poor performance even on an obsolete Phenom II x4
955. But now that you've mentioned when I notice a very slight bit of this
shimmering effect on my R9 285, admittedly not to the same degree as you.
It's quite noticeable on the first red step at the beginning of the game and
seems to shift around with the position of the game camera:
https://imgur.com/a/IBmHmhd
Using the GOG v2.1.5 release on:
> Debian Testing
> Linux-drm-fixes-5.1
> Mesa 19.1.0-devel (git-53f715fafb)
> Device: AMD Radeon R9 200 Series (TONGA, DRM 3.30.0, 5.1.0-rc1+, LLVM 8.0.0)
Recorded a trace running the x86 & x86_64 build of the game:
https://drive.google.com/drive/folders/10lYHjPXwkxVyUCQM2lJgKES_l2_HNKLg
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1902 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-04-10 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 12:32 [Bug 110370] Rendering artifacts in Enter The Gungeon on Both RX 590 and Radeon 7 bugzilla-daemon
2019-04-09 13:32 ` bugzilla-daemon
2019-04-10 18:04 ` bugzilla-daemon [this message]
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-110370-502-ZWqsorZmOB@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