From 3b1e03f9887fc7b540c90e9e34e32b46612281bb Mon Sep 17 00:00:00 2001
From: Philip Rebohle <philip.rebohle@tu-dortmund.de>
Date: Wed, 12 Jun 2019 12:32:30 +0200
Subject: [PATCH] [util] Report correct GPU vendor to Far Cry 3, 4 and Blood
 Dragon

Now that fast clear behaviour has been fixed in RADV, reporting an
Nvidia GPU breaks rendering again since the game expects the clear
behaviour to match that of the Windows D3D11 drivers exactly. To
recap, clear(0.5) on an R8_UNORM render target results in 127 on
Nvidia GPUs and 128 on AMD GPUs.
---
 src/util/config/config.cpp | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/util/config/config.cpp b/src/util/config/config.cpp
index 4649642d4..4b40c2cb4 100644
--- a/src/util/config/config.cpp
+++ b/src/util/config/config.cpp
@@ -47,17 +47,17 @@ namespace dxvk {
     }} },
     /* Far Cry 3: Assumes clear(0.5) on an UNORM  *
      * format to result in 128 on AMD and 127 on  *
-     * Nvidia. Most Vulkan drivers clear to 127,  *
-     * assuming higher values causes artifacts.   */
+     * Nvidia. We assume that the Vulkan drivers  *
+     * match the clear behaviour of D3D11.        */
     { "farcry3_d3d11.exe", {{
-      { "dxgi.customVendorId",              "10de" },
+      { "dxgi.nvapiHack",                   "False" },
     }} },
     { "fc3_blooddragon_d3d11.exe", {{
-      { "dxgi.customVendorId",              "10de" },
+      { "dxgi.nvapiHack",                   "False" },
     }} },
     /* Far Cry 4: Same as Far Cry 3               */
     { "FarCry4.exe", {{
-      { "dxgi.customVendorId",              "10de" },
+      { "dxgi.nvapiHack",                   "False" },
     }} },
     /* Far Cry 5: Avoid CPU <-> GPU sync          */
     { "FarCry5.exe", {{