For those interested, Khronos Group has today announced the release of the Vulkan [Official Site] API version 1.1 and NVIDIA already have a beta driver ready.
Beaverton, OR – March 7, 2018 – The Khronos™ Group, an open consortium of leading hardware and software companies creating advanced acceleration standards, announces the release of the Vulkan® 1.1 and SPIR-V™ 1.3 specifications. Version 1.1 expands Vulkan’s core functionality with developer-requested features, such as subgroup operations, while integrating a wide range of proven extensions from Vulkan 1.0. Khronos will also release full Vulkan 1.1 conformance tests into open source and AMD, Arm, Imagination, Intel Corporation, NVIDIA and Qualcomm have implemented conformant Vulkan 1.1 drivers. Find more information on the Vulkan 1.1 specification and associated tests and tools at Khronos’s Vulkan Resource Page.
Find the official Khronos Group announcement here. You can also see the specification documents here. There will also be plenty of activity at this year's GDC (Game Developers Conferenc) with the Khronos Developer Day Sessions. You can see the full GDC schedule here.
On top of that, they've also got a presentation you can flick through here (~7MB), where you can find slides to explain things a little more like these:
Also, for those interested in testing out any of the new stuff, NVIDIA has their 387.42.05 beta driver out for Linux which includes full Vulkan 1.1 support available here.
On top of that, AMD have also put out their "Radeon™ Software for Linux® Driver 17.50" which includes Vulkan 1.1 support, find that here.
Right now, it doesn't mean all that much for Linux gamers until games and applications start making use of any of the new stuff. We're just reporting on it to keep you up to date.
Post updated to include more info after publishing. We may update it again, be sure to check back!
Quoting: EhvisDoes anybody know details about that "HLSL support"? If that works like it suggests, this could be massive for multi platform engines like UE4 and Unity3D.
I think idea is that shader format between DX12 and Vulkan is the same, but issue is memory management. Vulkan adds way to manage memory similar to DX12, thus allowing porting code with no pain and all gain.
Quoting: gustavoyaraujoI don't know about you guys. But 90% of my Linux issues are related to updating nvidia drivers.
I wonder why. I got so many problems with e. g. printer and Wifi USB stick support, but Nvidia drivers just work like a charm (Debian here).
Quoting: Guesthttps://lists.freedesktop.org/archives/mesa-dev/2018-March/187902.html
(Intel driver, "ANV", patch submission for Vulkan 1.1 support).
AMD's "amdvlk" driver also has Vulkan 1.1 support. Not sure on radv status, but it won't be far behind I'm sure.
--edit: https://airlied.blogspot.co.uk/2018/03/radv-vulkan-11-coformant-on-launch-day.html
... and already committed into mesa git master :)
https://cgit.freedesktop.org/mesa/mesa/commit/?id=034cce96b4337bb497394b41b1530bedb8923439
Last edited by edmondo on 7 March 2018 at 9:04 pm UTC
Quoting: GuestQuoting: FifteenthPenYay, just what I always wanted, built-in DRM support! :/
Might not be what you want, but it is what the rest of the software industry wants.
HLSL support would be excellent.. though I imagine this is more a HLSL -> SPIR-V compiler, which is still excellent. D3D Shader Binary -> SPIR-V bytecode should be easier to do than the current binary->GLSL path.
Rest of the industry wants to hold back progression with cancer. I get it. ;)
See more from me