| Bug ID | 98974 |
|---|---|
| Summary | Can't see borders/empires in Stellaris |
| Product | Mesa |
| Version | git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/r600 |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | lukas.fuernkranz+bugzilla2@gmail.com |
| QA Contact | dri-devel@lists.freedesktop.org |
I'm using Ubuntu 16.04 and an AMD Radeon 6870 with the drivers= from h= ttps://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers. In Stellaris (a video game) I can't see the borders/empires on the map. Un= less I set the graphics quality to low that is. (Temporarily I used an AMD R9 270x---also with the drivers from the oibaf P= PA; radeonsi though---and there I didn't have that problem.) In case more infos are needed please say so and I'll do my best to provide = it.
| What | Removed | Added |
|---|---|---|
| QA Contact | dri-devel@lists.freedesktop.org | mesa-dev@lists.freedesktop.org |
| Assignee | dri-devel@lists.freedesktop.org | mesa-dev@lists.freedesktop.org |
| Component | Drivers/Gallium/r600 | Mesa core |
I can verify this bug on Archlinux using the i965 driver on bo= th HSW and SKL, thus moving to mesa core. On i965 I'm using low settings but see no borders for my own empire, but ot= her empires get a light grey border. I can also verify that the game works correctly on the Nvidia blob on Steam= OS.
| What | Removed | Added |
|---|---|---|
| QA Contact | mesa-dev@lists.freedesktop.org | dri-devel@lists.freedesktop.org |
| Assignee | mesa-dev@lists.freedesktop.org | dri-devel@lists.freedesktop.org |
| Component | Mesa core | Drivers/Gallium/r600 |
I can verify this bug with an AMD Radeon HD 6870 and Mesa 17.0= .5 on Fedora. The Stellaris mod "Patch for r600 GPUs" fixed indeed this bug, bu= t the real bug is in Mesa. This bug seems to only affect AMD GPUs with r600 driver (Intel GPU fixed a similar bug with same effects in a previous Mesa version). There's no usefull logs from Stellaris nor crash dump.
With apitrace there is a lot of : EE r600_shader.c:3663 r600_shader_from_tgsi - GPR limit exceeded - shader requires 213 registers EE r600_shader.c:183 r600_pipe_shader_create - translation from TGSI failed= ! EE r600_state_common.c:799 r600_shader_select - Failed to build shader vari= ant (type=3D1) -12 EE r600_shader.c:3663 r600_shader_from_tgsi - GPR limit exceeded - shader requires 215 registers EE r600_shader.c:183 r600_pipe_shader_create - translation from TGSI failed= ! EE r600_state_common.c:799 r600_shader_select - Failed to build shader vari= ant (type=3D1) -12
Could you check whether the bug persists in 17.3.0? It include= s patches that improve the register allocation on r600.=20 If this doesn't fix the bug, could you post an apitrace?
I have a thinkpad x220 (Intel HD 3000 integrated graphics). I=
can confirm that
this bug is fixed for me with MESA 17.2.4
/--------------------------------------------------------------------------/
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
Max core profile version: 3.3
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.2.4
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.0 Mesa 17.2.4
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.2.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
/--------------------------------------------------------------------------/
Bug was present in previous MESA version, I believe it was ~17.0.5.
I'm using Stellaris v1.9 through the Steam client on Linux Min= t 18.3 with the MATE desktop.
@James Lovinsky: since you are running the game on Intel g= raphics hardware you probably saw #95530, this bug refers to AMD hardware (r600).
Sorry, my mistake. Will refer to #95530, thanks!
(In reply to Gert Wollny from comment #14) > Could you check whether the bug persists in 17.3= .0? It includes patches=20 > that improve the register allocation on r600.=20 >=20 > If this doesn't fix the bug, could you post an apitrace? I can test it in two weeks at the earliest. If someone beat me to it that would be great. However, if nobody does that and you don't hear back from = me within three weeks please remind me about this issue.
| What | Removed | Added |
|---|---|---|
| CC | bugs.freedesktop@johnthomson.fastmail.com.au |
(In reply to Gert Wollny from comment #14) > If this doesn't fix the bug, could you post an a= pitrace? mesa 17.3.2 no galaxy map borders apitrace: DEBUGGER=3D"apitrace trace" steam-native steam://rungameid/281990 https://www.dropbox.com/s/a8d38yoaeu7n9uy/stellaris_nobor= ders_r600g.trace?dl=3D1 SHA256(stellaris_noborders_r600g.trace)=3D bfc9f724dff5f27a3b3670a15b0bdd72c14b049e047c9194d22fe0651f653888 EE r600_shader.c:3672 r600_shader_from_tgsi - GPR limit exceeded - shader requires 213 registers EE r600_shader.c:183 r600_pipe_shader_create - translation from TGSI failed= ! EE r600_state_common.c:787 r600_shader_select - Failed to build shader vari= ant (type=3D1) -12 AMD 5850 DRI3 Arch Linux=20 Stellaris 1.9.1 Is there a preferred apitrace file host? Thanks
I now see borders with versions: Stellaris v2.0.1 Linux 4.15.6 mesa 17.3.6 xorg 1.19.6
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | FIXED |
Marking as fixed as per comment 21. Please reopen if there are still issues.