No swapchain image has been acquired

Hello! Thanks for providing this sample, it is the best looking I found so far!
I am trying to run it on Windows 10, MSVC 2022 with a HP Reverb G2 headset. I installed a fresh Vulkan SDK 1.3.283.0.
Now as far as I know my headset doesn't support OpenXR with Vulkan, but with the help of this tool: https://github.com/mbucchia/OpenXR-Vk-D3D12, I managed to run Godot XR samples using the Vulkan renderer (called Forward+). So I assumed this sample should also work with my setup (this assumption can be easily wrong). I made sure to disable my OpenXR Toolkit.
I am getting the following validation errors in Debug, not sure if they are important:
[Vulkan] Validation Error: [ VUID-VkImageViewCreateInfo-image-04441 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xb75da543 | vkCreateImageView(): pCreateInfo->image (VkImage 0xe88693000000000c[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_SAMPLED_BIT|VK_IMAGE_USAGE_STORAGE_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT|VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT|VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT|VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT|VK_IMAGE_USAGE_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR|VK_IMAGE_USAGE_FRAGMENT_DENSITY_MAP_BIT_EXT|VK_IMAGE_USAGE_VIDEO_DECODE_DST_BIT_KHR|VK_IMAGE_USAGE_VIDEO_DECODE_DPB_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_SRC_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_DPB_BIT_KHR|VK_IMAGE_USAGE_SAMPLE_WEIGHT_BIT_QCOM|VK_IMAGE_USAGE_SAMPLE_BLOCK_MATCH_BIT_QCOM. The Vulkan spec states: image must have been created with a usage value containing at least one of the usages defined in the valid image usage list for image views (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageViewCreateInfo-image-04441)
[Vulkan] Validation Error: [ VUID-VkImageViewCreateInfo-image-04441 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xb75da543 | vkCreateImageView(): pCreateInfo->image (VkImage 0x967dd1000000000e[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_SAMPLED_BIT|VK_IMAGE_USAGE_STORAGE_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT|VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT|VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT|VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT|VK_IMAGE_USAGE_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR|VK_IMAGE_USAGE_FRAGMENT_DENSITY_MAP_BIT_EXT|VK_IMAGE_USAGE_VIDEO_DECODE_DST_BIT_KHR|VK_IMAGE_USAGE_VIDEO_DECODE_DPB_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_SRC_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_DPB_BIT_KHR|VK_IMAGE_USAGE_SAMPLE_WEIGHT_BIT_QCOM|VK_IMAGE_USAGE_SAMPLE_BLOCK_MATCH_BIT_QCOM. The Vulkan spec states: image must have been created with a usage value containing at least one of the usages defined in the valid image usage list for image views (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageViewCreateInfo-image-04441)
[Vulkan] Validation Error: [ VUID-VkImageViewCreateInfo-image-04441 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xb75da543 | vkCreateImageView(): pCreateInfo->image (VkImage 0xd5b26f0000000010[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_SAMPLED_BIT|VK_IMAGE_USAGE_STORAGE_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT|VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT|VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT|VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT|VK_IMAGE_USAGE_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR|VK_IMAGE_USAGE_FRAGMENT_DENSITY_MAP_BIT_EXT|VK_IMAGE_USAGE_VIDEO_DECODE_DST_BIT_KHR|VK_IMAGE_USAGE_VIDEO_DECODE_DPB_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_SRC_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_DPB_BIT_KHR|VK_IMAGE_USAGE_SAMPLE_WEIGHT_BIT_QCOM|VK_IMAGE_USAGE_SAMPLE_BLOCK_MATCH_BIT_QCOM. The Vulkan spec states: image must have been created with a usage value containing at least one of the usages defined in the valid image usage list for image views (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageViewCreateInfo-image-04441)
[Vulkan] Validation Error: [ VUID-VkGraphicsPipelineCreateInfo-None-09497 ] | MessageID = 0x5750c307 | vkCreateGraphicsPipelines(): pCreateInfos[0].flags (0x400) has VkPipelineCreateFlagBits values that requires the extensions VK_EXT_graphics_pipeline_library. The Vulkan spec states: If the pNext chain does not include a VkPipelineCreateFlags2CreateInfoKHR structure, flags must be a valid combination of VkPipelineCreateFlagBits values (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkGraphicsPipelineCreateInfo-None-09497)
[Vulkan] Validation Error: [ VUID-VkGraphicsPipelineCreateInfo-None-09497 ] | MessageID = 0x5750c307 | vkCreateGraphicsPipelines(): pCreateInfos[0].flags (0x400) has VkPipelineCreateFlagBits values that requires the extensions VK_EXT_graphics_pipeline_library. The Vulkan spec states: If the pNext chain does not include a VkPipelineCreateFlags2CreateInfoKHR structure, flags must be a valid combination of VkPipelineCreateFlagBits values (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkGraphicsPipelineCreateInfo-None-09497)

I am confused about the first ones regarding empty usage, because I confirmed ImageBuffer.cpp always assigning a non-zero usage.
The VR app does start up in my headset and keeps running, but I am only getting a black scene. Meanwhile this error is continuously logged:
Exception thrown at 0x00007FFD8167BA99 in openxr-vulkan-example.exe: Microsoft C++ exception: msxr::XrResultException at memory location 0x000000F8974FD890.
ERROR (OpenXR) : [xrReleaseSwapchainImage] No swapchain image has been acquired.

Please let me know if you have any suggestion.

Strangely I am not always getting the same validation errors. Sometimes I have this one as well:
[Vulkan] Validation Error: [ VUID-VkSemaphoreTypeCreateInfo-timelineSemaphore-03252 ] | MessageID = 0x396b5439 | vkCreateSemaphore(): pCreateInfo->semaphoreType is VK_SEMAPHORE_TYPE_TIMELINE, but timelineSemaphore feature was not enabled. The Vulkan spec states: If the timelineSemaphore feature is not enabled, semaphoreType must not equal VK_SEMAPHORE_TYPE_TIMELINE
But this one I managed to fix, and it didn't help with the No swapchain image has been acquired error.

I have similar issue, running Meta XR Simulator v64 i get white screen and "no swapchain image is waited" error:

Hi @katz1,
The VkGraphicsPipelineCreateInfo warnings make sense, they're an error on my part. If you remove line 124 in Pipeline.cpp, this is resolved.
For the VkImageUsageFlags, I think that these are warnings about resources that are not created by the openxr-vulkan-example code, but rather by the OpenXR runtime. It's unfortunately very common that these runtimes are not written very cleanly and generate warnings like these. Normally these can be ignored, but it makes troubleshooting that much harder.
What puzzles me however is that I would have also thought the same to be the cause of the VkCreateSemaphore issue. I can't see where the openxr-vulkan-example code would use timeline semaphore types (that work through the next ptr of the VkSemaphoreCreateInfo struct, which is always initialized to null in the code.
How did you fix this issue?
@all500234765 Once we have the original issue figured out, I can take a look at the Meta XR Sim. It may just not (yet) be compatible. Do you happen to have a Quest headset fx. to try this without the simulator? That way we could find out if it's the simulator causing the issue.

Thanks for responding!
Yes, removing line 124 in Pipeline.cpp did fix the VkGraphicsPipelineCreateInfo issues.
I didn't realize you are not using timeline semaphores, I guess this also comes from the OpenXR runtime then? Adding these lines to Context.cpp line 739 does seem to fix the error for me though:
VkPhysicalDeviceVulkan12Features features{ VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_VULKAN_1_2_FEATURES };
features.timelineSemaphore = VK_TRUE;
physicalDeviceMultiviewFeatures.pNext = &features;

I have these validation issues now, but I imagine these are not related to the sample:
[Vulkan] Validation Error: [ VUID-VkImageCreateInfo-usage-requiredbitmask ] | MessageID = 0x34d7a349 | vkCreateImage(): pCreateInfo->usage is zero. The Vulkan spec states: usage must not be 0 (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageCreateInfo-usage-requiredbitmask)
[Vulkan] Validation Error: [ VUID-VkImageCreateInfo-usage-requiredbitmask ] | MessageID = 0x34d7a349 | vkCreateImage(): pCreateInfo->usage is zero. The Vulkan spec states: usage must not be 0 (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageCreateInfo-usage-requiredbitmask)
[Vulkan] Validation Error: [ VUID-VkImageCreateInfo-usage-requiredbitmask ] | MessageID = 0x34d7a349 | vkCreateImage(): pCreateInfo->usage is zero. The Vulkan spec states: usage must not be 0 (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageCreateInfo-usage-requiredbitmask)
[Vulkan] Validation Error: [ VUID-VkImageViewCreateInfo-image-04441 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xb75da543 | vkCreateImageView(): pCreateInfo->image (VkImage 0xe88693000000000c[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_SAMPLED_BIT|VK_IMAGE_USAGE_STORAGE_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT|VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT|VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT|VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT|VK_IMAGE_USAGE_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR|VK_IMAGE_USAGE_FRAGMENT_DENSITY_MAP_BIT_EXT|VK_IMAGE_USAGE_VIDEO_DECODE_DST_BIT_KHR|VK_IMAGE_USAGE_VIDEO_DECODE_DPB_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_SRC_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_DPB_BIT_KHR|VK_IMAGE_USAGE_SAMPLE_WEIGHT_BIT_QCOM|VK_IMAGE_USAGE_SAMPLE_BLOCK_MATCH_BIT_QCOM. The Vulkan spec states: image must have been created with a usage value containing at least one of the usages defined in the valid image usage list for image views (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageViewCreateInfo-image-04441)
[Vulkan] Validation Error: [ VUID-VkImageViewCreateInfo-image-04441 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xb75da543 | vkCreateImageView(): pCreateInfo->image (VkImage 0x967dd1000000000e[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_SAMPLED_BIT|VK_IMAGE_USAGE_STORAGE_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT|VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT|VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT|VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT|VK_IMAGE_USAGE_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR|VK_IMAGE_USAGE_FRAGMENT_DENSITY_MAP_BIT_EXT|VK_IMAGE_USAGE_VIDEO_DECODE_DST_BIT_KHR|VK_IMAGE_USAGE_VIDEO_DECODE_DPB_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_SRC_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_DPB_BIT_KHR|VK_IMAGE_USAGE_SAMPLE_WEIGHT_BIT_QCOM|VK_IMAGE_USAGE_SAMPLE_BLOCK_MATCH_BIT_QCOM. The Vulkan spec states: image must have been created with a usage value containing at least one of the usages defined in the valid image usage list for image views (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageViewCreateInfo-image-04441)
[Vulkan] Validation Error: [ VUID-VkImageViewCreateInfo-image-04441 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xb75da543 | vkCreateImageView(): pCreateInfo->image (VkImage 0xd5b26f0000000010[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_SAMPLED_BIT|VK_IMAGE_USAGE_STORAGE_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT|VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT|VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT|VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT|VK_IMAGE_USAGE_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR|VK_IMAGE_USAGE_FRAGMENT_DENSITY_MAP_BIT_EXT|VK_IMAGE_USAGE_VIDEO_DECODE_DST_BIT_KHR|VK_IMAGE_USAGE_VIDEO_DECODE_DPB_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_SRC_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_DPB_BIT_KHR|VK_IMAGE_USAGE_SAMPLE_WEIGHT_BIT_QCOM|VK_IMAGE_USAGE_SAMPLE_BLOCK_MATCH_BIT_QCOM. The Vulkan spec states: image must have been created with a usage value containing at least one of the usages defined in the valid image usage list for image views (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageViewCreateInfo-image-04441)

I still have the swapchain image issue, here are a few parts from the full log that might be interesting:
2024-06-07 20:43:52 +0200: XR_APILAYER_MBUCCHIA_vulkan_d3d12_interop layer (v1.1.1) is active
2024-06-07 20:43:52 +0200: Using layer: XR_APILAYER_MBUCCHIA_vulkan_d3d12_interop
...
2024-06-07 20:43:52 +0200: Available extension: XR_KHR_win32_convert_performance_counter_time
2024-06-07 20:43:52 +0200: Available extension: XR_KHR_D3D11_enable
2024-06-07 20:43:52 +0200: Available extension: XR_KHR_D3D12_enable
2024-06-07 20:43:52 +0200: Available extension: XR_KHR_composition_layer_depth
2024-06-07 20:43:52 +0200: Available extension: XR_KHR_composition_layer_color_scale_bias
2024-06-07 20:43:52 +0200: Available extension: XR_MSFT_unbounded_reference_space
2024-06-07 20:43:52 +0200: Available extension: XR_MSFT_spatial_anchor
2024-06-07 20:43:52 +0200: Available extension: XR_MSFT_perception_anchor_interop
2024-06-07 20:43:52 +0200: Available extension: XR_EXT_win32_appcontainer_compatible
2024-06-07 20:43:52 +0200: Available extension: XR_EXT_conformance_automation
2024-06-07 20:43:52 +0200: Available extension: XR_MSFT_composition_layer_reprojection
2024-06-07 20:43:52 +0200: Available extension: XR_MSFT_spatial_graph_bridge
2024-06-07 20:43:52 +0200: Available extension: XR_MSFT_spatial_anchor_persistence
2024-06-07 20:43:52 +0200: Available extension: XR_EXT_palm_pose
2024-06-07 20:43:52 +0200: Available extension: XR_EXT_active_action_set_priority
2024-06-07 20:43:52 +0200: Available extension: XR_MSFT_scene_understanding
2024-06-07 20:43:52 +0200: Available extension: XR_MSFT_scene_understanding_serialization
2024-06-07 20:43:52 +0200: Available extension: XR_MSFT_scene_marker
2024-06-07 20:43:52 +0200: Available extension: XR_FB_display_refresh_rate
2024-06-07 20:43:52 +0200: Available extension: XR_EXT_eye_gaze_interaction
2024-06-07 20:43:52 +0200: Available extension: XR_EXT_hand_interaction
2024-06-07 20:43:52 +0200: Available extension: XR_MSFT_hand_interaction
2024-06-07 20:43:52 +0200: Available extension: XR_EXT_hand_tracking
2024-06-07 20:43:52 +0200: Available extension: XR_EXT_hand_joints_motion_range
2024-06-07 20:43:52 +0200: Available extension: XR_MSFT_hand_tracking_mesh
2024-06-07 20:43:52 +0200: Available extension: XR_MSFT_controller_model
2024-06-07 20:43:52 +0200: Available extension: XR_KHR_visibility_mask
2024-06-07 20:43:52 +0200: Available extension: XR_EXT_samsung_odyssey_controller
2024-06-07 20:43:52 +0200: Available extension: XR_EXT_hp_mixed_reality_controller
2024-06-07 20:43:52 +0200: Requested extension: XR_KHR_vulkan_enable
2024-06-07 20:43:52 +0200: Application: OpenXR Vulkan Example
2024-06-07 20:43:52 +0200: Using OpenXR runtime: Windows Mixed Reality Runtime 113.2405.31001
2024-06-07 20:43:52 +0200: Using OpenXR system: Windows Mixed Reality
...
2024-06-07 20:43:52 +0200: Using Vulkan on adapter: NVIDIA GeForce RTX 2070 SUPER
[OBS] graphics-hook.dll loaded against process: openxr-vulkan-example.exe
[OBS] (half life scientist) everything..  seems to be in order
2024-06-07 20:43:52 +0200: Using Direct3D 12 on adapter: NVIDIA GeForce RTX 2070 SUPER
2024-06-07 20:43:52 +0200: Using Vulkan interop
...
2024-06-07 20:43:52 +0200: Creating swapchain with dimensions=2472x2416, arraySize=2, mipCount=1, sampleCount=1, format=43, usage=0x0
2024-06-07 20:43:52 +0200: Translated format: 29
2024-06-07 20:43:52 +0200: Swapchain image descriptor:
2024-06-07 20:43:52 +0200:   w=2472 h=2416 arraySize=2 format=27
2024-06-07 20:43:52 +0200:   mipCount=1 sampleCount=1
2024-06-07 20:43:52 +0200:   flags=0x21
2024-06-07 20:43:52 +0200:   heapFlags=0x85
ERROR (OpenXR) : [xrReleaseSwapchainImage] No swapchain image has been acquired.
Exception thrown at 0x00007FFEE03ABA99 in openxr-vulkan-example.exe: Microsoft C++ exception: msxr::XrResultException at memory location 0x000000C44A6FDA20.
2024-06-07 20:43:56 +0200: xrReleaseSwapchainImage failed with XR_ERROR_CALL_ORDER_INVALID
ERROR (OpenXR) : [xrReleaseSwapchainImage] No swapchain image has been acquired.
Exception thrown at 0x00007FFEE03ABA99 in openxr-vulkan-example.exe: Microsoft C++ exception: msxr::XrResultException at memory location 0x000000C44A6FDA20.
2024-06-07 20:43:56 +0200: xrReleaseSwapchainImage failed with XR_ERROR_CALL_ORDER_INVALID

Looks like the d3d12_interop tool I mentioned is loaded. I am a bit surprised by that OBS hook, I may try to get rid of that.

Thanks for the detailed info @katz1 , this is really helpful.
My hypothesis is that all validation errors are from the runtime. But the issue you're seeing is because the sample does not call xrWaitSwapchainImage() and/or xrAcquireSwapchainImage() (in Headset::beginFrame() in Headset.cpp), but it DOES call xrReleaseSwapchainImage() (in Headset::endFrame() in Headset.cpp).
Looking at the code, it looks like the only way this can occur is if the XrFrameState struct given by xrWaitFrame() (in Headset::beginFrame() in Headset.cpp) tells the sample that it should not render through the shouldRender flag. Line 446 in Headset::beginFrame() in Headset.cpp returns from the function before the calls to xrWaitSwapchainImage() and xrAcquireSwapchainImage() are made and returns a Headset::BeginFrameResult of SkipRender from the function in the sample code.
If you then look at the main loop in Main.cpp, you can see that, beginning in line 180, in case of a SkipRender result, the sample still calls Headset::endFrame() which will then proceed to call the xrReleaseSwapchainImage(), causing the issue.
Long story short, please try commenting out line 446 in Headset.cpp so that it looks like this:
 {
   // Let the host know that we don't want to render this frame
   // We do still need to end the frame however
   //return BeginFrameResult::SkipRender;      // Line 446 with change!
 }```

This way the sample will ignore the `shouldRender` flag and should render properly.

Please do let me know if this patch fixes your issue so I can make a proper commit to the sample! :)

Commenting out return BeginFrameResult::SkipRender; as you suggested fixed the swapchain error. The sample is fully functional now on my setup, thanks for your help!
I have lots of validation errors flooding the output. They may not be related to the sample, but I will post some of them just in case:
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x28d1c641090, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x28d1c641090[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x28d1c641090, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x28d1c641090[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0xd175b40000000013, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0xdcc8fd0000000012, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0xd175b40000000013[] pAttachments[2] (VkImageView 0xdcc8fd0000000012[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01779 ] Object 0: handle = 0x2cfba2000000001c, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x5717e75b | vkAcquireNextImageKHR():  Semaphore must not have any pending operations. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-vkCmdBlitImage-srcImage-00219 ] Object 0: handle = 0x28d1c641090, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xc3f06e26 | vkCmdBlitImage(): srcImage (VkImage 0xe88693000000000c[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_TRANSFER_SRC_BIT. The Vulkan spec states: srcImage must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage flag (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBlitImage-srcImage-00219)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x28d1c641090[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0xb991fa0000000024, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0xb991fa0000000024[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x28d1c07af70, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x28d1c07af70[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x28d1c07af70, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x28d1c07af70[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0xdd3a8a0000000015, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0x9fde6b0000000014, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0xdd3a8a0000000015[] pAttachments[2] (VkImageView 0x9fde6b0000000014[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01779 ] Object 0: handle = 0x301e6c0000000022, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x5717e75b | vkAcquireNextImageKHR():  Semaphore must not have any pending operations. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0x967dd1000000000e[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0x967dd1000000000e[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-vkCmdBlitImage-srcImage-00219 ] Object 0: handle = 0x28d1c07af70, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xc3f06e26 | vkCmdBlitImage(): srcImage (VkImage 0x967dd1000000000e[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_TRANSFER_SRC_BIT. The Vulkan spec states: srcImage must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage flag (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBlitImage-srcImage-00219)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0x967dd1000000000e[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0x967dd1000000000e[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x28d1c07af70[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0xcfcda0000000001e, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0xcfcda0000000001e[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x28d1c641090, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x28d1c641090[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x28d1c641090, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x28d1c641090[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0x84c0580000000017, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0xd897d90000000016, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0x84c0580000000017[] pAttachments[2] (VkImageView 0xd897d90000000016[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01779 ] Object 0: handle = 0x2cfba2000000001c, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x5717e75b | vkAcquireNextImageKHR():  Semaphore must not have any pending operations. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0xd5b26f0000000010[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0xd5b26f0000000010[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-vkCmdBlitImage-srcImage-00219 ] Object 0: handle = 0x28d1c641090, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xc3f06e26 | vkCmdBlitImage(): srcImage (VkImage 0xd5b26f0000000010[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_TRANSFER_SRC_BIT. The Vulkan spec states: srcImage must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage flag (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBlitImage-srcImage-00219)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0xd5b26f0000000010[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0xd5b26f0000000010[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x28d1c641090[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0xb991fa0000000024, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0xb991fa0000000024[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x28d1c07af70, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x28d1c07af70[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x28d1c07af70, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x28d1c07af70[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0xd175b40000000013, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0xdcc8fd0000000012, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0xd175b40000000013[] pAttachments[2] (VkImageView 0xdcc8fd0000000012[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01779 ] Object 0: handle = 0x301e6c0000000022, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x5717e75b | vkAcquireNextImageKHR():  Semaphore must not have any pending operations. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-vkCmdBlitImage-srcImage-00219 ] Object 0: handle = 0x28d1c07af70, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xc3f06e26 | vkCmdBlitImage(): srcImage (VkImage 0xe88693000000000c[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_TRANSFER_SRC_BIT. The Vulkan spec states: srcImage must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage flag (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBlitImage-srcImage-00219)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x28d1c07af70[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0xcfcda0000000001e, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0xcfcda0000000001e[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x28d1c641090, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x28d1c641090[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x28d1c641090, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x28d1c641090[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0xdd3a8a0000000015, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0x9fde6b0000000014, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0xdd3a8a0000000015[] pAttachments[2] (VkImageView 0x9fde6b0000000014[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01779 ] Object 0: handle = 0x2cfba2000000001c, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x5717e75b | vkAcquireNextImageKHR():  Semaphore must not have any pending operations. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0x967dd1000000000e[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0x967dd1000000000e[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-vkCmdBlitImage-srcImage-00219 ] Object 0: handle = 0x28d1c641090, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xc3f06e26 | vkCmdBlitImage(): srcImage (VkImage 0x967dd1000000000e[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_TRANSFER_SRC_BIT. The Vulkan spec states: srcImage must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage flag (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBlitImage-srcImage-00219)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0x967dd1000000000e[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0x967dd1000000000e[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x28d1c641090[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0xb991fa0000000024, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0xb991fa0000000024[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x28d1c07af70, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x28d1c07af70[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x28d1c07af70, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x28d1c07af70[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0x84c0580000000017, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0xd897d90000000016, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0x84c0580000000017[] pAttachments[2] (VkImageView 0xd897d90000000016[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01779 ] Object 0: handle = 0x301e6c0000000022, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x5717e75b | vkAcquireNextImageKHR():  Semaphore must not have any pending operations. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0xd5b26f0000000010[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0xd5b26f0000000010[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-vkCmdBlitImage-srcImage-00219 ] Object 0: handle = 0x28d1c07af70, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xc3f06e26 | vkCmdBlitImage(): srcImage (VkImage 0xd5b26f0000000010[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_TRANSFER_SRC_BIT. The Vulkan spec states: srcImage must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage flag (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBlitImage-srcImage-00219)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0xd5b26f0000000010[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0xd5b26f0000000010[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x28d1c07af70[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0xcfcda0000000001e, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0xcfcda0000000001e[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x28d1c641090, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x28d1c641090[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x28d1c641090, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x28d1c641090[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0xd175b40000000013, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0xdcc8fd0000000012, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0xd175b40000000013[] pAttachments[2] (VkImageView 0xdcc8fd0000000012[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01779 ] Object 0: handle = 0x2cfba2000000001c, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x5717e75b | vkAcquireNextImageKHR():  Semaphore must not have any pending operations. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-vkCmdBlitImage-srcImage-00219 ] Object 0: handle = 0x28d1c641090, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xc3f06e26 | vkCmdBlitImage(): srcImage (VkImage 0xe88693000000000c[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_TRANSFER_SRC_BIT. The Vulkan spec states: srcImage must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage flag (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBlitImage-srcImage-00219)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x28d1c641090[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)

It looks like useSemaphores is always true in my case, so that if-block is always executed.

Hi @katz1,
The VkGraphicsPipelineCreateInfo validation errors make sense, they're an error on my part. Removing line 124 in Pipeline.cpp resolves this issue.
For the VkImageUsageFlags: I think that these are validation errors about resources that are not created by the openxr-vulkan-example code, but rather by the OpenXR runtime. It's unfortunately very common that these runtimes are not written very cleanly and generate errors like these. Normally these can be ignored, but they do make troubleshooting much harder.
What puzzles me however is that I would have also thought the same to be the cause of the VkCreateSemaphore issue. I can't see where the openxr-vulkan-example code would use timeline semaphore types (that work through the next ptr of the VkSemaphoreCreateInfo struct, which is always initialized to null in the code).
You say you fixed this issue. How did you do that? What was the issue?
@all500234765 Once we have the original issue figured out, I can take a look at the Meta XR Sim. It may just not (yet) be compatible. Do you happen to have a Quest headset for example to try this without the simulator? That way we could find out if it's the simulator causing the issue.

Sample works fine with Quest 2 but not the MetaXRSim.
Lately i found lots of other bugs but in SteamVR's runtime implementation. Not sure how i will work around some of them yet.

@all500234765 Roger that, annoying!
@katz1 Okay, weird. Let's try something else. Can you comment out the frameState.shouldRender conditional in line 528 in Headset.cpp? It should look like this post fix:
if (/*frameState.shouldRender &&*/ positionValid && orientationValid) // Line 628 with change!
{
  layers.push_back(reinterpret_cast<XrCompositionLayerBaseHeader*>(&compositionLayerProjection));
}

Let's see if that gets rid of the validation errors.
I tried hardcoding the shouldRender flag to false to recreate your situation. When I do so, I don't see render output in my headset (as the above conditional prevents presenting the image to the screen). But you confirm the sample works fully in the same situation, ie. you do get render output in both your headset and in the "mirror view", ie. the window on your desktop screen. I am not sure how this is possible...

I tried the /*frameState.shouldRender &&*/ change you suggested. I still have render output in both headset and mirrorview. The validation issues are still there it seems:
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x2820ad8bce0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x2820ad8bce0[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x2820ad8bce0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x2820ad8bce0[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0xd175b40000000013, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0xdcc8fd0000000012, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0xd175b40000000013[] pAttachments[2] (VkImageView 0xdcc8fd0000000012[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x2820ad8bce0[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0xb991fa0000000024, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0xb991fa0000000024[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x2820ae19800, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x2820ae19800[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x2820ae19800, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x2820ae19800[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0xdd3a8a0000000015, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0x9fde6b0000000014, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0xdd3a8a0000000015[] pAttachments[2] (VkImageView 0x9fde6b0000000014[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x2820ae19800[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0xcfcda0000000001e, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0xcfcda0000000001e[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x2820ad8bce0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x2820ad8bce0[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x2820ad8bce0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x2820ad8bce0[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0x84c0580000000017, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0xd897d90000000016, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0x84c0580000000017[] pAttachments[2] (VkImageView 0xd897d90000000016[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x2820ad8bce0[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0xb991fa0000000024, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0xb991fa0000000024[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x2820ae19800, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x2820ae19800[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x2820ae19800, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x2820ae19800[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0xd175b40000000013, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0xdcc8fd0000000012, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0xd175b40000000013[] pAttachments[2] (VkImageView 0xdcc8fd0000000012[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x2820ae19800[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0xcfcda0000000001e, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0xcfcda0000000001e[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x2820ad8bce0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x2820ad8bce0[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x2820ad8bce0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x2820ad8bce0[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0xdd3a8a0000000015, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0x9fde6b0000000014, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0xdd3a8a0000000015[] pAttachments[2] (VkImageView 0x9fde6b0000000014[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x2820ad8bce0[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0xb991fa0000000024, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0xb991fa0000000024[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x2820ae19800, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x2820ae19800[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x2820ae19800, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x2820ae19800[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0x84c0580000000017, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0xd897d90000000016, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0x84c0580000000017[] pAttachments[2] (VkImageView 0xd897d90000000016[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] | MessageID = 0x2e2f4d65 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] VkCommandBuffer 0x2820ae19800[] is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0xcfcda0000000001e, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0xcfcda0000000001e[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x2820ad8bce0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x2820ad8bce0[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x2820ad8bce0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x2820ad8bce0[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0xd175b40000000013, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0xdcc8fd0000000012, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0xd175b40000000013[] pAttachments[2] (VkImageView 0xdcc8fd0000000012[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)

I still have this change in, I assume you didn't mean I should revert that while trying these new changes.
  if (!frameState.shouldRender)
  {
    // Let the host know that we don't want to render this frame
    // We do still need to end the frame however
    //return BeginFrameResult::SkipRender;
  }

Quick update: I noticed the validation errors you now get are not the same. It's missing all the calls from the mirror view (the window on your desktop).
Anyhow, I dug a bit into the OpenXR-Vk-D3D12 tool you are using and discovered some interesting tidbits. The timeline semaphore issue you saw, for example, is expected when using the OpenXR Vulkan extension that this sample project is using. Turns out there is a newer version of that extension that may work better. When I switched over to using the new extension, and adapted the code accordingly, I got a crash in release mode (and only in release mode) that I was able to track down to semaphores again. To reiterate, it looks like the validation errors you are getting are also because an issue with semaphores.
So in short, I will try to find out what is wrong with the semaphores in release mode with the newer OpenXR Vulkan extension, push that commit, and then we can see if that also fixes the validation errors you are seeing.

Okay @katz1 I have pushed two commits. Could you please pull (make sure that any local changes you may have are overwritten) and see if this changes anything on your end?

I pulled and reverted my changes. Sadly I have an Access Violation error now at line:
XrResult result = xrEnumerateInstanceExtensionProperties(nullptr, 0u, &instanceExtensionCount, nullptr);
I guess this is the first XR api call. My environment doesn't like something about the OpenXR update it seems.

Weird, let's try reverting the OpenXR version locally then. Please try going into the repository openxr-vulkan-example > external > openxr and deleting everything in the openxr folder, then unzipping the contents of this zip file in there:
openxr-v1.0.25.zip
This will revert OpenXR to version 1.0.25, which worked for you previously.
Let me know what happens when you then try to run the sample.

If I revert the OpenXR update but keep your other commit (Use the new XR_KHR_vulkan_enable2 OpenXR extension), it seems like I am in the same situation as I originally was without any changes. Meaning I don't get the scene in the headset or on mirror view. These are the validation errors, but I believe we already concluded that these ones are harmless:
[Vulkan] Validation Error: [ VUID-VkImageCreateInfo-usage-requiredbitmask ] | MessageID = 0x34d7a349 | vkCreateImage(): pCreateInfo->usage is zero. The Vulkan spec states: usage must not be 0 (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageCreateInfo-usage-requiredbitmask)
[Vulkan] Validation Error: [ VUID-VkImageCreateInfo-usage-requiredbitmask ] | MessageID = 0x34d7a349 | vkCreateImage(): pCreateInfo->usage is zero. The Vulkan spec states: usage must not be 0 (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageCreateInfo-usage-requiredbitmask)
[Vulkan] Validation Error: [ VUID-VkImageCreateInfo-usage-requiredbitmask ] | MessageID = 0x34d7a349 | vkCreateImage(): pCreateInfo->usage is zero. The Vulkan spec states: usage must not be 0 (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageCreateInfo-usage-requiredbitmask)
[Vulkan] Validation Error: [ VUID-VkImageViewCreateInfo-image-04441 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xb75da543 | vkCreateImageView(): pCreateInfo->image (VkImage 0xe88693000000000c[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_SAMPLED_BIT|VK_IMAGE_USAGE_STORAGE_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT|VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT|VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT|VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT|VK_IMAGE_USAGE_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR|VK_IMAGE_USAGE_FRAGMENT_DENSITY_MAP_BIT_EXT|VK_IMAGE_USAGE_VIDEO_DECODE_DST_BIT_KHR|VK_IMAGE_USAGE_VIDEO_DECODE_DPB_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_SRC_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_DPB_BIT_KHR|VK_IMAGE_USAGE_SAMPLE_WEIGHT_BIT_QCOM|VK_IMAGE_USAGE_SAMPLE_BLOCK_MATCH_BIT_QCOM. The Vulkan spec states: image must have been created with a usage value containing at least one of the usages defined in the valid image usage list for image views (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageViewCreateInfo-image-04441)
[Vulkan] Validation Error: [ VUID-VkImageViewCreateInfo-image-04441 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xb75da543 | vkCreateImageView(): pCreateInfo->image (VkImage 0x967dd1000000000e[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_SAMPLED_BIT|VK_IMAGE_USAGE_STORAGE_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT|VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT|VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT|VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT|VK_IMAGE_USAGE_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR|VK_IMAGE_USAGE_FRAGMENT_DENSITY_MAP_BIT_EXT|VK_IMAGE_USAGE_VIDEO_DECODE_DST_BIT_KHR|VK_IMAGE_USAGE_VIDEO_DECODE_DPB_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_SRC_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_DPB_BIT_KHR|VK_IMAGE_USAGE_SAMPLE_WEIGHT_BIT_QCOM|VK_IMAGE_USAGE_SAMPLE_BLOCK_MATCH_BIT_QCOM. The Vulkan spec states: image must have been created with a usage value containing at least one of the usages defined in the valid image usage list for image views (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageViewCreateInfo-image-04441)
[Vulkan] Validation Error: [ VUID-VkImageViewCreateInfo-image-04441 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xb75da543 | vkCreateImageView(): pCreateInfo->image (VkImage 0xd5b26f0000000010[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_SAMPLED_BIT|VK_IMAGE_USAGE_STORAGE_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT|VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT|VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT|VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT|VK_IMAGE_USAGE_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR|VK_IMAGE_USAGE_FRAGMENT_DENSITY_MAP_BIT_EXT|VK_IMAGE_USAGE_VIDEO_DECODE_DST_BIT_KHR|VK_IMAGE_USAGE_VIDEO_DECODE_DPB_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_SRC_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_DPB_BIT_KHR|VK_IMAGE_USAGE_SAMPLE_WEIGHT_BIT_QCOM|VK_IMAGE_USAGE_SAMPLE_BLOCK_MATCH_BIT_QCOM. The Vulkan spec states: image must have been created with a usage value containing at least one of the usages defined in the valid image usage list for image views (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageViewCreateInfo-image-04441)

If I use the previous workaround and comment out the line return BeginFrameResult::SkipRender;, then it works again.

Thanks for giving that a shot @katz1 - looks like the problem didn't have anything to do with the XR_KHR_vulkan_enable2 extension then, that's unfortunate. I assume you still get the same verification errors in the console after applying our BeginFrameResult::SkipRender workaround?
I have done some research and discovered that I did not really update OpenXR properly in my commit 2090ef58f89f089ab52ed803b53422d2789ee86d. I have now done so in the latest commit cf3cd6beaf27bdd1bfce01f69c61713c13cd6b45. Last time, you had a crash in the first OpenXR function xrEnumerateApiLayerProperties() - I hope this new commit will fix that and run, maybe with the same verification errors, maybe without. Please try pulling the latest commit and running that to see what happens.
If you still get the crash, I would love if you could check out Khronos' own Hello XR Sample and let me know if that also crashes on your setup or if that works fine. It's pretty straightforward to build their sample.
Thanks for sticking around while we are troubleshooting this annoying issue by the way, it really helps to improve the quality of this project. I appreciate it! :)

Thanks for looking into that! Update time:
I don't have an explanation as to why the new(er?) OpenXR versions crash for you when using with this project. One idea to try would be to simply build OpenXR yourself on your machine. Since you get a "hard" crash on the first OpenXR call, it may be some kind of incompatibility. You can build OpenXR yourself super easily. Just clone the repo from here. You can then generate build files using CMake with the default parameters. I do have to build in debug and release mode separately in Visual Studio, which generates an openxr_loader.lib (release) and an openxr_loaderd.lib (debug). Copy both .lib files into the external/openxr/lib/win/ folder of this project. Then also copy the headers from the OpenXR source into the external/openxr/include folder of this project. This is how I made that .zip file for you earlier. If you do these steps yourself, it will eliminate any possibility of the binaries I supply being incompatible with your environment. Let me know if you have any questions.
Let's also look at the other remaining issue again, the validation errors. Here I was able to make some progress. I used the Vulkan Configurator program that is part of the Vulkan SDK to enable extra synchronization checks:

With this enabled, I can indeed see that this project was not correctly synchronizing in the area of code that renders the mirror view. I believe this may be the cause for the validation errors you are seeing. I don't have a 'beautiful' fix for this yet, but found that  I could simply hard-code full synchronization to get rid of any warnings or errors. This is not as performant as it could be, but let's try it out to see if it makes your validation errors disappear.
Please go back into the state of the project where everything works but you get the validation errors (ie. check out the latest commit, apply the OpenXR fix with the .zip file I provided - or build OpenXR yourself on your own system -, then fix the render output by commenting out line 446 in Headset.cpp: return BeginFrameResult::SkipRender;). Confirm that everything works and that you are still seeing the validation errors in the console.
Now head into MirrorView.cpp and change line 181/182 to:
vkCmdPipelineBarrier(commandBuffer, VK_PIPELINE_STAGE_ALL_GRAPHICS_BIT, VK_PIPELINE_STAGE_ALL_GRAPHICS_BIT,
                       VK_DEPENDENCY_BY_REGION_BIT, 0u, nullptr, 0u, nullptr, 1u, &imageMemoryBarrier);

Change line 195/196 to:
vkCmdPipelineBarrier(commandBuffer, VK_PIPELINE_STAGE_ALL_GRAPHICS_BIT, VK_PIPELINE_STAGE_ALL_GRAPHICS_BIT,
                       VK_DEPENDENCY_BY_REGION_BIT, 0u, nullptr, 0u, nullptr, 1u, &imageMemoryBarrier);

Change line 250/251 to:
vkCmdPipelineBarrier(commandBuffer, VK_PIPELINE_STAGE_ALL_GRAPHICS_BIT, VK_PIPELINE_STAGE_ALL_GRAPHICS_BIT,
                       VK_DEPENDENCY_BY_REGION_BIT, 0u, nullptr, 0u, nullptr, 1u, &imageMemoryBarrier);

And change line 264/265 to:
vkCmdPipelineBarrier(commandBuffer, VK_PIPELINE_STAGE_ALL_GRAPHICS_BIT, VK_PIPELINE_STAGE_ALL_GRAPHICS_BIT,
                       VK_DEPENDENCY_BY_REGION_BIT, 0u, nullptr, 0u, nullptr, 1u, &imageMemoryBarrier);

These changes simply set all the stage parameters of the four vkCmdPipelineBarrier() calls to VK_PIPELINE_STAGE_ALL_GRAPHICS_BIT.
Please let me know if that fixes the validation errors in the console.

Hi! Yes, the openxr_loader update seem to work fine with my locally built .lib files now. I confirmed that everything works with the modified Headset.cpp, and I still have the validation errors.
I applied your suggested changes to MirrorView.cpp, but it doesn't seem to have any effect on the validation errors. For reference, these are my current errors:
[Vulkan] Validation Error: [ VUID-VkImageCreateInfo-usage-requiredbitmask ] | MessageID = 0x34d7a349 | vkCreateImage(): pCreateInfo->usage is zero. The Vulkan spec states: usage must not be 0 (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageCreateInfo-usage-requiredbitmask)
[Vulkan] Validation Error: [ VUID-VkImageCreateInfo-usage-requiredbitmask ] | MessageID = 0x34d7a349 | vkCreateImage(): pCreateInfo->usage is zero. The Vulkan spec states: usage must not be 0 (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageCreateInfo-usage-requiredbitmask)
[Vulkan] Validation Error: [ VUID-VkImageCreateInfo-usage-requiredbitmask ] | MessageID = 0x34d7a349 | vkCreateImage(): pCreateInfo->usage is zero. The Vulkan spec states: usage must not be 0 (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageCreateInfo-usage-requiredbitmask)
[Vulkan] Validation Error: [ VUID-VkImageViewCreateInfo-image-04441 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xb75da543 | vkCreateImageView(): pCreateInfo->image (VkImage 0xe88693000000000c[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_SAMPLED_BIT|VK_IMAGE_USAGE_STORAGE_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT|VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT|VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT|VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT|VK_IMAGE_USAGE_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR|VK_IMAGE_USAGE_FRAGMENT_DENSITY_MAP_BIT_EXT|VK_IMAGE_USAGE_VIDEO_DECODE_DST_BIT_KHR|VK_IMAGE_USAGE_VIDEO_DECODE_DPB_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_SRC_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_DPB_BIT_KHR|VK_IMAGE_USAGE_SAMPLE_WEIGHT_BIT_QCOM|VK_IMAGE_USAGE_SAMPLE_BLOCK_MATCH_BIT_QCOM. The Vulkan spec states: image must have been created with a usage value containing at least one of the usages defined in the valid image usage list for image views (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageViewCreateInfo-image-04441)
[Vulkan] Validation Error: [ VUID-VkImageViewCreateInfo-image-04441 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xb75da543 | vkCreateImageView(): pCreateInfo->image (VkImage 0x967dd1000000000e[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_SAMPLED_BIT|VK_IMAGE_USAGE_STORAGE_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT|VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT|VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT|VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT|VK_IMAGE_USAGE_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR|VK_IMAGE_USAGE_FRAGMENT_DENSITY_MAP_BIT_EXT|VK_IMAGE_USAGE_VIDEO_DECODE_DST_BIT_KHR|VK_IMAGE_USAGE_VIDEO_DECODE_DPB_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_SRC_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_DPB_BIT_KHR|VK_IMAGE_USAGE_SAMPLE_WEIGHT_BIT_QCOM|VK_IMAGE_USAGE_SAMPLE_BLOCK_MATCH_BIT_QCOM. The Vulkan spec states: image must have been created with a usage value containing at least one of the usages defined in the valid image usage list for image views (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageViewCreateInfo-image-04441)
[Vulkan] Validation Error: [ VUID-VkImageViewCreateInfo-image-04441 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xb75da543 | vkCreateImageView(): pCreateInfo->image (VkImage 0xd5b26f0000000010[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_SAMPLED_BIT|VK_IMAGE_USAGE_STORAGE_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT|VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT|VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT|VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT|VK_IMAGE_USAGE_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR|VK_IMAGE_USAGE_FRAGMENT_DENSITY_MAP_BIT_EXT|VK_IMAGE_USAGE_VIDEO_DECODE_DST_BIT_KHR|VK_IMAGE_USAGE_VIDEO_DECODE_DPB_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_SRC_BIT_KHR|VK_IMAGE_USAGE_VIDEO_ENCODE_DPB_BIT_KHR|VK_IMAGE_USAGE_SAMPLE_WEIGHT_BIT_QCOM|VK_IMAGE_USAGE_SAMPLE_BLOCK_MATCH_BIT_QCOM. The Vulkan spec states: image must have been created with a usage value containing at least one of the usages defined in the valid image usage list for image views (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageViewCreateInfo-image-04441)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0xd175b40000000013, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0xdcc8fd0000000012, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0xd175b40000000013[] pAttachments[2] (VkImageView 0xdcc8fd0000000012[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-vkCmdBlitImage-srcImage-00219 ] Object 0: handle = 0x21949267da0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xc3f06e26 | vkCmdBlitImage(): srcImage (VkImage 0xe88693000000000c[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_TRANSFER_SRC_BIT. The Vulkan spec states: srcImage must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage flag (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBlitImage-srcImage-00219)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0xe88693000000000c, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0xe88693000000000c[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0xdd3a8a0000000015, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0x9fde6b0000000014, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0xdd3a8a0000000015[] pAttachments[2] (VkImageView 0x9fde6b0000000014[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0x967dd1000000000e[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0x967dd1000000000e[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-vkCmdBlitImage-srcImage-00219 ] Object 0: handle = 0x219492d72d0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xc3f06e26 | vkCmdBlitImage(): srcImage (VkImage 0x967dd1000000000e[]) was created with VkImageUsageFlags(0) but requires VK_IMAGE_USAGE_TRANSFER_SRC_BIT. The Vulkan spec states: srcImage must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage flag (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBlitImage-srcImage-00219)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01212 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xff795e16 | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL) is not compatible with VkImage 0x967dd1000000000e[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01212)
[Vulkan] Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-01208 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0xf855a75b | vkCmdPipelineBarrier(): pImageMemoryBarriers[0].newLayout (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL) is not compatible with VkImage 0x967dd1000000000e[] usage flags VkImageUsageFlags(0). The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-01208)
[Vulkan] Validation Error: [ VUID-vkResetFences-pFences-01123 ] Object 0: handle = 0x301e6c0000000022, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x68a5074e | vkResetFences(): pFences[0] (VkFence 0x301e6c0000000022[]) is in use. The Vulkan spec states: Each element of pFences must not be currently associated with any queue command that has not yet completed execution on that queue (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetFences-pFences-01123)
[Vulkan] Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x21949267da0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xd10d270000000018, type = VK_OBJECT_TYPE_COMMAND_POOL; | MessageID = 0x1e7883ea | vkResetCommandBuffer():  (VkCommandBuffer 0x21949267da0[]) is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
[Vulkan] Validation Error: [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object 0: handle = 0x21949267da0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x84029a9f | vkBeginCommandBuffer():  on active VkCommandBuffer 0x21949267da0[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
[Vulkan] Validation Error: [ VUID-vkCmdBeginRenderPass-initialLayout-00895 ] Object 0: handle = 0xd5b26f0000000010, type = VK_OBJECT_TYPE_IMAGE; Object 1: handle = 0xfa21a40000000003, type = VK_OBJECT_TYPE_RENDER_PASS; Object 2: handle = 0x84c0580000000017, type = VK_OBJECT_TYPE_FRAMEBUFFER; Object 3: handle = 0xd897d90000000016, type = VK_OBJECT_TYPE_IMAGE_VIEW; | MessageID = 0x34f84ef4 | vkCmdBeginRenderPass(): pRenderPassBegin->renderPass (VkRenderPass 0xfa21a40000000003[]) was created with pCreateInfo->pAttachments[2].finalLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL, but VkFramebuffer 0x84c0580000000017[] pAttachments[2] (VkImageView 0xd897d90000000016[]) usage is VkImageUsageFlags(0). The Vulkan spec states: If any of the initialLayout or finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReference structures specified when creating the render pass specified in the renderPass member of pRenderPassBegin is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then the corresponding attachment image view of the framebuffer specified in the framebuffer member of pRenderPassBegin must have been created with a usage value including VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-vkCmdBeginRenderPass-initialLayout-00895)