BlunterCheese9
Published
Saved OK a couple times, but no longer able to save.
I have not debugged yet, but saving via auto-save and exiting the game gives an error popup and requires killing the game. Loading the save that is present works ok.
Game has a minor texture issue when run using the beta 1.08 workaround.
Cutscenes would not play. This is apparently a known issue that affects both Windows and Linux Native versions. Workaround is to run beta 1.8 version, but this introduces a minor but annoying graphical texture issue. See this post on steam forum for more details: https://steamcommunity.com/app/280160/discussions/1/1697175413671233075/.
My testing was done with Linux Native version. Game is still playable.
Proton-5.11-GE-3-MF
Mouse pointer was in incorrect location. This was caused by initial game resolution being completely incorrect. Fix was to set the game resolution to match my monitor.
Last time I played the game on Windows, I had crashes to Desktop all the time. I didn't see a single crash when I played on Linux via Proton. Not sure if this is due to the game being updated since I last played it on Windows, due to Proton / Linux being more stable, or luck.
Game (native Linux version) had visual glitches where were bad enough to make it unplayable. Resolved by disabling the steam overlay.
Cutscene sometimes didn't load. Resolved by restarting the game.
Game would occassionally start lagging. Always happened when a night turned into day and I happened to be home at my base. Workaround is to quit to the main menu and then reload the save.
Game requires Proton Experimental to load. Game has occassional but predictable lagginess that requires a reload (no progress loss.)
Game would not launch with regular Proton. I didn't notice any issues with the game under Proton Experimental.
Playable but a little strenuous reading text.
Appeared that the game was not running at the correct aspect ratio causing the text to be distorted and harder to read.
Setting resolution properly required the workaround mentioned in other posts (manual editing of config file).
Games has good framerate, but has a slight nausea inducing effect.
Requires Proton Experimental for audio to play.
Crashed once the only time I tried a longer than 5 stage run. Appears that the further into a run I get, the more performance and stability issues arise.
Required Proton Experimental to launch. Mostly fine with Proton Experimental. Longer runs may encounter issues.
Previous issue with longer runs resolved in Update 04 "Into the Blue" released October 2024. Still doesn't launch with regular Proton for me. Had an issue once were it didn't launch with Proton Experimental, but worked after trying again.
P.s.: I had DRAM / GPU issues while playing that are unrelated to the game (issues occurred in other games and on desktop.) The game was surprisingly stable even with these hardware issues. I was rather impressed.
Played a few matches against AI without issue.
Was a little finicky controlling / building with the mouse. Might be the game, Proton, or me. But I don't remember the issue when I played on Windows a few years ago.
Runs well
Occasionally has significant frame drops where the screen basically freezes for up to 2 seconds. Usually only happens once in a while (every few hours), and appears to be related to lots of enemies and abilities going off. Might be problematic if playing a hardcore character in a tough situation.
Game was stuttering (to the point of headaches and nausea) when first installed. Required tweaking in game settings and disabling steam overlay (IIRC) to fix. Once fixed ran without any further issue.
Significant frame drops when cycling an airlock while inside. Possibly due to particle effects. No options that I could find in the settings to adjust particle effects. Rest of game was fine with occassional hitches maybe. Unclear if this is a game vs Proton issue.
Game occassionally hung and had to be killed from desktop. As reported by other players, this appears to occur with long playtimes.
Crashed once when starting. And once more in middle of playing (no progress lost, once in ~11 hours of playtime).
Would not launch with regular / default Proton
Max 15 FPS at all graphical settings, including lowest settings
Game would crash on launch with most Proton versions I tried, including default, experimental, and 3 GE versions (including the latest.) Proton version listed in my report is the only one that I tried that worked.
I tried several of the configuration options mentioned in other reports. They did not work for me. Looking at my computer metrics, it appears the issue may be CPU related (since I'm maxing out). But the issue is entirely with FPS.
Proton-6.21-GE-2
A couple lines of dialog didn't play. 99% of the dialog was fine.
Average FPS (per Steam overlay) was 40-55 FPS, with dips to low 30s. Even while idling in the menu. No impact to gameplay, but seemed lower than I would expect. Did not compare against Windows performance.
Seems to work fine
Limited playtime thus far, so small sample size. But launched the game and played through it once to confirm its ok.
Proton-6.21-GE-2
Worked just as well with only 2GiB RAM (I upgraded after finishing the game).
Game crashes during bootup with regular Proton. Beat the game without any issues with Proton Experimental.
Game itself appears to be a little buggy - but is fine
Bugs in a couple campaign missions that are unlikely Proton related.
Game works as well as on Windows, which has FPS issues in some in-game locations.
Appears to be an issue with the game itself based on loads of forum reports. Frame rate drops drastically near cities. FPS is normally 50-60 but drops to ~12 and sometimes even ~2 FPS. I nearly had to stop playing due to nausea.
My monitor's resolution was not listed. Trying to change the resolution / windowing settings causes the game to not display properly and eventually led to the game not launching at all. Fixed by reinstalling the game (and wiping save data off disk and disabling cloud sync) and leaving the resolution as-is.
I was worried going in about technical issues but was able to enjoy the game without any blocking issues.
Game slowed down as rooms are added, students are present, and/or cards are played. Unclear whether this is Proton specific or an issue in the game itself as I don't have Windows to compare it to. Drop was about 20-30 FPS but mitigated by reducing the graphical settings.
- Initial game cutscene plays on load, but stays on black screen. Requires a non-obvious click through to reach the main menu.
- Game does not exit when quitting. Game process still shows in the taskbar, but the game is no longer visible. Requires force quitting (closing it from the taskbar worked fine - command line
kill -9was not required.)
Anecdote: I did not (yet) notice any memory issues while playing that were mentioned in other reports.
Game crashed and appears to have corrupted the save, wasting all the progress on a save slot.
Game crashes to desktop trying to load my save (after the initial crash). Creating a new save to start over seems to work ok. I.e.: game crash appears to be a progression blocker.
Crashed to desktop at the ~100 minute mark. Was well into my best run yet.
I haven't debugged yet to see if other Proton versions will be able to workaround the issue, etc.
Achievements only work with Proton Experimental.
Had a crash with default Proton which appears to have corrupted the save file. Had to restart my playthrough with Proton Experimental. Managed to beat the game on Proton Experimental without any issues.
Originally worked a couple months ago with regular Proton. Later stopped working and was forced to switch to Proton Experimental. Otherwise no issues detected.
Mix of options
Tried both DX12 and DX11
Frame rate drops immediately after building the 2nd or 3rd building. CPU benchmark runs at 3 FPS on default settings. And about 6 FPS on minimal graphics settings.
I tried a variety of proton versions (regular, experimental, GE), launch options (no fsync, no esync, DX, NVAPI), and in game settings (DX11, DX12, vsync on/off, minimal graphics settings.) CPU benchmark always had horrible frame rates. Loading times are rough as well (average being about a minute).
Enter key stops working after alt-tabbing a couple times. Is fixed after starting a new run.
Framerate drops near the end of a run. This is not a Proton issue. The developer is aware of it and per a post on Steam they are working on using a new engine to fix the issue. (Issue is physics is restricted to one CPU.)
As other reports have mentioned, the native Linux version of the game has an issue with some middleware that causes the game to run much slower than its Windows / Proton counterpart. In my case it got to the point where I wasn't getting less than 1 FPS and had to kill the game from my desktop. Proton version worked perfectly fine.
Previously played on Win7. Using similar/same graphics settings, I can't tell the difference between playing on Windows vs on Linux.
5.11-GE-2-MF GloriousEggroll
Used nvida-settings to "Force Composition Pipeline" and/or "Force Full Composition Pipeline." Also had to use nvidia-xconfig to create an Xorg configuration file to save the settings persistently.
This was necessary to fix screen tearing issues. But has the downside of causing the full screen to occasionally not cover the entire screen. But that is resolved by cycling through the fullscreen/window/bordless window options and resaving as fullscreen on launch.
Full screen not fully full resolved by re-selecting fullscreen in the options menu. Only happens intermittently. Appears to be related to nvidia-settings "force (full) composition pipeline" setting.
Trying to view Railjack intrinsics causes the game to freeze. This only started in the last month or two (worked fine before), and thus appears to be related to an update in the game itself.
Proton-5.9-GE-7-ST GloriousEggroll
Installed Proton-5.9-GE-7-ST as per the README instructions on the relevant github project.
Issue with game crashing mentioned in my previous report a year ago (due to the intrinsics screen) was resolved by updating my Nvidia drivers (specifically enabling and installing newer drivers from Debian stable backports.)
Works amazing with DX12 option selected in launcher
Game was stable for a year or so until the Kullervo update (about 3 or so months ago). It was problematic for me since then, in particular: long loading times, stuttering, network lag, crashes, and huge memory usage (~16GB just starting the game up with increases as it goes). After trying DX12 per another report here on ProtonDB, the game is amazingly stable with <8 GB usage. I have limited test time with DX12, but to anyone running into issues, I suggest trying the DX12 option to see if helps. P.s.: special thanks to users Nancy Reagan Throat Goat, Bonafide, and Utherbone for your reports which suggested DX12.
Game difficult to play in late game (~7 hours in)
One time when the game crashed it corrupted the save so that it could not be loaded (the other half dozen times the save was still ok.) The game does have a builtin save backup that I was able to restore from. (Find the game#BACKUP.save in game-specific Proton AppData and overwrite game#.save.)
After ~5 hours into a run (mid to late game), with lots of cards in play, game will sometimes freeze for a few seconds. Usually when something occurs in game and it needs to move a lot of cards around.
Late game (~7 hours into a run), game frequently crashes to desktop. Like every 5-10 minutes of playtime. Game autosaves so only a limited amount of progress is lost. But between the frequent crashes, having to reload the game, and redo some progress, it makes overall game progress 2-3 times slower.
Game occasionally makes a stack of cards "explode" all over the place, requiring player to restack them. Will also some cards (watchtower in my experience) across the board, requiring player to scower the board looking for it.
I find the game fun and want to play more, but given the issues with it currently, it is too frustrating to play.
The game worked really well until mid game, at which point it had annoyances. It is only in late game where it becomes extremely frustrating trying to play. Issue may be related to number of cards in play, extent of automation, etc. So using a different stragety may work. But at that point, game may not be winnable. (Especially since I am in the middle of a major fight and cannot retool my strategy given the time pressure, etc.)
Enjoyable game with some early access bugs
Appears that the game has a memory leak as after an hour or two of playtime my computer's 16GB RAM are all used and it starts swapping. This brings down the game's performance from the usual 60 FPS to about 40 FPS with hitching. Contained by restarting the game when this happens, but unfortunately I typically notice after loading into a new mission.
