|Summary:||Civilization VI - Animated leader characters small black squares artifacts|
|Product:||Mesa||Reporter:||Hadrien Nilsson <freedesktop>|
|Component:||Drivers/Gallium/radeonsi||Assignee:||Default DRI bug account <dri-devel>|
|Status:||RESOLVED MOVED||QA Contact:||Default DRI bug account <dri-devel>|
|i915 platform:||i915 features:|
|Attachments:||A leader character covered with multiple small black squares|
Description Hadrien Nilsson 2018-10-04 05:33:05 UTC
Created attachment 141871 [details] A leader character covered with multiple small black squares See the attached picture. I'm not sure if the problem is related to bug 108111 so I prefer opening a new one. If both are related to a LLVM regression it's possible we'll be able to close both. Computer info: OpenGL renderer string: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.23.0, 4.15.0-34-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 - padoka PPA
Comment 1 Hadrien Nilsson 2018-10-13 21:48:31 UTC
This is actually another issue than bug 108111: I upgraded from Mesa 18.2.1 to 18.2.2. bug 108111 is fixed, but the characters are still displayed with these small black squares.
Comment 2 Timothy Arceri 2018-11-01 00:48:47 UTC
I couldn't reproduce. Do you think you could get an apitrace  of the problem? Also if you were able to test 18.3 that would be great too.  https://github.com/apitrace/apitrace/wiki/Steam
Comment 3 Timothy Arceri 2018-11-01 06:48:18 UTC
It's also possible this is another example of bug #104602
Comment 4 Hadrien Nilsson 2018-11-01 11:54:25 UTC
I'm not sure for bug 104602 as everything else renders correctly. --------------- I installed a fresh version of Ubuntu 18.04 on a specific disk and added padoka unstable ppa for mesa. I got this version: 1:18.3~git181021202700.2d235d6~b~padoka0 And the bug is still present. I also installed Ubuntu 18.10 (kernel 4.18), used the stock mesa (18.2.2), and the bug was there too. --------------- I have two concerns about apitrace: 1. the apitrace file will be full of copyrighted assets. Isn't there a legal risk to share such a file on the Internet? 2. Civilization is a huge game and I'm afraid the apitrace file will be huge too (I need to reach the Leader screen before stopping the recording). What is the best way to share huge apitrace files with Mesa developers? --------------- Maybe I could also enable some kind of error logging, or a dump of compiled shaders? By the way, the rendering level for Leaders is set to "low". I'm back on my daily installation, with Mesa 18.2.3. In case in can help, here are my LLVM versions: ii libllvm6.0:amd64 1:6.0-1ubuntu2 amd64 Modular compiler and toolchain technologies, runtime library ii libllvm6.0:i386 1:6.0-1ubuntu2 i386 Modular compiler and toolchain technologies, runtime library ii libllvm7:amd64 1:7-2~oibaf~b amd64 Modular compiler and toolchain technologies, runtime library ii libllvm7:i386 1:7-2~oibaf~b i386 Modular compiler and toolchain technologies, runtime library
Comment 5 Timothy Arceri 2019-02-12 12:18:46 UTC
Possibly related to bug 104602. Can you try the workaround from that bug report.
Comment 6 Timothy Arceri 2019-02-12 12:23:06 UTC
To be clear. Can you right click on the game in steam, select properties. Then click 'Set Launch Options'. In here add: R600_DEBUG=nir %command% Click ok, and close the properties window. Then launch the game.
Comment 7 Dieter Nützel 2019-02-12 16:26:20 UTC
If I read this right Civilization VI in an OpenGL game? Without shifting the focus to much have anyone maybe set EQAA filtering? I've found an EQAA regression with TGSI and NIR running DiRT Rally on our Polaris 20. Same corruption. unset EQAA helps, here. I've did some testing for Marek and Nicolai in April/May/June 2018 and have now to bisect.
Comment 8 Hadrien Nilsson 2019-02-12 18:19:46 UTC
I started both Steam and the game with R600_DEBUG=nir, it has no effect on the bug. Graphics settings are all either "Low" or "Disabled", with the exception of v-sync. This includes anti-aliasing (thus no EQAA). My system was slightly upgraded to kernel 4.20 and Mesa 18.3.3 (the bug is still here and looks the same).
Comment 9 Timothy Arceri 2019-08-27 23:57:52 UTC
Do you think you can test git master now that this fix  has landed?  https://cgit.freedesktop.org/mesa/mesa/commit/?id=360cf3c4b05679709574ef4d20b5097b0fd0be82
Comment 10 GitLab Migration User 2019-09-25 18:09:58 UTC
-- 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/1330.