From c0f7dc34e799c023c6f4f7c1a73005c32e8ec02e Mon Sep 17 00:00:00 2001 From: baldurk Date: Fri, 9 Aug 2019 12:18:52 +0100 Subject: [PATCH] Ignore racey validation message about swapchain currentExtent --- renderdoc/driver/vulkan/vk_core.cpp | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/renderdoc/driver/vulkan/vk_core.cpp b/renderdoc/driver/vulkan/vk_core.cpp index a08da336f..b9a65b98b 100644 --- a/renderdoc/driver/vulkan/vk_core.cpp +++ b/renderdoc/driver/vulkan/vk_core.cpp @@ -3375,11 +3375,18 @@ VkBool32 WrappedVulkan::DebugCallback(MessageSeverity severity, MessageCategory if(category == MessageCategory::Performance) return false; - // Non-linear image is aliased with linear buffer + // "Non-linear image is aliased with linear buffer" // Not an error, the validation layers complain at our whole-mem bufs if(strstr(pMessageId, "InvalidAliasing") || strstr(pMessage, "InvalidAliasing")) return false; + // "vkCreateSwapchainKHR() called with imageExtent, which is outside the bounds returned by + // vkGetPhysicalDeviceSurfaceCapabilitiesKHR(): currentExtent" + // This is quite racey, the currentExtent can change in between us checking it and the valiation + // layers checking it. We handle out of date, so this is likely fine. + if(strstr(pMessageId, "VUID-VkSwapchainCreateInfoKHR-imageExtent")) + return false; + RDCWARN("[%s] %s", pMessageId, pMessage); }