Support us on Patreon
PayPalToday along with upgrading Quake II RTX to support cross-vendor Ray Tracing, NVIDIA had another surprise with the release of the new 460.27.04 Beta driver with quite a number of changes. On top of that, there's also a big new release of the LunarG Vulkan SDK for Ray Tracing.
Firstly, the driver update. Version 460.27.04 is out now, tagged as a Beta release of their mainline drivers. This new driver adds support for these extensions:
- VK_KHR_acceleration_structure extension.
- VK_KHR_ray_tracing_pipeline extension.
- VK_KHR_ray_query extension.
- VK_KHR_pipeline_library extension.
- VK_KHR_deferred_host_operations extension.
- VK_NV_fragment_shading_rate_enums
- VK_KHR_fragment_shading_rate
- VK_KHR_shader_terminate_invocation
- VK_EXT_shader_image_atomic_int64
- VK_KHR_copy_commands2
That's not all. The driver release itself also brings with it bug fixes and numerous improvements for Linux users including support for RandR rotation and reflection while using an NVIDIA-driven display as a PRIME Display Offload sink and "Reverse PRIME Bypass" which is "an optimization that bypasses the bandwidth overhead of PRIME Render Offload and PRIME Display Offload in conditions where a render offload application is fullscreen, unredirected, and visible only on a given NVIDIA-driven PRIME Display Offload output".
With OpenGL and Vulkan the shader disk cache also saw some upgrades this time around too. The location was moved, and the default size has bumped up to 1024MB, although they mentioned that caches with paths containing "/.nv/ will continue to use the previous default of 128MB "unless the size is manually overridden".
See the full driver notes here.
As for the Vulkan Software Development Kit (SDK), The Khronos Group announced today that LunarG have put out a big upgrade to the SDK with full support for the new Vulkan Ray Tracing extensions, including Validation Layers and integration of upgraded GLSL, HLSL and SPIR-V shader tool chains. With this out, plus the new drivers, the pickup of Ray Tracing might start to increase.
"Shipping API specifications was just the first step in building the developer ecosystem for Vulkan Ray Tracing, we now have tools and samples to truly enable developers to tap into the power of cross-platform ray tracing acceleration," said Daniel Koch, senior graphics system software engineer at NVIDIA and Vulkan Ray Tracing TSG chair at Khronos. "One of the key requests from the developer community was the ability to easily bring DirectX 12 ray tracing (DXR) code to Vulkan. We have achieved that through delivering a carefully designed superset of DXR, and integrating Vulkan Ray Tracing support in the DXC open source HLSL compiler."
The press release also mentions that through "the design of Vulkan Ray Tracing, projects such as vkd3d-Proton will be able to efficiently support layered DXR over Vulkan".
Article taken from GamingOnLinux.com.
Quoting: GrabbyQuoting: 3zekielQuoting: DoctorJunglistQuoting: BeamboomVK_VALVE_mutable_descriptor_type still missing though :(
/*-That's what I'm waiting for as well, it's needed for Cyberpunk 2077.
I hope it doesn't take Nvidia too long to incorporate this extension into their drivers.
Quoting: ikirutoRTX 2060 and Ryzen 1700 works without problems on Proton-Experimental with the settings in the screenshots and hex fix.
https://ibb.co/bJ0Z315
https://ibb.co/M75Ndt4
https://ibb.co/p3mMvqw
gamemoderun %command% --launcher-skip
Use a hex editor on the Cyberpunk2077.exe.
Replace "75 30 33 C9 B8 01 00 00 00 0F A2 8B C8 C1 F9 08" with "EB 30 33 C9 B8 01 00 00 00 0F A2 8B C8 C1 F9 08".
Replace "55 48 81 ec a0 00 00 00 0f 29 70 e8" with "c3 48 81 ec a0 00 00 00 0f 29 70 e8".
It seems the fix should be in exe for Nvidia. (second hand info though)
Doesn't that hex edit only affects the core scaling of the game ? Vk3d3d devs were saying that the engine is relying on undefined behavior in DX12, which is the cause of the crashes. I doubt core scaling has anything to do with that.
Besides, the crash are very random, so just because he didn't experience them after applying the fix doesn't mean the issue is solved.
Quoting: ikirutoQuoting: GrabbyDoesn't that hex edit only affects the core scaling of the game ? Vk3d3d devs were saying that the engine is relying on undefined behavior in DX12, which is the cause of the crashes. I doubt core scaling has anything to do with that.Research is not a matter of faith, if there is something that needs verification, it should be verified, and not refer to your doubts. Crashes of the game are corrected not by the first line, but by the second.
Besides, the crash are very random, so just because he didn't experience them after applying the fix doesn't mean the issue is solved.
Signature of AVX bug is as follows:
Game crashes at and beyond these locations:
Take a seat for Corpo
Exit bar for Street Kid
After cutscene for arrival at city for Nomad
You can do this mod yourself trivially. Simply use a hex editor on the Cyberpunk2077.exe,
and replace "55 48 81 ec a0 00 00 00 0f 29 70 e8" with "c3 48 81 ec a0 00 00 00 0f 29 70 e8".
This simply turns the bad AVX call into a return.
DISCLAIMER: May be breaking things under the hood, but seems stable.
what he said I guess ? (once again only second hand, don't quote me, talk to the source :) )
Quoting: RoosterQuoting: wytrabbitQuoteWith OpenGL and Vulkan the shader disk cache also saw some upgrades this time around too. The location was moved, and the default size has bumped up to 1024MB, although they mentioned that caches with paths containing "/.nv/ will continue to use the previous default of 128MB "unless the size is manually overridden".
Yes, finally! Should reduce the daily shader processing after opening the Steam client.
Is this related to the annoying "Processing Vulkan Shaders" message I keep getting on every Steam Play title?
Yes I'm almost positive it is.
- https://www.reddit.com/r/linux_gaming/comments/jm2j4l/overwatch_recompiling_shaders_every_time/gass1pv/
QuoteThe increase in observed shader disk cache usage is intended, as additional shader information is being stored to improve application runtime performance.
A change increasing the default size of the shader disk cache will be made available in the next driver release series (after 455). Moving forward we will continue to optimize our shader disk cache usage for performance as well as size.
Last edited by wytrabbit on 16 December 2020 at 2:44 pm UTC
See more from me