Bug 103300 - Tear rendering bug in Bioshock Infinite
Summary: Tear rendering bug in Bioshock Infinite
Status: NEEDINFO
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/radeonsi (show other bugs)
Version: 17.2
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-16 19:21 UTC by Ian Bruene
Modified: 2019-02-17 20:58 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
What is (2.28 MB, image/png)
2017-10-16 19:21 UTC, Ian Bruene
Details
What should be (80.63 KB, image/jpeg)
2017-10-16 19:22 UTC, Ian Bruene
Details
apitrace (66 bytes, text/plain)
2019-02-17 20:58 UTC, Ian Bruene
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Bruene 2017-10-16 19:21:27 UTC
Created attachment 134870 [details]
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.
Comment 1 Ian Bruene 2017-10-16 19:22:12 UTC
Created attachment 134871 [details]
What should be
Comment 2 Timothy Arceri 2018-09-10 03:19:18 UTC
Hi Ian,

Is this still a problem with a recent version of Mesa?

If so do you think you could get an apitrace [1] of the problem?

[1] https://github.com/apitrace/apitrace/wiki/Steam
Comment 3 Ian Bruene 2018-09-10 12:45:00 UTC
(In reply to Timothy Arceri from comment #2)
> Hi Ian,
> 
> Is this still a problem with a recent version of Mesa?

Tested with a just updated ubuntu 18.04 + padoka unstable. The problem still exists.

> If so do you think you could get an apitrace [1] of the problem?
> 
> [1] https://github.com/apitrace/apitrace/wiki/Steam

Will do, later today or tomorrow.
Comment 4 Ian Bruene 2018-09-11 04:37:41 UTC
(In reply to Timothy Arceri from comment #2)
> If so do you think you could get an apitrace [1] of the problem?
> 
> [1] https://github.com/apitrace/apitrace/wiki/Steam

I tried today and was unable to get a trace I'm afraid.
Comment 5 Timothy Arceri 2018-09-12 05:04:16 UTC
(In reply to Ian Bruene from comment #4)
> I tried today and was unable to get a trace I'm afraid.

Looks like the game is 32-bit so a 32bit build of apitrace is needed. 64bit distros usually only ship a 64-bit version of apitrace. For 32-bit you need to build from source [1].

If you manage to build it the you can just try loading steam like so:

LD_PRELOAD=/ ...path to apitrace git repo... /build32/wrappers/glxtrace.so steam

Then just launch the game and you should end up with a trace.

[1] https://github.com/apitrace/apitrace/blob/master/docs/INSTALL.markdown#linux
Comment 6 Timothy Arceri 2019-02-12 12:12:14 UTC
Another option if you can't get a trace would be to attach a saved game here so we can easily get to the right scene for testing.
Comment 7 Ian Bruene 2019-02-17 20:58:22 UTC
Created attachment 143393 [details]
apitrace

I was finally able to get a trace.

Current system is ubuntu 18.04, padoka-stable drivers. Bug still present.

The trace consists of loading the game, then the save. Running up to the spot with the missing texture, then quitting the game.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.