| 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 [details]<=
/a>
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. W=
hen
I encounter them the sprite is missing. This only effects the tears that ha=
ve
the "static" in them (the music, three truths, and Elizabeth scre=
aming 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 (s=
team
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 loo=
k.
| What | Removed | Added |
|---|---|---|
| Status | NEW | NEEDINFO |
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://git= hub.com/apitrace/apitrace/wiki/Steam
(In reply to Timothy Arceri from comment #2) > Hi Ian, >=20 > 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? >=20 > [1] https:= //github.com/apitrace/apitrace/wiki/Steam Will do, later today or tomorrow.
(In reply to Timothy Arceri from comment #2) > If so do you think you could get an apitrace [1]= of the problem? >=20 > [1] https:= //github.com/apitrace/apitrace/wiki/Steam I tried today and was unable to get a trace I'm afraid.
(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=3D/ ...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
Another option if you can't get a trace would be to attach a s= aved game here so we can easily get to the right scene for testing.
Created attachment 143393 [detai=
ls]
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 sp=
ot
with the missing texture, then quitting the game.
For some reason the rendering when I replay the trace is compl= etely broken for me.
| What | Removed | Added |
|---|---|---|
| Status | NEEDINFO | RESOLVED |
| Resolution | --- | MOVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1285.