All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103300] Tear rendering bug in Bioshock Infinite
Date: Mon, 16 Oct 2017 19:21:27 +0000	[thread overview]
Message-ID: <bug-103300-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 103300
           Summary: Tear rendering bug in Bioshock Infinite
           Product: Mesa
           Version: 17.2
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: ianbruene@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 134870
  --> https://bugs.freedesktop.org/attachment.cgi?id=134870&action=edit
What is

Running Ubuntu 17.04, kernel 4.12.11, mesa 17.2.2 padoka-stable (but it
appeared in an earlier version), RX 460.

In Bioshock Infinite there are "tears" which graphically consist of a swirly
glowy cloud thing and a sprite that looks like a tear with static inside. When
I encounter them the sprite is missing. This only effects the tears that have
the "static" in them (the music, three truths, and Elizabeth screaming ones),
but does not effect any of the story or combat tears.

What few tests I know how to do eliminate corruption in the installation (steam
verifies it), or corrupted shader cache (deleted that). I am *not* certain that
this is a driver bug, but it seems to lean in that direction.

Attached is a screenshot of how it looks on my system, vs how it should look.

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

[-- Attachment #1.2: Type: text/html, Size: 3016 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:[~2017-10-16 19:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 19:21 bugzilla-daemon [this message]
2017-10-16 19:22 ` [Bug 103300] Tear rendering bug in Bioshock Infinite bugzilla-daemon
2018-09-10  3:19 ` bugzilla-daemon
2018-09-10 12:45 ` bugzilla-daemon
2018-09-11  4:37 ` bugzilla-daemon
2018-09-12  5:04 ` bugzilla-daemon
2019-02-12 12:12 ` bugzilla-daemon
2019-02-17 20:58 ` bugzilla-daemon
2019-02-18  0:11 ` bugzilla-daemon
2019-09-25 18:00 ` 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-103300-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.