Change Details

**Overview of new features in SDK 1.0.51** * Update loader and docs to Vulkan version 1.0.51. * Visual Studio 2017 templates are now included * Extensions introduced since the 1.0.51 SDK include: - VK_AMD_texture_gather_bias_lod (added the vulkan 1.0.50 specification) * Vulkan Layers have changed: - The remaining functionality in the VK_LAYER_LUNARG_swapchain layer has been migrated into the VK_LAYER_LUNARG_core_validation layer - The VK_LAYER_LUNARG_api_dump utility layer has been improved with the addition of an HTML back-end for a better api_dump user experience * VkTrace/VkReplay additions: - vktraceviewer included in both the Windows and Linux SDKs and is an alpha release. - vktrace trim feature is now available and has been improved. Trim can be used to specify a frame interval to capture - all other frames are removed from the trace file, resulting in a smaller trace file. - vktrace has been improved to increase portability of generated trace files across display driver versions. * Scores of bugfixes, validation coverage and accuracy improvements, and many feature additions [Changelog](https://vulkan.lunarg.com/doc/sdk/1.0.51.0/linux/release_notes-1.0.html) Depends on D489 Signed-off-by: Pierre-Yves <pyu@riseup.net>

- Internal Issues: * Fix tessellation domain to have an upper-left origin in the <<img-tessellation-topology-ul, tessellation toplogy image>> and related language. CTS and all implementations were already doing this, it was just a documentation bug that it was flipped to lower-left (internal issue 603). * Add a section to the style guide describing how VUID tags are changed and removed when the corresponding Valid Usage statements are modified (internal issue 829). * Add explicit Valid Usage statement to slink:VkPipelineDynamicStateCreateInfo to require that members of pname:pDynamicStates must be unique (internal issue 851). - New Extensions: * `VK_KHR_16bit_storage` * `VK_KHR_dedicated_allocation` * `VK_KHR_external_fence` * `VK_KHR_external_fence_capabilities` * `VK_KHR_external_fence_fd` * `VK_KHR_external_fence_win32` * `VK_KHR_get_memory_requirements2` * `VK_KHR_storage_buffer_storage_class` * `VK_KHR_variable_pointers` - Extensions Promoted From KHX To KHR Status: * `VK_KHR_external_memory` * `VK_KHR_external_memory_capabilities` * `VK_KHR_external_memory_fd` * `VK_KHR_external_memory_win32` * `VK_KHR_external_semaphore` * `VK_KHR_external_semaphore_capabilities` * `VK_KHR_external_semaphore_fd` * `VK_KHR_external_semaphore_win32` * `VK_KHR_win32_keyed_mutex` Depends on D489, D685. Signed-off-by: Pierre-Yves <pyu@riseup.net>

**Overview of new features in SDK 1.0.51** * Update loader and docs to Vulkan version 1.0.51.- Internal Issues: * Fix tessellation domain to have an upper-left origin in the <<img-tessellation-topology-ul, tessellation toplogy image>> and related language. CTS and all implementations were already doing this, it was just a documentation bug that it was flipped to lower-left (internal issue 603). * Add a section to the style guide describing how VUID tags are changed and removed when the corresponding Valid Usage statements are modified * Visual Studio 2017 templates are now included (internal issue 829). * Extensions introduced since the 1.0.51 SDK include: * Add explicit Valid Usage statement to slink:VkPipelineDynamicStateCreateInfo to require that members of pname:pDynamicStates must be unique (internal issue 851). - New Extensions: * `VK_KHR_16bit_storage` - VK_AMD_texture_gather_bias_lod (added the vulkan 1.0.50 specifi* `VK_KHR_dedicated_allocation)` * Vulkan Layers have changed: * `VK_KHR_external_fence` - The remaining functionality in the VK_LAYER_LUNARG_swapchain layer has been migrated into the VK_LAYER_LUNARG_core_validation layer* `VK_KHR_external_fence_capabilities` - The VK_LAYER_LUNARG_api_dump utility layer has been improved with the addition of an HTML back-end for a better api_dump user experience* `VK_KHR_external_fence_fd` * VkTrace/VkReplay additions: * `VK_KHR_external_fence_win32` - vktraceviewer included in both the Windows and Linux SDKs and is an alpha release.* `VK_KHR_get_memory_requirements2` - vktrace trim feature is now available and has been improved. Trim can be used to specify a frame interval to capture - all other frames are removed from the trace file, resulting in a smaller trace file.* `VK_KHR_storage_buffer_storage_class` - vktrace has been improved to increase portability of generated trace files across display driver versions.* `VK_KHR_variable_pointers` * Scores of bugfixes, validation coverage and accuracy improvements, and many feature additions [Changelog](https://vulkan.lunarg.com/doc/sdk/1.0.51.0/linux/release_notes-1.0.html) Depends on D489- Extensions Promoted From KHX To KHR Status: * `VK_KHR_external_memory` * `VK_KHR_external_memory_capabilities` * `VK_KHR_external_memory_fd` * `VK_KHR_external_memory_win32` * `VK_KHR_external_semaphore` * `VK_KHR_external_semaphore_capabilities` * `VK_KHR_external_semaphore_fd` * `VK_KHR_external_semaphore_win32` * `VK_KHR_win32_keyed_mutex` Depends on D489, D685. Signed-off-by: Pierre-Yves <pyu@riseup.net>