tribbin
Published
PROTON_VERSION='GE-Proton7-14' protontricks 223750 d3dcompiler_47 vcrun2019 corefonts xact
After Alt-Tab the screen disappears. When selecting DCS and pressing Alt+F4 the screen returns with the exit-prompt.
Starting without protontricks will not pass the loading screen.
gamemoderun %command%
Random crashes. Like 6 times in 3 hours.
Increasing max_map_count kernel parameter: https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1422699309
Without the max_map_count kernel setting increased (I set it to 1000000), the game would regularily crash when fast traveling.
Controllers works in all other games and previously with this game. New Origin intermediate seems to be the culprit.
I tried various versions of Proton (7/GE/...).
The Steam overlay does not work anymore, probably since the new Origin intermediate. This is probably why the controller inputs are not forwarded to the game.
Even when forced to use keyboard, the frame-rate is not acceptable for competitive players.
Xbox controller was not usable.
Input lag, input (Xbox Controller) errors and low framerate.
Getting 60fps at HIGH and 4K and no inputlag. It simply works now.
PROTON_NO_ESYNC=1 %command%
Proton Experimental crashed frequently, but on Proton 7 I had no problems.
If it is magically stable for a while, this game is awesome.
Tried all kinds op Proton versions and launch options. Sometimes it seems stable for a while, but every time the frequent crashes return.
I was waiting for a Proton stability fix, but after two weeks I see no indication (and no responses) that this is being worked on.
Popup message: "DX12 is not supported on your system. Try running without the -dx12 or -d3d12 command line argument."
I tried both Experimental and GE
My previous ("borked") report was using Experimental or GE, which did not work. Using Proton 7 it worked out of the box.
I got 60 fps (vsync limit) on 4K, rendered at 50%, using high settings and dialing down texture settings one notch because of my limited video memory.
Had to create /usr/local/bin/pulseaudio to work around SIGSEGV 11 error message.
https://steamcommunity.com/app/391220/discussions/1/3288067088128170128/
The PulseAudio SIGSEGV 11 (segmentation fault) is only present in this game and not the two other Tomb Raider games from this trilogy.
Tried demo. Didn't work.
Proton Experimental is my default, but the game would not start. Had to select Proton 9.0-2 for it to start.
XBox Gamepad was not detected the first few times I started this game. Did some tinkering and not it works. Don't know what I changed.
gamemoderun %command%
Controllers disconnect (2 player split screen) shortly after starting playing.
My Steam family members can't install friend-pass, so I opted for split screen but that has controller problems.
Tried Experimental and GE.
gamemoderun WINEDLLOVERRIDES="amd_ags_x64=b" %command%
I had low (~30fps) in medium settings with audio stutters when I booted the game, but high fps and no stutters when I set it to ultra (balanced FSR2), but that might be due to the shaders being finished building. I haven't tried without WINEDLLOVERRIDES="amd_ags_x64=b" (which I got from protondb) and as it works for me, I'm not touching anything.
gamemoderun %command% --launcher-skip
The RT Ultra settings reverts back to performance mode RT.
Startup screen was overlayed over the game screen, making it unplayable. Was only fixed by using Proton 8.
Origin screens overlay the game and are hard to close.
Using GE Proton and renaming the V -> noV makes this game run perfectly. Finished the game twice.
