Vulkan: Fix possible mismatch between EFB framebuffer and render pass

This could happen when changing MSAA settings or internal resolution at
runtime.

1 files changed, 4 insertions, 6 deletions

diff --git a/Source/Core/VideoBackends/Vulkan/FramebufferManager.cpp b/Source/Core/VideoBackends/Vulkan/FramebufferManager.cpp
index bf13701600..9c2c712837 100644
--- a/Source/Core/VideoBackends/Vulkan/FramebufferManager.cpp
+++ b/Source/Core/VideoBackends/Vulkan/FramebufferManager.cpp
@@ -318,17 +318,15 @@ void FramebufferManager::DestroyEFBFramebuffer()
   m_efb_resolve_depth_texture.reset();
 }
 
-void FramebufferManager::ResizeEFBTextures()
+void FramebufferManager::RecreateEFBFramebuffer()
 {
   DestroyEFBFramebuffer();
-  if (!CreateEFBFramebuffer())
-    PanicAlert("Failed to create EFB textures");
-}
 
-void FramebufferManager::RecreateRenderPass()
-{
   if (!CreateEFBRenderPasses())
     PanicAlert("Failed to create EFB render pass");
+
+  if (!CreateEFBFramebuffer())
+    PanicAlert("Failed to create EFB textures");
 }
 
 void FramebufferManager::RecompileShaders()