Released yesterday, both Mesa 18.1.8 as a bug-fix release and Mesa 18.2.0 as the latest full release of the open source graphics drivers are now out. As usual, the Mesa team are suggesting you wait for Mesa Mesa 18.2.1 if you plan to upgrade, at least if you want a fully stable experience.
For the RadeonSI (AMD) driver, it now has compatibility profile support up to OpenGL 4.4. This is quite important for historic reasons, since there will be applications and games that rely on it that won't be updated (including for us in Steam Play/Wine). Personally, I think that's one of the more important features of this release, since it will give users a better experience. RadeonSI also now has compute shader support in the Mesa shader cache.
There's also various improvements to the Intel ANV Vulkan driver, various performance improvements, bug fixes and much more. Since I don't personally use Mesa, having an NVIDIA 980ti I use their proprietary driver so I'm not exactly too up to speed on it all. Great to see it progress though! If you want a more in-depth look, Phoronix has their usual overview.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Wonder if this will fix Dying light for non *butu users ?
And before anyone chimes in with " you just need to add..." They don't work!
And before anyone chimes in with " you just need to add..." They don't work!
0 Likes
Quoting: pete910Wonder if this will fix Dying light for non *butu users ?
And before anyone chimes in with " you just need to add..." They don't work!
DL wasn't working on Ubuntu 18.04 with Mesa 18.1, but using Mesa 18.2RC made it work (for me and many others, I think). So, try to test it and share your results.
0 Likes
Quoting: x_wingQuoting: pete910Wonder if this will fix Dying light for non *butu users ?
And before anyone chimes in with " you just need to add..." They don't work!
DL wasn't working on Ubuntu 18.04 with Mesa 18.1, but using Mesa 18.2RC made it work (for me and many others, I think). So, try to test it and share your results.
I thought the problem with DL was with the new version of glibc?
0 Likes
Quoting: ziabiceFinally I can put my hands on RAGE and Wolfenstein!
Been playing Rage. Although only 64bit works properly for me and I had to add xact to get the sound working.
I need to do some driver testing to see if its just a buggy version of mesa-git, but 32bit Rage and Wolfenstein N.O. tend to crash in the menus.
0 Likes
Quoting: x_wingQuoting: pete910Wonder if this will fix Dying light for non *butu users ?
And before anyone chimes in with " you just need to add..." They don't work!
DL wasn't working on Ubuntu 18.04 with Mesa 18.1, but using Mesa 18.2RC made it work (for me and many others, I think). So, try to test it and share your results.
Just tried with the Arch testing packages.... No go.
I'll look into it a bit more, time permitting.
0 Likes
Quoting: F.UltraQuoting: x_wingQuoting: pete910Wonder if this will fix Dying light for non *butu users ?
And before anyone chimes in with " you just need to add..." They don't work!
DL wasn't working on Ubuntu 18.04 with Mesa 18.1, but using Mesa 18.2RC made it work (for me and many others, I think). So, try to test it and share your results.
I thought the problem with DL was with the new version of glibc?
Arrrh that's right, damn!
Quoting: stormaQuoting: x_wingQuoting: pete910Wonder if this will fix Dying light for non *butu users ?
And before anyone chimes in with " you just need to add..." They don't work!
DL wasn't working on Ubuntu 18.04 with Mesa 18.1, but using Mesa 18.2RC made it work (for me and many others, I think). So, try to test it and share your results.
Just tried with the Arch testing packages.... No go.
I'll look into it a bit more, time permitting.
Looks like it is a glibc issue. :'(
0 Likes
Quoting: pete910Quoting: F.UltraQuoting: x_wingQuoting: pete910Wonder if this will fix Dying light for non *butu users ?
And before anyone chimes in with " you just need to add..." They don't work!
DL wasn't working on Ubuntu 18.04 with Mesa 18.1, but using Mesa 18.2RC made it work (for me and many others, I think). So, try to test it and share your results.
I thought the problem with DL was with the new version of glibc?
Arrrh that's right, damn!
Quoting: stormaQuoting: x_wingQuoting: pete910Wonder if this will fix Dying light for non *butu users ?
And before anyone chimes in with " you just need to add..." They don't work!
DL wasn't working on Ubuntu 18.04 with Mesa 18.1, but using Mesa 18.2RC made it work (for me and many others, I think). So, try to test it and share your results.
Just tried with the Arch testing packages.... No go.
I'll look into it a bit more, time permitting.
Looks like it is a glibc issue. :'(
Anyone that knows what kind of magic that Steam adds when running games? I've tried to rename "DyingLightGame" to "DyingLightGame.exe" and then created a small shell script named "DyingLightGame" that just did "./DyingLightGame.exe" as a preparation for doing glibc preload but the game refused to start even with such a basic script (it couldn't find the steam overlay I think it complained about) so it looks like Steam does more than just execute the binary.
0 Likes
Quoting: F.UltraAnyone that knows what kind of magic that Steam adds when running games? I've tried to rename "DyingLightGame" to "DyingLightGame.exe" and then created a small shell script named "DyingLightGame" that just did "./DyingLightGame.exe" as a preparation for doing glibc preload but the game refused to start even with such a basic script (it couldn't find the steam overlay I think it complained about) so it looks like Steam does more than just execute the binary.No need for custom scripts. You can add your LD_PRELOAD magic to the game's launch options. Right click the game in your library, select "Properties" -> "SET LAUNCH OPTIONS...":
LD_PRELOAD=path_to_lib.so %command%Just bear in mind that when it comes to Dying Light and glibc, others have tried and failed. I hope you have better luck.
Last edited by tuubi on 9 September 2018 at 8:04 pm UTC
1 Likes, Who?
Quoting: lejimsterI think this is the problem:Quoting: ziabiceFinally I can put my hands on RAGE and Wolfenstein!
Been playing Rage. Although only 64bit works properly for me and I had to add xact to get the sound working.
I need to do some driver testing to see if its just a buggy version of mesa-git, but 32bit Rage and Wolfenstein N.O. tend to crash in the menus.
https://cgit.freedesktop.org/mesa/mesa/commit/?id=bc65dcab3bc48673ff6180afb036561a4b8b1119
Though I'm seeing hangs, not crashes, in the menu in Rage, haven't tried Wolfenstein yet.
Could you try if this fixes the problem for you?
https://pastebin.com/iwGynY9E
0 Likes
Patreon
PayPal
See more from me