From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95528] BioShock Infinite graphical glitches on radeonsi
Date: Sat, 25 Jun 2016 19:36:07 +0000 [thread overview]
Message-ID: <bug-95528-502-XIOszaFaa0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95528-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1889 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95528
--- Comment #14 from Daniel Scharrer <daniel@constexpr.org> ---
Created attachment 124721
--> https://bugs.freedesktop.org/attachment.cgi?id=124721&action=edit
Trimmed R600_DEBUG=vs,ps output & shader GL calls with LLVM r273782
I could not record an apitrace (game hangs before getting to the main menu,
possibly performance related), but I was able to dump the shaders and narrow
down (some of) the affected ones.
The game uses two passes to render the flags and banners: The first pass
(possibly a z prepass?) uses pipeline=20 in the attached logs (vertex
shader=73, program=74; fragment shader=89, program=90).
The second pass is depth-tested against the results of the first, but uses
different shaders - pipeline=105 (vertex shader=383 program=384; fragment
shader=381, program=382).
With LLVM r266378 reverted, the results of the two passes line up, with current
LLVM they do not causing the z-fighting visible in the video linked in the bug
description. Even when disabling the depth test in the second pass, there are
still visible parts of "white" background so this is a) most likely an issue
with one of the vertex shaders and b) not just a depth precision issue. You can
also see this by looking closely at the flags in the video - the while (holes
punched by the z-prepass) and textured parts sway differently.
Since the game compiles an enormous amount of shaders on startup, the full
R600_DEBUG=cs,vs,tcs,tes,gs,ps output is quite large - I have attached a
trimmed output that only contains the two vertex/fragment shader pairs used for
the banners. The full logs are available at:
http://constexpr.org/tmp/bioshockinfinite-bad.log (20 MiB)
http://constexpr.org/tmp/bioshockinfinite-good.log (21 MiB)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3050 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:[~2016-06-25 19:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 20:53 [Bug 95528] BioShock issues on Tonga bugzilla-daemon
2016-05-22 20:55 ` bugzilla-daemon
2016-05-22 20:56 ` bugzilla-daemon
2016-05-22 21:08 ` bugzilla-daemon
2016-05-22 21:09 ` bugzilla-daemon
2016-05-24 7:01 ` bugzilla-daemon
2016-05-24 23:41 ` bugzilla-daemon
2016-05-24 23:43 ` bugzilla-daemon
2016-05-30 9:32 ` [Bug 95528] BioShock Infinite " bugzilla-daemon
2016-05-30 9:43 ` [Bug 95528] BioShock Infinite issues on Tonga/Hawaii bugzilla-daemon
2016-05-30 18:47 ` bugzilla-daemon
2016-06-07 9:22 ` bugzilla-daemon
2016-06-07 16:22 ` [Bug 95528] BioShock Infinite graphical glitches on radeonsi bugzilla-daemon
2016-06-23 2:22 ` bugzilla-daemon
2016-06-23 2:56 ` bugzilla-daemon
2016-06-25 19:36 ` bugzilla-daemon [this message]
2016-06-25 19:36 ` bugzilla-daemon
2016-06-30 15:24 ` bugzilla-daemon
2016-07-01 0:11 ` bugzilla-daemon
2016-07-01 0:15 ` bugzilla-daemon
2016-07-04 21:59 ` bugzilla-daemon
2016-07-29 7:24 ` 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-95528-502-XIOszaFaa0@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