KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
improve UNASSIGNED-CoreValidation-DrawState-InvalidImageLayout error
- Dominant language
- C++
- Stars
- 1k
- Forks
- 504
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 224
Description
Sometimes I get an error like:
```
UNASSIGNED-CoreValidation-DrawState-InvalidImageLayout(ERROR / SPEC): msgNum: 1303270965 - Validation Error: [ UNASSIGNED-CoreValidation-DrawState-InvalidImageLayout ] Object 0: handle = 0x589f420, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x4dae5635 | vkQueueSubmit(): pSubmits[1].pCommandBuffers[1] command buffer VkCommandBuffer 0x589f420[] expects VkImage 0xecc83d0000000274[] (subresource: aspectMask 0x1 array layer 0, mip level 1) to be in layout VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL--instead, current layout is VK_IMAGE_LAYOUT_SHADER_READ_ONLY_OPTIMAL.
```
This is extremely vague and unhelpful, and it's annoying to figure out exactly where something went wrong. VVL should be able to print more info, specifically which command is "expecting" a given layout.
update - the VU is not ` VUID-vkCmdDraw-None-09600`
Contributor guide
Assessment
This issue has not been assessed yet.