Good news for those of you using an AMD GPU, as Mesa with radeonsi now has support for compatibility profiles up to OpenGL 4.4.
Why is it important to have this? To put it simply, there's a few games out there that required it and wouldn't run without it. It's another tick in the box for getting the best experience possible for those with an AMD GPU using open source graphics drivers on Linux.
Going by what the developer said, this in particular helps with games like Doom and Wolfenstein run in Wine. It's also something that should hopefully help to fix Dying Light, Dead Island Definitive Edition, Grand Ages: Medieval, Black Mesa and probably quite a few more that required it.
It's currently only in Mesa-git, the development version, meaning it should hopefully make the Mesa 18.2 release. The first RC of Mesa 18.2 is expected around July 20th, with a release due in August going by their release calendar.
Thanks for the tip, mirv.
Quoting: pete910Quoting: F.UltraQuoting: pete910Quoting: F.UltraQuoting: pete910Quoting: ShmerlYep, it shows up in the OpenGL string now:
OpenGL renderer string: Radeon RX Vega (VEGA10, DRM 3.25.0, 4.17.0-trunk-amd64, LLVM 6.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.0-devel (git-2854c0f795)
OpenGL core profile shading language version string: 4.50
OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.0-devel (git-2854c0f795)
OpenGL shading language version string: 4.40
Killing compat profile could have made sense if Khronos would have done it. But they didn't, and now it's proliferated in Nvidia blob, so some clueless developers use it despite many warnings not to, and you get results like Dying Light. There is no option for Mesa but to implement it.
Does Dying Light work for you ?
You can already make Dying Light run on stable mesa if you set the Launch Options in Steam to "MESA_GL_VERSION_OVERRIDE=4.5 MESA_GLSL_VERSION_OVERRIDE=450 %command%" the great thing with the new patches is that such workarounds will no longer be necessary.
edit: however reading the mesa-dev post it seams that this perhaps does fix some stability for Dying Light that the override did not. In that case this change is even better :)
As mentioned numerous times, that fix does not work for arch users or even non *buntu based distros. :(
Yeah I know but that should indicate that the problem on Arch is something else. I do hope that this is where I'm totally wrong so that things will start to work for you Arch-guys as well.
It's not just arch seems to be anything other than *ubuntu/debian but I agree hope its fixed soon too, I have already played through it once so not a major issue but it's a good co-op game.
Just upgraded to Ubuntu 18.04LTS from 16.04 and Dying Light crashes after the loading screen. So I guess that the rumours that I heard on Phoronix that this is somehow related to a new version of glibc might be true.
Quoting: F.UltraJust upgraded to Ubuntu 18.04LTS from 16.04 and Dying Light crashes after the loading screen. So I guess that the rumours that I heard on Phoronix that this is somehow related to a new version of glibc might be true.
Hey, I was with the same problem and think that was something with glibc. But compiling Mesa 18.2 RC3 solved the issue. Dying Light works as used to with latest Mesa drivers (well, maybe better as it works without the start parameters).
Last edited by x_wing on 25 August 2018 at 9:03 pm UTC
Quoting: x_wingQuoting: F.UltraJust upgraded to Ubuntu 18.04LTS from 16.04 and Dying Light crashes after the loading screen. So I guess that the rumours that I heard on Phoronix that this is somehow related to a new version of glibc might be true.
Hey, I was with the same problem and think that was something with glibc. But compiling Mesa 18.2 RC3 solved the issue. Dying Light works as used to with latest Mesa drivers (well, maybe better as it works without the start parameters).
Think I'll just hang back and wait for 18.2 to release. Hope it is fixed. Do we know if they are doing a linux client for their upcoming game ?
See more from me