mas1701
Published
Works flawlessly OOTB with maybe a crash after long time of non-stop playing
After playing for a long time non-stop (many hours!), the game may suddenly become slow and sluggish and then typically crashes (closes). Maybe a memory overflow bug. Not sure if Linux-related at all, haven't played this on Windows much before switching over to Linux. A simple re-start from last autosave and everything is fine again.
Note: I'm running Linux Mint Cinnamon Edition ("Virgina 21.3" with Edge-/HWE-Kernel), using Pipewire as a PulseAudio drop-in replacement. This has solved some audio problems in the past, related to Wine/Proton gaming.
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.
LOTUS-NG based on Bevy/Rust (Windows .exe) always crashes on start
The small team behind LOTUS has changed the game engine for this Early Access title a second time. First, it was something they've developed themselves. Then they switched to Unity. Now the second switch to Bevy/Rust (because Unity now wants money per installation). Previous releases ran with Steam/Proton quite well, even better than on native Windows, but this new version based on Bevy/Rust won't start at all. Until now, I haven't been able to find a workaround:
- 2024-04-16T19:04:34.610079Z ERROR tracing_panic: A panic occurred panic.payload="called
Result::unwrap()on anErrvalue: Error { code: HRESULT(0x80004001), message: "Not implemented." }" panic.location="C:\Users\Mochida Yuka\.cargo\registry\src\index.crates.io-6f17d22bba15001f\gilrs-core-0.5.11\src\platform\windows_wgi\gamepad.rs:515:67"
Seems to be related to Windows Gaming Input (WGI).
The developers hinted there would be a Linux-native version later, but not right now. A shame, considering Linux seems to be the natural environment for Bevy/Rust projects.
- Note: I tried several proton versions.
I've played for 10+ hours so far. Overall, the game runs very well. Playing in UltraHD (4K). Good frame rates on highest graphical settings.
Cannot see any difference between windowed mode and borderless window.
After playing for several hours (4+), the game may begin to "stutter", meaning micro-freezes. These stutters may also be heared (stuttering game audio). You can just save your game, exit and re-start it, problem gone for the next few hours. Not sure if that is even related to using Linux, I haven't tried the game on Windows yet. And it's Early Access after all.
While you can enjoy this game on Linux, you have to be willing to tinker quite a lot if unlucky.
gamemoderun %command% (optional)
On some systems, including mine, the game may crash again and again and you'll find a message about an audio task problem in the game's crash log. It happens mostly during battle scenes with a lot of sound effects, but may happen in silent scenes as well, just not as often.
If you are experiencing this problem, check your system for the audio system used. Is it Pulseaudio? It seems to have many bugs. Try replacing it with Pipewire. Pipewire can act as a 100% compatible Pulseaudio drop-in replacement. You can find instructions online asking your search engine of choice. In short: Aside from installing Pipewire, you must disable Pulseaudio auto-startup (systemd) and instead enable Pipewire. They can't run both at the same time. Reboot.
For me, replacing Pulseaudio with Pipewire completely solved this issue. Pipewire is included in recent Linux Mint releases, but not used by default.
Sometimes, during the loading screen, the not-really-full-fullscreen gets pushed up a bit off-center. Otherwise, there are very similar black bars below and above the almost-fullscreen game image.
There is an offset when selecting anything with the mouse. Point your mouse cursor slightly below the item you want. Irritating, but otherwise harmless.
Performance is lower than on comparable Windows system. Reduce graphics settings to compensate. Interestingly, this doesn't seam to hurt the game graphics too much, still looks good. However, I know this game for sometimes having unexplainable performance issues on Windows as well. If it gets too bad after playing for a while (hours), save, exit and re-start. It helps for a while.
The game is very unstable if you are playing with reflections higher than "low" in in-game graphics options. "Low" and "off" however work fine.
The game might still occasionally freeze after playing for a while without any error message or chance of recovery. I'd advice to keep a terminal window open so you can do a "killall -9 StrandedSteam.exe" and then re-start with the latest autosave. Keep it on with short intervals!
Thanks to Denuvo DRM (Digital Restrictions Management), do not change the Proton version multiple times per day. Every time you do, Denuvo thinks this is a new installation. Otherwise, you may find yourself locked out for 24 hours. This really s*cks!
I don't know what Frontier Development was thinking when beginning to implement Denuvo into their single-player games. Steam is already providing DRM internally. Also, the development studio, Haemimont, is experienced in creating Linux-native game versions (see: Surviving Mars, originally from Haemimont). So why would Frontier ask them for "Windows only"? So much unneccessary trouble.
