Vulkan SDK 1.3.268.0 Release Notes
Version 1.3.268.0 for Windows
October 24, 2023
This SDK supports Vulkan API revision 1.3.268.
Overview of new features in SDK 1.3.268.0
- vk_format_utils.h is now an official SDK deliverable
- vk_enum_string_helper.h is now a C compatible header file.
- Debug versions of the DXC and VOLK libraries have been included in the SDK (dxcompilerd.dll, dxcompilerd.lib, volkd.lib)
- To improve layer consistency, the naming of layer and layer settings of the extension layers has been refactored which may not be backward compatible with existing Vulkan developer environment setup when not using the Vulkan Configurator. Please, refer to the VK_LAYER_KHRONOS_shader_object layer documentations to update the developer environment in case of any issue.
- The Vulkan Configurator (vkconfig) has been updated to improve quality and stability. See the fixes included in this SDK here. See the Vulkan Configurator documentation for more information.
- The Vulkan headers now include the following new extensions. Note that extensions are optional and may not be implemented by the underlying driver/ICD. Applications can now query for the presence of these new features.
- VK_EXT_nested_command_buffer
- VK_NV_extended_sparse_address_space
- VK_ANDROID_external_format_resolve
- VK_NV_low_latency2
- VK_EXT_frame_boundary
- VK_MSFT_layered_driver (support not yet in Vulkan Loader)
- VK_NV_descriptor_pool_overallocation
- VK_QCOM_filter_cubic_clamp
- VK_QCOM_filter_cubic_weights
- VK_QCOM_image_processing2
- VK_QCOM_ycbcr_degamma
- Improved validation coverage. VUID validation coverage documentation (validation_error_database.csv and validation_error_database.html) has been updated to represent the validation layer VUID coverage status.
Drivers: It is recommended you update Vulkan-capable hardware drivers to the latest recommended version from the hardware vendor. A list of Known Issues appears at the end of this document with more information.
Vulkan Loader: The Windows SDK does not update the Vulkan Loader on your system. Instead you should be getting the Vulkan Loader from your graphics hardware provider driver package. There is an optional Vulkan Runtime package available at vulkan.lunarg.com should you wish to force updating your system with a more recent Vulkan Loader.
Platform Support Matrix
Feature | Windows | Linux tarball | Ubuntu Packages | macOS SDK |
---|---|---|---|---|
Tools | ||||
Vulkan Configurator | X | X | X | X |
Vulkaninfo | X | X | X | X |
VIA (Vulkan Installation Analyzer) | X | X | X | X |
Vulkan Profiles API Library | X | X | X | X |
VOLK (a meta-loader for Vulkan) | X | X | X | X |
AMD Memory Allocator | X | X | X | X |
Validation Layers | ||||
Validation | X | X | X | X |
Best Practices | X | X | X | X |
GPU Assisted Validation | X | X | X | |
Debug Printf | X | X | X | |
Synchronization Validation | X | X | X | X |
Utility Layers | ||||
Profiles Layer | X | X | X | X |
API Dump | X | X | X | X |
Monitor | X | X | X | |
Screenshot | X | X | X | |
GFXReconstruct | X | X | X | |
Extension Layers | ||||
Synchronization 2 | X | X | X | X |
Shader Object | X | |||
Shader Tools | ||||
glslangValidator | X | X | X | X |
SPIR-V Optimizer | X | X | X | X |
SPIR-V Disassembler, Assembler, Validator | X | X | X | X |
SPIR-V Remapper | X | X | X | X |
SPIR-V Control Flow Visualization | X | X | X | X |
SPIR-V Cross-Compilation and Reflection | X | X | X | X |
shaderc | X | X | X | X |
DXC (DirectX Shader Compiler) | X | X | X | X |
SPIRV-reflect | X | X | X | X |
SDK Components
This version of the SDK is based on the following specifications, source code repositories, and commits:
- Vulkan Specification
- SPIR-V Specification (Version 1.6, Revision 1)
- GLSL Specification (Version 4.6)
- GitHub Repo: KhronosGroup/glslang, Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: KhronosGroup/SPIRV-Cross Version Tag: vulkan-sdk-1.3.268.0
- Github Repo: SPIRV-Reflect Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: KhronosGroup/SPIRV-Tools, Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: KhronosGroup/Vulkan-Headers, Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: KhronosGroup/Vulkan-Loader, Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: KhronosGroup/Vulkan-Tools, Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: KhronosGroup/Vulkan-ValidationLayers, Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: KhronosGroup/Vulkan-Profiles, Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: KhronosGroup/Vulkan-ExtensionLayer, Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: KhronosGroup/Vulkan-Utility-Libraries, Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: LunarG/gfxreconstruct, Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: LunarG/VulkanTools, Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: volk, Version Tag: vulkan-sdk-1.3.268.0
- GitHub Repo: AMD Memory Allocator commit: 2f382df218d7e8516dee3b3caccb819a62b571a2
- GitHub Repo: microsoft/DirectXShaderCompiler commit: 93ad5b31316cfed379a8e83bb6cfbbc8bc886ff9
- GitHub Repo: google/shaderc commit: 066853941a3f097b6196f452dde42c0cbf7f98f4
- GitHub Repo: SaschaWillems/VulkanCapsViewer tag: 3.32
- GitHub Repo: sdl, Version Tag: release-2.28.4
- GitHub Repo: glm, Version Tag: 0.9.9.8
LunarG would like to thank all of the many contributors to all of the above repositories and the contributions they are making to the Vulkan Ecosystem.
Submitting Issues
If while using the tools and layers included in the SDK you find a defect in that tool or layer, the most expedient way to get a resolution is to submit to its corresponding repository. For example, if you believe you have found a defect in the Validation Layers, submit an issue at the repository for Validation Layers. The only exception to this is for the shader tool chain (glslang, SPIRV-Cross, SPIRV-Tools, shaderc). For these repositories you can submit issues against the SDK at vulkan.lunarg.com.
Known Issues
New Layer Manifest File version: The new version of the Layer Manifest File may cause an older Vulkan Loader to generate a warning. This warning is safe to ignore. It appears like the following with a corresponding SDK path and layer name:
WARNING: [Loader Message] Code 0 : loaderAddLayerProperties: [path\to\sdk]VkLayer_[layer_name].json invalid layer manifest file version 1.2.0. May cause errors.
Vulkan Configurator known issues are documented in the Vulkan Configurator Change Log
Possible Conflict between Vulkan Profiles Layer and Vulkan Hardware Capability Viewer: If the the Vulkan Profiles layer is active (perhaps via the Vulkan Configurator) and the Vulkan Hardware Capability Viewer is started, you may get the message "Feature modifying tool detected, upload disabled". This can occur on installation of a new SDK if autolaunch of Vulkan Configurator and and the capabilities viewer is selected, when the last selected configuration includes the profile layer.