mirror of
https://github.com/doitsujin/dxvk.git
synced 2025-01-31 14:52:11 +01:00
[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.
This commit is contained in:
parent
d5ba36443e
commit
3b1e03f988
@ -47,17 +47,17 @@ namespace dxvk {
|
|||||||
}} },
|
}} },
|
||||||
/* Far Cry 3: Assumes clear(0.5) on an UNORM *
|
/* Far Cry 3: Assumes clear(0.5) on an UNORM *
|
||||||
* format to result in 128 on AMD and 127 on *
|
* format to result in 128 on AMD and 127 on *
|
||||||
* Nvidia. Most Vulkan drivers clear to 127, *
|
* Nvidia. We assume that the Vulkan drivers *
|
||||||
* assuming higher values causes artifacts. */
|
* match the clear behaviour of D3D11. */
|
||||||
{ "farcry3_d3d11.exe", {{
|
{ "farcry3_d3d11.exe", {{
|
||||||
{ "dxgi.customVendorId", "10de" },
|
{ "dxgi.nvapiHack", "False" },
|
||||||
}} },
|
}} },
|
||||||
{ "fc3_blooddragon_d3d11.exe", {{
|
{ "fc3_blooddragon_d3d11.exe", {{
|
||||||
{ "dxgi.customVendorId", "10de" },
|
{ "dxgi.nvapiHack", "False" },
|
||||||
}} },
|
}} },
|
||||||
/* Far Cry 4: Same as Far Cry 3 */
|
/* Far Cry 4: Same as Far Cry 3 */
|
||||||
{ "FarCry4.exe", {{
|
{ "FarCry4.exe", {{
|
||||||
{ "dxgi.customVendorId", "10de" },
|
{ "dxgi.nvapiHack", "False" },
|
||||||
}} },
|
}} },
|
||||||
/* Far Cry 5: Avoid CPU <-> GPU sync */
|
/* Far Cry 5: Avoid CPU <-> GPU sync */
|
||||||
{ "FarCry5.exe", {{
|
{ "FarCry5.exe", {{
|
||||||
|
Loading…
x
Reference in New Issue
Block a user