Unknown
(none)
Haven't noticed any bugs that weren't already in the windows version
No issues, game plays like native on Windows
If game doesnt load press 'Esc' without selecting window
Works out of the box. Runs just as well as it did on Windows. Potentially a bit slower loading times on larger maps but could be imagined
Very occasionally crashed at the end of a game.
Runs beautifully without any tinkering, with performance on par with the Windows 10 experience I had on the very same hardware.
gamemoderun %command%
I did not try multiplayer.
Played one long battle in the campaign with no problems. Proton 6.3-8
Previously I was not able to run the game. The cause of this was because the game was installed on a NTFS partition. Moving the game to an ext4 partition solved my problems. ( I found out that Proton do not work well with games installed on NTFS partitions).
When pressing play, nothing happens.
Proton 6.3-8
It is playable on Singleplayer and small team games 2v2s and 4v4s. But it's not very enjoyable..
Caused major slowdowns and takes 5 seconds to reload into game.
You cannot play 10v10s to the finish. It often crashes before I can complete a game. I believe the engine is overloaded.
Can't pass past the launcher
The launcher starts, but after clicking to start the game, the launcher becomes a bit transparent and hangs. The game seems to be running, but invisible, in the sense that I can't click on anything in the screen, unless, I press alt tab to change to another app. After several changes between apps, you are able to see the "screen" of the game, but it is just a mess of green squares. I tried with proton version 5.0, 5.13, 6.3 and experimental, all with and without the lancher option taskset -c 0 %command% (as seen in another comments), but not dice, it is always pretty much the same issue
need taskset -ca 0 %command% in the launch setting and proton 5.0, I tried with proton 5.13, but I had always a crash when i loaded a game. I tried in medium and high setting with 35-40 fps, not really good with a 1070, but that work. the multiplayer work, I didn't have any problems, just think to open 21000/tcp, 23000:24000/tcp and 23000:24000/udp. I had only one crash it's when I started the game with the logo of Eugen Systems, but no problems when i restarted the game
Running with a single core is needed to avoid crashing on loading screens. However, it makes large multiplayer matches lag out and can lead to you getting kicked automatically for lag.
However, to workaround this you can reenable cores during play by running taskset -p -a 0xffff $(pgrep SteelDivision2) from another terminal. Disable them again with taskset -p -ca 0 $(pgrep SteelDivision2) to make loading work again once you're done. Alternately you can restart the game.
Cutscenes will often crash the game, even with only a single core active. Mash <ESC> and pray to get through these.
Really needs taskset -ca 0 %command% in the launch options. I tested on a few different proton versions and it appears to work the best on proton 5.0, so I would recommend forcing that version. In newer versions of proton taskset appears to do nothing.
Have to run with a single core, which is really too little to run big multiplayer matches
If running without taskset -c 0 %command% or with proton 5.0 there are frequent crashes.
games needs taskset -c 0 %command% as it heas deadlock multithreaded bug
Unable to play, stuck in loading screen
Since Fate of Finland DLC (march 2020), unable to play anymore. Before that, the game freeze sometimes but was playable. Now, I'm simply unable to launch a game at all. Tried with Pop!_OS and Manjaro KDE.
Crashes, hanging and audio cutting out are too problematic to recommend playing this game with Proton.
Cuts out after a while of playing skirmish
Crashes randomly (due to deadlocks) at loading screens, including launching and exiting the game.
After a while of playing skirmish you can no longer use the menu, including saving your game. Even if you reach a win or loss, you can't then end/exit the match. At that point the game is essentially hung.
crash when loading game
I tried in windowed mode, and full screen, all settings in low, but always when I want start a game, the loading screen is here, but no loading (i waited 10-15 min) but nothing, i must kill the process because ALT-TAB don't work.
Game *is* playable but stability issues result in needing to restart it multiple times.
Would randomly crash or freeze up in loading menus, couldn't launch some game modes.
Unable to use any game mode other than skirmish, tried with multiple versions of proton up to 5.05
Every startup asks me to load the last good config since it can't close properly. If I click yes, it freezes on launch, if I click no or close the window I can atleast get into the game.
The foliage glitch is really annoying but is still playable, but the deadlocking is a show-stopper.
Tree foliage textures missing with Vulkan. With OpenGL the terrain is invisible.
It ground to almost a halt when zooming down to ground level. That didn't happen on windows, and is possibly related to the foliage texture glitch.
The game hangs (due to a thread deadlock) often, usually when launching or exiting the game, or during loading screens.
after ~20 Minutes audio output stops completely
in 70% of the time, after a skirmish against the AI in single player the game speed just pauses. No "Won" Overlay is displayed. Pressing ESC shows the menu. Once "Surrender" is pressed nothing happens. Once agein pressing ESC displays just "Continue","Options" and "Exit". After pressing "Exit" the menu just disappears and nothing else happens. The only way to Exit the Game is by killing the Process.
Tried again with Proton 4.11-8, full screen and played 3-4 times more than 45 minutes without anymore issue regarding cursor. No more disappearing.
Still disappearing cursor issue when played full screen. Cursor is still here but invisible! Tweak is to play it windowed. Also, intro videos tend to freeze the game. Tweak is to hit ESC key as soon as video starts. Other than that, game runs smoothly.
Unknown(2+ hours with Proton)Works perfectly when run in windowed mode to avoid the disappearing cursor bug.
Unknown(2+ hours with Proton)Run without problem with Proton 3.16-4. I have observe the cursor becoming invisible (but still working) only with Proton 4.2-5. Steel Division 2 Beta v20403
