Rakqoi
Published
Nearly perfect with no real issues.
Moving through the long hallways between major areas (masked loading screens) drops the framerate to <15fps for around 30s, and load times are a bit longer than on Windows. Teleporting between areas bypasses this after the first time through anyway. Otherwise, perfect performance.
Played with DS4 native, DS4 through Steam Input, and Steam Controller without issues, though I had to disable touchpad input in (KDE Plasma) system settings to stop the DS4 touchpad from acting like a mouse and sending a left click input when pressed.
Borked as of the season 3 update.
The game does not launch at all under any mix of compatibility options, proton version, or launch flags.
Disabling Esync/Fsync is required to avoid the game basically softlocking.
The biggest issue is that the game drops to <30fps during almost any intense particle effects, especially with multiple NPC companions. Certain menus hang for a couple seconds, and loading screens are long and laggy.
Very playable without companions and I haven't run into many performance issues in this scenario. Otherwise, I boot back into Windows for multiplayer, during which the performance and load times are not worth the hassle.
I'll post again once I play GE2RB, though I don't expect it to be much different than GER.
Runs extremely well out of the box. Some launch options may help or hurt performance depending on your machine.
%command% -USEALLAVAILABLECORES
On DX12 mode (default), some objects are missing their textures, just displaying as the blank material. This is most notable on SEAF Artillery shells, which are all just plain silver (instead of color coded), but also affects some grenades, weapon magazines, and certain props in the game world. However, aside from the minor inconvenience with artillery, this doesn't affect the gameplay at all and is hardly noticeable.
This can be fixed with the launch argument --use-d3d11, but for me, this makes the game look much worse and perform very significantly worse, even with -force-vulkan and -USEALLAVAILABLECORES. It also changes how the game's lighting looks, leading to it being much darker in some scenarios, compared to DX12. I also have had some crashes with d3d11, which has never happened when playing without the launch argument.
1 pixel white border around the screen while in windowless fullscreen. This can be fixed by using exclusive fullscreen.
Alternatively (if using KDE) you can have borderless fullscreen without the pixel border by switching to windowed mode, then press ALT+F3 to open the KDE window menu > More Actions > Fullscreen
You can skip the startup videos with the launch argument +connect_lobby -1. It just tries to launch your game and immediately connect to a non-existent lobby, so you just have to click once to close the "failed" popup.
