Closed Popax21 closed 2 years ago
NOTES
Linux is not supported for FIN because SF doesnt even support it, and mods for dedicated servers are also not supported
With "on Linux" I mean using Proton/Wine.
I know... Proton/Wine != Windows Runtime Sry I simply dont have any time to even think about supporting Linux feel free to create a PR tho
Ah OK, as it seems to be related to SymLoadModuleExW
(as this fails right before crashing), I'm gonna try to look into possible issues regarding that.
Also note that it worked perfectly before Update 5, so it isn't an inherit Proton issue.
It gets weirder: if I launch the game with pure wine, everything works flawlessly, however if I run it with Proton it crashes.
I figured it out: a wine version somewhere between version 6.19 (my system's) and 6.3 (first broken proton one) introduces a bug somewhere related to SymLoadModuleExW
(am still investigating this) which causes it to fail and Satisfactory to subsequently crash. One workaround is to downgrade to a proton version before or at version 6.19.
TLDR Force Satisfactory to use Proton version 5.13-6
for now
As a note for future people: this can also be resolved by adding -d3d11 as a launch option.
Adding -d3d11
didn't help for me, but disabling some mods did. It still crashes sometimes, but it's stable once you get in-game. I noticed when it fails, the memory usage is 3.6GB just before crash, but when it loads OK, it's 3.0GB at the menu. I wonder if some 32-bit limit is to blame? (It does go over 5GB in-game though)
Game version is the current Early Access branch (CL176027, SML v3.3.0), OS is Arch Linux. This happens with the latest version installed via SMM,
development
profile. Interestingly, if I manually install the latest version from SMR, it doesn't crash anymore, however it then crashes when starting a new game.Crash log for the SMM setup:
Crash log for the manual install setup: