Shortly after giving us a brand new stable mainline driver, the NVIDIA driver team have released a new developer-focused Vulkan Beta Driver.
A big change here is that the driver has been rebased onto the newer r450 series, bringing with it numerous other bug fixes and improvements there in past driver released. As for what's new to the 450.56.01 Vulkan Beta:
Features:
- Added support for the VkPhysicalDeviceRayTracingFeaturesKHR.rayTracingIndirectTraceRays ray tracing feature
- VK_NV_device_diagnostics_config
While Ray Tracing has been supported on NVIDIA + Linux for a long time now, their work continues on the newer vendor-neutral extensions from the Khronos Group which when out of provisional status will provide Ray Tracing for AMD, Intel and NVIDIA all together.
Fixes:
- Make the pSizes parameters of vkCmdBindVertexBuffers2EXT be relative to the pBuffers+pOffsets
- Fixed potential crash in the first vkQueuePresentKHR() call after creating a new VkSwapchainKHR with a non-NULL oldSwapchain
- Fixed potential crash in vkCmdBeginRenderPass() when using VK_EXT_sample_locations
Reminder: you know it's a special Beta driver thanks to the additional two numbers on the end of the version string, with the newest stable version of the NVIDIA driver for Linux at 450.57 which released on July 9. 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.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
8 comments
This driver give with more updated vulkan version according json file:
{
"file_format_version" : "1.0.0",
"ICD": {
"library_path": "libGLX_nvidia.so.0",
"api_version" : "1.2.145"
}
}
Almost forget this driver works with cuda 11 - nvenc sdk 10 and lastest ffmpeg git
Last edited by mrdeathjr on 10 July 2020 at 1:52 pm UTC
{
"file_format_version" : "1.0.0",
"ICD": {
"library_path": "libGLX_nvidia.so.0",
"api_version" : "1.2.145"
}
}
Almost forget this driver works with cuda 11 - nvenc sdk 10 and lastest ffmpeg git
Last edited by mrdeathjr on 10 July 2020 at 1:52 pm UTC
1 Likes, Who?
... and yet another bloody weird case of Nvidia versioning.
Just recently they released a new STABLE driver version 450.57. Subversion 57 of the 450 driver.
... And now they continue with a new beta, version 450.56.01?! So like, this is a new driver that's a beta of the version prior to the stable 450.57??
WTF?
Just recently they released a new STABLE driver version 450.57. Subversion 57 of the 450 driver.
... And now they continue with a new beta, version 450.56.01?! So like, this is a new driver that's a beta of the version prior to the stable 450.57??
WTF?
0 Likes
Quoting: Beamboom... and yet another bloody weird case of Nvidia versioning.
Just recently they released a new STABLE driver version 450.57. Subversion 57 of the 450 driver.
... And now they continue with a new beta, version 450.56.01?! So like, this is a new driver that's a beta of the version prior to the stable 450.57??
WTF?
for vulkan this driver is better than stable
doutsujin from discord:
Quotecan confirm that the vertex buffer stuff is fixed
Last edited by mrdeathjr on 10 July 2020 at 7:54 pm UTC
0 Likes
Quoting: Beamboom... and yet another bloody weird case of Nvidia versioning.
Just recently they released a new STABLE driver version 450.57. Subversion 57 of the 450 driver.
... And now they continue with a new beta, version 450.56.01?! So like, this is a new driver that's a beta of the version prior to the stable 450.57??
WTF?
Do you have any experiences with git and branches? Just consider "stable" and "vulkan-beta" to be long lived branches. Sometimes the commits from the "vulkan-beta" branch will be merged into stable (I guess at the start of a new major stable branch). At some point the "vulkan-beta" branch is rebased against the "stable" branch, thus all changes from the "vulkan-beta" will be applied on top of "vulkan-beta".
See eg. https://www.atlassian.com/git/tutorials/merging-vs-rebasing
1 Likes, Who?
Quoting: jensDo you have any experiences with git and branches? Just consider "stable" and "vulkan-beta" to be long lived branches. Sometimes the commits from the "vulkan-beta" branch will be merged into stable (I guess at the start of a new major stable branch). At some point the "vulkan-beta" branch is rebased against the "stable" branch, thus all changes from the "vulkan-beta" will be applied on top of "vulkan-beta".
See eg. https://www.atlassian.com/git/tutorials/merging-vs-rebasing
So what you're saying is that the stable branch and the beta branch are two different branches who just so happen to have a version number very close to each other? So this beta branch is not branched off a 450.56 main code base (of whom 450.57 stable is a later version of), but is a version totally on it's own?
0 Likes
Quoting: BeamboomQuoting: jensDo you have any experiences with git and branches? Just consider "stable" and "vulkan-beta" to be long lived branches. Sometimes the commits from the "vulkan-beta" branch will be merged into stable (I guess at the start of a new major stable branch). At some point the "vulkan-beta" branch is rebased against the "stable" branch, thus all changes from the "vulkan-beta" will be applied on top of "vulkan-beta".
See eg. https://www.atlassian.com/git/tutorials/merging-vs-rebasing
So what you're saying is that the stable branch and the beta branch are two different branches who just so happen to have a version number very close to each other? So this beta branch is not branched off a 450.56 main code base (of whom 450.57 stable is a later version of), but is a version totally on it's own?
From my understanding the Vulkan Dev branch is indeed not branched of 450.56, but rebased against 450.56. Thus 450.56.1 contains all commits from 450.56 plus all Vulkan Development commits that didn't get merged into 450, on top of it.
Thus yeah, you could say that both branches are independent, but will be synchronized once in a while with merges (vulkan-dev into stable) and rebases (stable into vulkan-dev).
The change logs are unfortunately aren't that exhaustive but e.g. stable 450.57 does not contains all commits from vulkan-dev 440.66.15. I think (but not sure) that vulkan-dev at 440.66.12 was merged into 450. Since the vulkan dev branch was rebased against 450.56, it does not contains the commits between 450.56 and 450.57 from the stable branch.
I hope this still makes sense ;)
Last edited by jens on 10 July 2020 at 11:30 pm UTC
0 Likes
Quoting: mrdeathjrThis driver give with more updated vulkan version according json file:
{
"file_format_version" : "1.0.0",
"ICD": {
"library_path": "libGLX_nvidia.so.0",
"api_version" : "1.2.145"
}
}
Almost forget this driver works with cuda 11 - nvenc sdk 10 and lastest ffmpeg git
Does it have New Nvenc on Linux ?
0 Likes
Quoting: massatt212Does it have New Nvenc on Linux ?
in my case use this:
Video Codec SDK 10
https://developer.nvidia.com/nvidia-video-codec-sdk/download
What's new in Video Codec SDK 10
New NVENC presets (H.264 - HEVC) for improved flexibility and granularity
Finer control of rate control modes
Use-case Setting (also referred to as Tuning information)
NVDEC Support for GA100
Last edited by mrdeathjr on 13 July 2020 at 2:24 am UTC
0 Likes
Patreon
PayPal
See more from me