From bbe681d9caa9ace6a51a11f7b3c74f556aac4199 Mon Sep 17 00:00:00 2001
From: Joshua Ashton <joshua@froggi.es>
Date: Fri, 3 Apr 2020 08:21:35 +0100
Subject: [PATCH] [dxvk] Fix incorrect logic in resolveDepthStencilImage

This fallbath check path should be triggered if we aren't currently using the fb.

Impacts #1537
---
 src/dxvk/dxvk_context.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/dxvk/dxvk_context.cpp b/src/dxvk/dxvk_context.cpp
index 67835e988..797c4e206 100644
--- a/src/dxvk/dxvk_context.cpp
+++ b/src/dxvk/dxvk_context.cpp
@@ -1774,7 +1774,7 @@ namespace dxvk {
               || !srcImage->isFullSubresource(region.srcSubresource, region.extent)
               || dstImage->info().format != srcImage->info().format;
     
-    if (useFb) {
+    if (!useFb) {
       // Additionally, the given mode combination must be supported.
       const auto& properties = m_device->properties().khrDepthStencilResolve;