OK, I’ve tested this extensively:
- 535.43.10 and 535.43.11 drivers (built and installed via Frogging-Family set of scripts)
- RTX 3070 Ti
- Kernel 6.5.5-1 (Manjaro)
- bleeding-edge vkd3d and nv-enable-dgcc branch build (were forcefully installed to game’s prefix with override to native, with prefix removal before switching the versions – so no chance of a mix-up)
- Game version of 1.7.33
- Numerous different versions of Proton, ranging from stable down to bleeding edge builds
The situation is the same: game runs on 535.43.10, save for performance issues, and hangs immediately when trying to load a save or start a new game on 535.43.11.
On 535.43.10 the only difference between bleeding edge vkd3d and dlls built from nv-enable-dgcc is that the latter performs even worse (FPS in single digits), whereas with build straight out of master branch I’m seeing the same 28-30 FPS in New Atlantis and 40 to 50 FPS elsewhere (interiors, barren planets with little to none vegetation and small details).
Can somebody with access both to Turing and Ampere cards cross-check the behavior?