Topic on Talk:Far Cry 2
This page shows the changes between two versions of a post by Deton24 in the topic "A new fix for splash screen crash issue" on Talk:Far Cry 2.
You can see other versions of this post at its history page.
Line 1: | Line 1: | ||
− | Possible. From other examples - in NFSMW 2005 wasn't any better with regular DXVK, although it was on 2021 version from September. GTA IV had excellent performance increase even for most people. <br><br>Maybe the whole Far Cry series is just very unlucky. Usually, Far Cry titles were games with the most multithreading issues, and it always strongly relied on single core performance (less in FC6 now), and in FC5 it was worse too vs OG DX11, but with even older DXVK version.<br> I tested both Far Cry 2 and Far Cry 3 in DX9 mode, and even on AMD GPUs, which are known for worse DX9 driver than on NVIDIA, it was still worse using DXVK. No matter if I used async, gpl-async, or regular DXVK (although GPL flag shouldn't be used in most cases on e.g. Polaris and older, as it can cause crashes | + | Possible. From other examples - in NFSMW 2005 wasn't any better with regular DXVK, although it was on 2021 version from September. GTA IV had excellent performance increase even for most people. <br><br>Maybe the whole Far Cry series is just very unlucky. Usually, Far Cry titles were games with the most multithreading issues, and it always strongly relied on single core performance (less in FC6 now), and in FC5 it was worse too vs OG DX11, but with even older DXVK version.<br> I tested both Far Cry 2 and Far Cry 3 in DX9 mode, and even on AMD GPUs, which are known for worse DX9 driver than on NVIDIA, it was still worse using DXVK. No matter if I used async, gpl-async, or regular DXVK (although GPL flag shouldn't be used in most cases on e.g. Polaris and older, as it can cause crashes due to broken Async Compute on these GPUS; here it wasn't the case, maybe due to DX9). |