guyonweed
Published
PROTON_NO_D3D11=1 %command%
Switching away from fullscreen to windowed sometimes results in the screen not scaling properly. This was encountered in Proton 6.0-8, but not after switching to Proton Experimental, so it could be a bug in Proton.
Launching with PROTON_NOD3D_11=1 %command% on Proton 6.0-8 was necessary to avoid a nasty bug with the Stardock Launcher which causes the window to not render to screen. The window is still there, of course, but you have to guess the location of the Play button. However, there also appears to be a bug in Proton 6.0-8 that makes it impossible to start any Single Player or Multiplayer games because the game is unable to contact Steam and, therefore, cannot confirm you have the full version of the game, thus locking you out. This problem cleared itself up after switching to Proton Experimental, but now the bug in the Stardock Launcher is back and setting PROTON_NOD3D_11=1 %command% no longer fixes it.
Minimal tinkering with launch options after which it runs just fine (albeit with some stuttering during cinematics).
OPENSSL_ia32cap=:~0x20000000 && %command%
Cinematics seem to stutter intermittantly.
At least initially cinematics render such that they wrap around the screen as if there's a sync issue with the monitor. This occurs whether in full screen or windowed. Gameplay, however, is unaffected. Also, you must launch with OPENSSL_ia32cap=:~0x20000000 && %command% in your launch options or the game will crash before even reaching the main menu due to a bug in the feature detection used by OpenSSL which crashes on 10th and 11th generation Intel CPUs.
