KhronosGroup / Vulkan-ValidationLayers

Vulkan Validation Layers (VVL)
https://vulkan.lunarg.com/doc/sdk/latest/linux/khronos_validation_layer.html
Other
778 stars 408 forks source link

VVL complain image layout is undefined when enable VK_VALIDATION_FEATURE_ENABLE_GPU_ASSISTED_EXT #8951

Open vkensou opened 1 day ago

vkensou commented 1 day ago

Environment:

Describe the Issue

When enable VK_VALIDATION_FEATURE_ENABLE_GPU_ASSISTED_EXT, VVL complain image 0xd10d270000000018 current layout is VK_IMAGE_LAYOUT_UNDEFINED, but it already transition to VK_IMAGE_LAYOUT_SHADER_READ_ONLY_OPTIMAL when frame 0.
Strangely, it doesn't complain every frame, but only starts complaining from the frame 3.

Expected behavior

Don't complain UNASSIGNED-CoreValidation-DrawState-InvalidImageLayout

Additional context

Here is full API dump.: report.txt

code or terminal output ```sh UNASSIGNED-CoreValidation-DrawState-InvalidImageLayout(ERROR / SPEC): msgNum: 1303270965 - Validation Error: [ UNASSIGNED-CoreValidation-DrawState-InvalidImageLayout ] Object 0: handle = 0x25b1d1aeab0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd 10d270000000018, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0x4dae5635 | vkCmdDraw(): command buffer VkCommandBuffer 0x25b1d1aeab0[] expects VkImage 0xd10d270000000018[] (subresource: aspectMask VK_IMAGE_ASPECT_COLOR_BIT array layer 0, mip level 0) to be in lay out VK_IMAGE_LAYOUT_SHADER_READ_ONLY_OPTIMAL--instead, current layout is VK_IMAGE_LAYOUT_UNDEFINED. Objects: 2 [0] 0x25b1d1aeab0, type: 6, name: NULL [1] 0xd10d270000000018, type: 10, name: NULL ```
spencer-lunarg commented 1 day ago

most likely a duplicate of https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/8688 (and currently working on it!)