Created attachment 130714 [details] Corrupted Screenshot of Total War Warhammer using 17.1 When I use Mesa 17.1 from the Padoka PPA the graphics of total war warhammer become corrupted. If I switch to Padoka stable (currently 17.0.2), after doing a ppa-purge, the issue is gone. My system: Kubuntu 16.04, with 4.8 kernel (the problem also exists with other kernel versions). CPU: Intel i5 3570 GPU: R9 290 RAM: 16GB DDR3 Game Version: 1.6.0 Graphics Settings: Very High (Problem exists with Low as well but is less obvious) glxinfo | grep 'version' server glx version string: 1.4 client glx version string: 1.4 GLX version: 1.4 Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.1.0-devel - padoka PPA OpenGL core profile shading language version string: 4.50 OpenGL version string: 3.0 Mesa 17.1.0-devel - padoka PPA OpenGL shading language version string: 1.30 OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.1.0-devel - padoka PPA OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
Some additional information: Quickest way to see the problem: Go to Options / Graphics / Advanced / Benchmark and start the benchmark The Oibaf PPA also has a problem lately but a different looking one (I'll add another screenshot). A few weeks ago the driver from Oibaf was working just fine in the game. The performance seems to be unaffected by the problems.
Created attachment 130721 [details] Screenshot showing weird colours on background textures using Oibaf PPA
Created attachment 130754 [details] Warhammer glitch padoka ppa after update on 2017-04-08 The padoka ppa was updated today Changes: mesa 1:17.1~git170407201100.c05cf9c~x~padoka0 Paulo Dias (9 hours ago) mesa 1:17.1~git170407201100.c05cf9c~y~padoka0 Paulo Dias (9 hours ago) libdrm 2.4.78+git1704072009.047aba1~x~padoka0 Paulo Dias (9 hours ago) libdrm 2.4.78+git1704072009.047aba1~y~padoka0 Paulo Dias (9 hours ago) Now both padoka and oibaf show the same error.
Hi. I also found some "shader color corruptions" on r9 270. I am using ubuntu 16.04 + kernel 4.11 + oibaf-ppa Having issues with unigine (valley/heaven), The long dark and compiz window shadow. Screenshots http://imgur.com/a/LaHdh
Some people reported this should actually got fixed by 0fb5a505fac7be0a1831b565019f0f04369e56bd, but looks like it isnt for all. https://bugs.freedesktop.org/show_bug.cgi?id=100531 Will test myself in some days...
(In reply to Gregor Münch from comment #5) > Some people reported this should actually got fixed by > 0fb5a505fac7be0a1831b565019f0f04369e56bd, but looks like it isnt for all. > https://bugs.freedesktop.org/show_bug.cgi?id=100531 > > Will test myself in some days... The "blue shadows" as shown in this screenshot https://bugs.freedesktop.org/show_bug.cgi?id=100531#c2 have been fixed for me with the latest update in the padoka ppa. What remains are the "fancy coloured textures" on my R9 290 (Hawaii, CGN 1.1) which were also reported on R9 270 (Curacao/Pitcairn, CGN 1.0) in unigine (valley/heaven) https://bugs.freedesktop.org/show_bug.cgi?id=100593#c4
Well its strange, this is completely fixed for me. So it should also be fixed on other GCN 1.0 cards. But looks like there is still a bug for GCN 1.1 cards.
Hi. My "shader color corruptions" bug was solved by "ppa-purge" and then again adding repository & updating. I was not using oibaf-ppa but padoka-ppa (https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa),
Oibaf still has problems on my R9 290. But with Padoka the issue is fixed now. However, Padoka is now installing mesa 17.2 git, so I have no idea, if it is fixed in the 17.1 branch.
(In reply to tarpoon from comment #9) > Oibaf still has problems on my R9 290. > > But with Padoka the issue is fixed now. However, Padoka is now installing > mesa 17.2 git, so I have no idea, if it is fixed in the 17.1 branch. Well I think we can close this if it's fixed in master. Other people can reopen the bug if they see the issue on 17.1.
I just did a retest with a freshly installed Kubuntu 17.04 with Padoka Stable (which means mesa 17.1.0 at the moment) The problem is completely fixed for me. Closing the bug. And thanks for the hard work everyone.
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.