Hello @waspennator, it might be interesting to tinker with a dxvk config file beside the game's executable and `d3d9.maxAvailableMemory` in a similar way to https://github.com/doitsujin/dxvk/commit/51e56c04209294cb38c174ec76129bdb857d85c9.
> Hello [@waspennator](https://github.com/waspennator), it might be interesting to tinker with a dxvk config file beside the game's executable and `d3d9.maxAvailableMemory` in a similar way to [doitsujin/dxvk@51e56c0](ht...
Hello @waspennator, it might be interesting to tinker with a dxvk config file beside the game's executable and `d3d9.maxAvailableMemory` in a similar way to https://github.com/doitsujin/dxvk/commit/51e56c04209294cb38c174...
According to pcgamingwiki and testing on my deck, the game will limit you to only using 2x MSAA on any device with a gpu that has more than 2gb of vram. It works if I use the specific PrototypeFix patch to limit the VRAM...
For me it crashes after a bit of the first mission on the steam deck without disabling fsync, tried beta candidate / main with proton stable. The game is also quite choppy if i have vsync on and 60 limit but that might b...
> It might be interesting to test if setting the game's launch options to `PROTON_NO_FSYNC=1 %command%` or `PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command%` has an effect. do you still need a test of these two parameters? ...