vulkan_debug_callback: Ignore InvalidCommandBuffer-VkDescriptorSet errors
This validation error is spammed on some titles, asserting that VkDescriptorSet 0x0[] was destroyed. This is likely a validation layer bug when using VK_KHR_push_descriptor, which can avoid using traditional VkDescriptorSet. It should be safe to ignore for now.
This commit is contained in:
		| @@ -16,6 +16,7 @@ VkBool32 Callback(VkDebugUtilsMessageSeverityFlagBitsEXT severity, | ||||
|     switch (static_cast<u32>(data->messageIdNumber)) { | ||||
|     case 0x682a878au: // VUID-vkCmdBindVertexBuffers2EXT-pBuffers-parameter | ||||
|     case 0x99fb7dfdu: // UNASSIGNED-RequiredParameter (vkCmdBindVertexBuffers2EXT pBuffers[0]) | ||||
|     case 0xe8616bf2u: // Bound VkDescriptorSet 0x0[] was destroyed. Likely push_descriptor related | ||||
|         return VK_FALSE; | ||||
|     default: | ||||
|         break; | ||||
|   | ||||
		Reference in New Issue
	
	Block a user
	 ameerj
					ameerj