PlayableShow Details
Unknown
weston -Bheadless -Swayland-2 & WAYLAND_DISPLAY=wayland-2 %command%
As the mouse does not mork in cosmoteer if it is launched by default a second wayland compositor needs to be started. This compositor can be headless and needs to be used by setting the WAYLAND_DISPLAY env var. If the main compositor supports XWayland the DISPLAY env var does not need to be set and the game will be displayed as a window in the main compositor without issues.
Works out of the box
Crashed once, but I don't know it if is connected to Linux or Java.
DISPLAY=:1 WAYLAND_DISPLAY=wayland-2 mangohud gamemoderun %command%
Mouse input doesn't function under Hyprland, running it in a nested session (in my case, Wayfire) fixes this.
%command% --cores 12
With proton 9 i no longer need to disable e_sync and f_sync which moderatly boosts performance. Game also stopped crashing every other hour in multiplayer as a client. Still using --cores command to limit wasted CPU usage on very high core count CPUs.
Works great Out-of-The-Box
First savegame started on Linux instead of Windows. Played through the complete beginner star system, then hyper-jumped to the next in row. Completely flawless so far. FPS always at or close to 60 FPS (display limit). Didn't try Multiplayer yet, though. But the list of avaiable MP games loads almost instantlys, so it seems normal.
PROTON_USE_WINED3D=1 PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command% --cores 12
Выскакивают иногда краши, но не могу сказать, что это происходит стабильно.
Crashes very occasionally when I am streaming to discord
The demo did not work at all, but the purchased game works fine.
PROTON_USE_WINED3D=1 PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command% --cores 12
The multithreading in the game has a lock contention problem with high thread counts (24 for me). At high game speeds 1/3 of CPU time is spent waiting for locks. Use --cores a_number_between_6-12 to limit this somewhat.
Rare desync (average every 15 hours), fix: save and rehost. Slowdown after 1h+, fix: rehost, probably a memory leak or heap fragmentation.
Without PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 the game takes twice the CPU (80% for me) at x16 speed instead of 40% for the same framerate and in game performance.
Tested above options (and variants) with Proton 8.0-4, Proton experimental and Proton GE all behave the same.
Crashed occasionally when I tried to load saves mid-game, using older Proton version per developer's recommendation fixed the issue.
Automatic local game discovery does not appear to work correctly - had to manually input local network IP. Maybe it's just my system configuration though.
Game rarely crashes when going back to the start menu or trying to load a save game. Dind't try GE, so maybe that fixes it.
Game sometimes crashes when I try to load a save game, never when saving, so no game time lost.
PROTON_USE_WINED3D=1 gamemoderun %command% --cores 1
~30FPS with DXVK. Solid 144 FPS with WINED3D
Constant desyncs (not proton-specific) and frequent crashes (possibly proton-specific). Not very playable.
No issues after a few hours of playing in singleplayer, works right out of the box.
Slow saving when initially using GE-Proton7-53, went away when moved to GE-Proton8-3
Slow loading when initially using GE-Proton7-53, went away when moved to GE-Proton8-3
Had some disconnects mid game for no reason, most likely not a proton / wine issue and more because the game is early access
update proton
Saves were slow when initially using GE-Proton7-53, switched to GE-Proton8-3 and saves are fast
Game loads slow when initially running GE-Proton7-53 but changing to GE-Proton8-3 solved this issue
Lost connection to host a few times, Don't think this has anything to do with proton / wine
Just make sure you're using the latest GE-Proton
The handling with the Steam Deck is perfect, utilizing all the functionalities except for the gyroscope.
I have been pleasantly surprised by how well the game works and how they have adapted the control for the Steam Deck. The game runs at 60 fps, except when you increase the speed to x4 - x8. However, this is not a problem since it is usually used for traveling or selling/collecting items.
Autosaving as a client takes a minute or longer while multiplayer host and other client on windows saved in seconds.
Disable autosave since the host was saving the game anyways to avoid long delays.
The installation never finished
I try with proton-ge & classique one. And it don't stil don't works.
it block at the end of instation
--cores 1
Nothing works
Runs like native without tweaks
Indistinguishable from a native port
Set Proton to 7.0-5, using GE on this game results in the game taking longer to load and saves taking about a 1-2 minutes to complete.
There are no issues with Proton 7.0-5, works same as native windows, GE causes issues with this game.
Aside from saving the game taking forever the game is perfect, however the constant delays from saving impact the experience greatly.
Manual and autosaves take an unreasonable amount of time on linux compared to windows.
Crash at launch, music plays game window does not update, application unresponsive.
https://steamcommunity.com/app/799600/discussions/4/3732952742343034510/
I'm able to use curl in the Proton wine instance to download a normal webpage, but the application seems to hang while waiting for some network request.
I've tried both Proton 7.0-5 and the latest GE.
It just works
Works out of the box and the dev is also aware of Proton/Wine player!
Just works out of the box now! The developer recently fixed the required command for Proton/Wine users so no more tinkering required.
--cores 1
Sporadic freezing. Irritating in single player, quite annoying in multiplayer (as the freeze lasts long enough to disconnect the session)
The freezing (which also occurs in singleplayer) disconnects the multiplayer session. It's quick enough to save the game, jump back to the menu and rejoin but it's a shame we have to.
Without --cores 1, the game behaved much more poorly. Afterwards, I can get a few hours in without it freezing, but it seems to be fairly luck-of-the-draw.
Starting without %command% --cores 1 the game runs and I could play for a bit, however, after some time it crashes. With there are no issues
%command% --cores 1
When a lot of things are inside the field of view my FPS drop to 10-20. This might also happen independently from Linux as this is still in early access.
Proton 7.0-4
It works great for me without %command% --cores 1 and with froced Proton 7.0-4.
Won't start even with %command% --cores 1.
It actually ran once or twice without any problems (exept it crashed once), but now it just won't start...
--cores 1
Es startet, man kommt ins Spiel, aber dann friert es ein und man muss es schließen. Ein Spielen ist also quasi nicht möglich.
It crash after the loading screen, before the splash screen
%command% --cores 1
it don't works
Adding --cores 1 to the launch parameter, possibly combined with --noplanets, fixes the only Proton-specific glitch I have experienced.
--noplanets --cores 1
Issues which arose are shared with the Windows version of the game, such as multiplayer desyncs and host lag. Proton 7.0 with the launch parameters previously mentioned had no additional problems thus far.
The game works just as well through Steam Proton on Linux as it does on Windows, with the potential caveat that setting the total processor cores to 1 may cause performance losses (I have not personally experienced any, and it is possible the game only has limited multithreading in the first place).
--cores 1
Needs the cores option to avoid crashing it seems
%command% --cores 1
Be sure to set the launch option! Otherwise the game will freeze after a while (usually between 5-15 min)
