Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sample subpasses throws lots of validation errors at startup #1197

Open
SaschaWillems opened this issue Oct 19, 2024 · 2 comments
Open

Sample subpasses throws lots of validation errors at startup #1197

SaschaWillems opened this issue Oct 19, 2024 · 2 comments

Comments

@SaschaWillems
Copy link
Collaborator

Running the subpasses sample throws dozens of validation errors for me at startup on Windows with an RTX 4070 using the latest SDK:

[error] 732146062 - VUID-vkCmdDraw-None-08114: Validation Error: [ VUID-vkCmdDraw-None-08114 ] Object 0: handle = 0xa952a5000000016f, type = VK_OBJECT_TYPE_DESCRIPTOR_SET; | MessageID = 0x2ba3a98e | vkCmdDraw():  Descriptor set VkDescriptorSet 0xa952a5000000016f[] Image layout specified by vkCmdBindDescriptorSets doesn't match actual image layout at time descriptor is used. See previous error callback for specific details. The Vulkan spec states: Descriptors in each bound descriptor set, specified via vkCmdBindDescriptorSets, must be valid as described by descriptor validity if they are statically used by the VkPipeline bound to the pipeline bind point used by this command and the bound VkPipeline was not created with VK_PIPELINE_CREATE_DESCRIPTOR_BUFFER_BIT_EXT (https://vulkan.lunarg.com/doc/view/1.3.290.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdDraw-None-08114)
[error] -564812795 - VUID-VkDescriptorImageInfo-imageLayout-00344: Validation Error: [ VUID-VkDescriptorImageInfo-imageLayout-00344 ] Object 0: handle = 0x240bf4e7e30, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0x59f7450000000038, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xde55a405 | vkCmdDraw():  Cannot use VkImage 0x59f7450000000038[] (layer=0 mip=0) with specific layout VK_IMAGE_LAYOUT_SHADER_READ_ONLY_OPTIMAL that doesn't match the previous known layout VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL. The Vulkan spec states: imageLayout must match the actual VkImageLayout of each subresource accessible from imageView at the time this descriptor is accessed as defined by the image layout matching rules (https://vulkan.lunarg.com/doc/view/1.3.290.0/windows/1.3-extensions/vkspec.html#VUID-VkDescriptorImageInfo-imageLayout-00344)

Changing options in the UI also retriggers those.

@SaschaWillems
Copy link
Collaborator Author

Probably related to #455 and #867

@marty-johnson59
Copy link
Contributor

Hi @tomadamatkinson, this one looks like it might be Framework related - possibly somewhere inside the scene graph? Any chance you can look into this? LMK, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants