
Creak
Published
The game in itself has bugs (no matter which platform), but it works!
The only bug I found was when trying to join a game, but I was not the only one and we were all on different platforms. It finally worked when changing the server area to Asia.
I have seen in another report here that changing server area and then reselect the the wanted server area is a workaround for this bug. It tend to believe this is true considering my experience.
Can't launch the game
I tried with Proton 5.0, 5.13 and experimental. The game won't start.
With Proton 5.0 I got to have a tiny "systray" window with the idLauncher icon in it, but nothing more.
Works fine (even with Flatpak, but needs a tweak)
The game stays black when returning from another application (through Alt-Tab or the Super key in GNOME)
Denuvo Anti-Cheat (DAC)
When using Steam with Flatpak, the game won't start unless you install install the "Proton (community build)" extension as well, and select it in the Proton versions list (see this github issue). In GNOME Software, app extensions can be found on the same app page.
No tweaks, it just works!
You can even crank up the graphics a bit, and the game UI is very nice for that as you can see how much resources each option is going to take. I enabled SSS, SSAO, shadow, bloom, etc. and I get a steady 30 fps (I'd say 40 fps in average).
Everything worked out-of-the-box, just long loading times and an issue when quiting the game.
The loading times are quite long, especially the very first one (shaders?).
Can't quit the game: the game freezes. Needed to kill the game.
Crash at startup
I'm using the Flatpaked Steam on Fedora 34. The game used to work (not without a few bugs), but since recently it just crashes at startup (with an oldish Windows98-like window) and became impossible to play.
I tried with both Wayland and X.org. I'm running Proton 6.3-7 (community build 1633097750).
As for others, I needed to add "PROTON_LOG=1 %command%" in the Launch Options, otherwise I'd get a Javascript error.
I don't know why enabling the Proton logs fixes this issue, but it does!