Spencer Fricke
Spencer Fricke
There are some SPIR-V edge cases that need to be handled, tests were added (but disabled) in https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/7463) update: likely related same issue - https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/4577
as shown in https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/6790/files#r1368138913 it seems that currently by not generating the `Unwrap` in the manual chassis dispatch, we open the possibility of missing a new extensions' pNext structure that...
**Describe the situation in which you encountered the missing validation** This was added as `VUID-vkCmdDraw-None-02686` (now `VUID-vkCmdDraw-None-08600`), then an [issue of it being wrong](https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/2243) was created and it was then...
The `NegativePipelineLayout.DescriptorTypeMismatchNonCombinedImageSampler` in https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/5900 shows we report the following two errors on the same shader > Validation Error: [ VUID-VkGraphicsPipelineCreateInfo-layout-07989 ] ... pCreateInfos[0] has a type mismatch for descriptor slot...
these were added in 1.3.280 headers/spec (https://gitlab.khronos.org/vulkan/vulkan/-/merge_requests/6512) - [ ] VUID-vkCmdDraw-None-09600 - [ ] VUID-vkCmdBeginRendering-pRenderingInfo-09588 - [ ] VUID-vkCmdBeginRendering-pRenderingInfo-09589 - [ ] VUID-vkCmdBeginRendering-pRenderingInfo-09590 - [ ] VUID-vkCmdBeginRendering-pRenderingInfo-09591 - [ ]...
From https://gitlab.khronos.org/vulkan/vulkan/-/merge_requests/6269 Call `vkGetDescriptorSetLayoutSupport` for apps this catches Mutable Descriptor tests failing on MESA because they don't support `VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER` (but NVIDIA does)
There are surely more missing, mostly dealing with SPIR-V and AHB, but here are some I found that are focused on the Renderpass/Framebuffer side - [ ] VUID-VkFramebufferCreateInfo-flags-03196 - [...
https://github.com/KhronosGroup/Vulkan-ValidationLayers/commit/6db385a7ea2c85d384df3e9ccff06729f71b22e9#diff-eefbaf049195ad7b10928b277b434137d20dbbd7654d1d6bc278f689b8a5a612R318 changed how the tests handled versions, previously one could write a test case that requires descriptor indexing to work with either core or extension as follows: ``` SetTargetApiVersion(VK_API_VERSION_1_3); AddOptionalExtensions(VK_EXT_DESCRIPTOR_INDEXING_EXTENSION_NAME);...
from https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/6883 we only detect if the descriptor is an array or not. This leaves gaps in validation when we know the size of the array and have constants access...
VUs such as `VUID-vkSetEvent-event-09543` (https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/7379) only track if it was used in a command buffer, not which command buffer It would be nice to have the command buffer handles tracked...