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 97338] Black squares in the Spec Ops: The Line chapter select screen
Date: Sun, 14 Aug 2016 01:09:11 +0000	[thread overview]
Message-ID: <bug-97338-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 97338
           Summary: Black squares in the Spec Ops: The Line chapter select
                    screen
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: daniel@constexpr.org
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 125773
  --> https://bugs.freedesktop.org/attachment.cgi?id=125773&action=edit
Screenshot showing the bug (frame 89)

With radeonsi the chapter select screen in Spec Ops: The Line has black squares
that should not be there. I have not observed this bug elsewhere in the game
(but haven't played through the whole game using radeonsi).

The number of squares increases with a higher texture quality setting. The
number and positions of the squares only changes when the camera moves.

The chapter select screen renders fine using the amdgpu-pro driver - tested
with version 16.30.3.306809 running on the upstream amdgpu kernel module.

Apitrace:
 http://constexpr.org/tmp/SpecOps-radeonsi.trace.xz (70 MiB)

This bug seems to be caused by pixels with NaN values that make it into the
framebuffer and are extended to larger squares by a later post-processing pass:
After draw call 1441551, pixel (875, 573) of the COLOR0 attachment has RGB
components set to NaN.

GPU: R9 380X (tonga)
Kernel: 4.7.0-gentoo
Mesa: git-561fd22
LLVM: r278309

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

[-- Attachment #1.2: Type: text/html, Size: 3320 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

             reply	other threads:[~2016-08-14  1:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14  1:09 bugzilla-daemon [this message]
2016-08-14  1:10 ` [Bug 97338] Black squares in the Spec Ops: The Line chapter select screen bugzilla-daemon
2016-09-02 10:21 ` bugzilla-daemon
2016-09-02 12:54 ` bugzilla-daemon
2016-09-02 13:10 ` bugzilla-daemon
2016-11-23 21:45 ` bugzilla-daemon
2017-01-05 16:48 ` bugzilla-daemon
2017-01-10 22:36 ` bugzilla-daemon
2017-01-23  8:48 ` bugzilla-daemon
2017-01-23 10:47 ` bugzilla-daemon
2017-03-22 21:08 ` 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-97338-502@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).