Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal. You can also buy games using our partner links for GOG and Humble Store.
We do often include affiliate links to earn us some pennies. See more here.

NVIDIA have pushed out the second Vulkan Beta Driver in the space of a week, with 435.27.07 now available for Linux.

Quite a small one this time, mainly just fixing up some issues found:

  • Fixed a bug that caused graphical corruption, reducing visibility in caves, in Steam Play title Assassin's Creed: Odyssey
  • Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system

Really good to see NVIDIA react so fast to issues, their drivers have come a long way in a few years.

Another reminder to prevent some confusion: 440.31 is the latest stable Linux driver, which is a different series to the Vulkan and OpenGL Beta drivers which usually have the extra two version points at the end. Eventually, changes from the Vulkan/OpenGL Betas make it into the stable series.

You can find the Vulkan Beta Drivers here.

Article taken from GamingOnLinux.com.
Tags: Beta, Drivers, Vulkan
9 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
The comments on this article are closed.
6 comments

Ehvis Nov 15, 2019
View PC info
  • Supporter Plus
QuoteFixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system

Now that's the fix that I wanted to see!
Beamboom Nov 15, 2019
I don't really understand all these title specific "fixes": The games are obviously all using the same graphics APIs, so isn't this essentially a bug on the application side?

I mean, most upgrades of the nvidia drivers, regardless of platform, are largely due to very specific issues in very specific games. It all sounds *so* application specific, I am wondering if not Nvidia are running the errands of the engine makers / game makers?
Or what's really going on here?
beko Nov 15, 2019
Quoting: BeamboomI don't really understand all these title specific "fixes": The games are obviously all using the same graphics APIs, so isn't this essentially a bug on the application side?
I'd wager that specific games are just the first to hit and report such issues. Read it more like a courtesy note instead of messages like "Fixed a bug where X broke when Y was called while Z was void" 😜
Ehvis Nov 15, 2019
View PC info
  • Supporter Plus
Quoting: BeamboomI don't really understand all these title specific "fixes": The games are obviously all using the same graphics APIs, so isn't this essentially a bug on the application side?

I don't think the fix is specifically for the game. The way I see it is that Vulkan drivers are relatively new and so are the Vulkan compatibility tests. Both are still evolving through experience. Nvidia probably recognised quickly that DXVK provided a much bigger test bed than the slowly appearing native games, which is why several Nvidia devs are active in the issues list. Currently these games are probably hitting (valid) corner cases where the driver needs a slight adjustment or maybe even a clarification of the spec.
jens Nov 15, 2019
  • Supporter
Quoting: Ehvis
Quoting: BeamboomI don't really understand all these title specific "fixes": The games are obviously all using the same graphics APIs, so isn't this essentially a bug on the application side?

I don't think the fix is specifically for the game. The way I see it is that Vulkan drivers are relatively new and so are the Vulkan compatibility tests. Both are still evolving through experience. Nvidia probably recognised quickly that DXVK provided a much bigger test bed than the slowly appearing native games, which is why several Nvidia devs are active in the issues list. Currently these games are probably hitting (valid) corner cases where the driver needs a slight adjustment or maybe even a clarification of the spec.

Yes, seems like a win for both parties. The same applies to AMD/Mesa drivers as well I guess. DXVK contributed massively for getting all Vulkan drivers to a next level.
Comandante Ñoñardo Nov 19, 2019
It seems the people behind the graphics-drivers PPA are dead.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.