Show Your Support: This site is primarily supported by advertisements. Ads are what have allowed this site to be maintained on a daily basis for the past 18+ years. We do our best to ensure only clean, relevant ads are shown, when any nasty ads are detected, we work to remove them ASAP. If you would like to view the site without ads while still supporting our work, please consider our ad-free Phoronix Premium.
Vulkan 1.0.69 Released With Fixes & New AMD Buffer Marker Extension
With Vulkan 1.0.68 having shipped in the middle of January, there are a fair amount of documentation improvements/fixes over the past month. As usual, addressing issues with the documentation reflects a majority of the changes for these point releases. Of the issues addressed in Vulkan 1.0.69, it's mostly a collection of over a dozen minor problems.
There is one new extension with Vulkan 1.0.69 and that is VK_AMD_buffer_marker. The VK_AMD_buffer_marker extension adds a new operation for executing pipelined writes of small marker values into a VkBuffer object. These buffer markers are to be used for development/debugging tools for tracking the status of pipelined commands. This should overall be another useful extension just not for AMD but all driver vendors.
The latest Vulkan documentation is available from the Khronos Registry.