Check out our Monthly Survey Page to see what our users are running.
We do often include affiliate links to earn us some pennies. See more here.

NVIDIA just quietly released another fresh update to their special developer-focused Vulkan Beta Driver.

After moving it over to the 455 series at the end of September, they released driver version 455.26.01 on October 9 which is a small bug-fix cleanup with these changes:

  • Reduce host memory consumption for descriptor memory when VkDescriptorSetVariableDescriptorCountAllocateInfo is used
  • Handle SPIR-V 1.4 non-Input/Ouput entry point variables correctly
  • Fixed a blending optimization that sometimes produced an incorrect result
  • Fixed SPIR-V intersection shader compilation issue when multi entry point ray tracing modules are used

Reminder: This special Vulkan beta driver is where all the shiny new stuff goes in before making its way into the stable release for everyone. Really, it's mostly aimed at developers and serious enthusiasts. Unless you need what's in them, it's generally best to use the stable drivers.

The newest stable versions of the main NVIDIA driver for Linux are at 450.80.02 released on September 30 from their "long lived" series or 455.28 released on October 7 from their "short lived" series. The difference can be a little confusing, NVIDIA explained the difference between short / long lived drivers as:

Any given release branch is either long-lived or short-lived. The difference is in how long the branch is maintained and how many releases are made from each branch. A short-lived branch typically has only one or two (non-beta) releases, while long-lived branches will have several.
[…]
When we make changes to the driver, we evaluate the oldest branch the change needs to go into. New features go into whatever the latest branch is, while bug fixes go into the older branches and are integrated through the newer branches. So using a short-lived branch doesn’t mean that you miss out on fixes, it just means that you also get the latest features.

Want to keep up with the latest Linux driver updates? You can follow our dedicated Drivers tag, all our tags have an RSS feed you can follow.

Article taken from GamingOnLinux.com.
11 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. You can also follow my personal adventures on Bluesky.
See more from me
The comments on this article are closed.
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
9 comments

Schattenspiegel Oct 10, 2020
Wish they would just mark l=long s=short and b=beta somewhere in there so people do not have to guess or look it up every time.
Liam Dawe Oct 10, 2020
Wish they would just mark l=long s=short and b=beta somewhere in there so people do not have to guess or look it up every time.
They do on the main list.
Schattenspiegel Oct 10, 2020
They do on the main list.
Thank you ! Good to know. It does fall into the look it up category unfortunately, though.
TheRiddick Oct 10, 2020
I hope someone gets RTX titles working under Linux soon, that be neat. (via proton I guess)
Liam Dawe Oct 11, 2020
I hope someone gets RTX titles working under Linux soon, that be neat. (via proton I guess)
This is a common misconception by people, sometimes just poor wording that I keep seeing repeated.

RTX is supported on Linux, has been for multiple years already. What doesn't work is DXR, the DirectX-only Ray Tracing - there's different implementations remember. With NVIDIA they have their own Vulkan extensions, while Khronos work on the cross-vendor solution which is in progress for Vulkan.

Just to be more clear for people reading.
Avehicle7887 Oct 11, 2020
Just to add a bit to what Liam said.

I think people still confuse the Ray Tracing Technology (Hardware) with the DXR API which is the software part that communicates with the hardware. When the AMD RDNA2 cards launch, they'll also be able to use DXR (DirectX Ray Tracing) and the Vulkan implementation when that is ready.

RTX is simply the name Nvidia gave to their cards to distinguish them from the Non-RT models. As far as I'm aware there are currently 2 titles that use Vulkan ray tracing which is Quake 2 RTX and Doom Eternal, as already pointed out though, Nvidia is using their own ray tracing Vulkan extension(s) for the Vulkan side (Extension Details Here).

My guess is, if AMD provides DXR support on Windows at the RDNA 2 release, DX12 Titles will be able to use RT feature out of the box.


Last edited by Avehicle7887 on 11 October 2020 at 9:06 pm UTC
jens Oct 12, 2020
  • Supporter
Nvidia’s ray tracing extension has been superseded by a Khronos raytracing extension, see https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_KHR_ray_tracing.html
So it’s no longer Nvidia only.
Comandante Ñoñardo Oct 13, 2020
If 450.80.02 was released on September 30, why my Ubuntu 20.04 downloaded it today, two weeks later?
oldrocker99 Oct 13, 2020
View PC info
  • Supporter Plus
Ubuntu does hold on to released packages for some time for thorough testing.
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.