Satisfactory

Satisfactory

View Stats:
[Linux] Game (and PC) Freezing all of the sudden...
Hi,

are there also some other Linux (or maybe also Windows) users who have issues just since today with the game randomly freezing? It can get so far that also the PC itself will get stuck so that I have to hard power reset the computer.

I played since the release of 1.0 and everything was pretty stable till today...
Also Pre-1.0 I never had that issue...

It seems to happen mostly while moving or jumping... (at leats I did not had it yet while standing still)

I know that Linux is not officially supported that's why I did not create a Ticket on the Q&A Site... Or should I anyway?
< >
Showing 1-15 of 37 comments
Rena Sep 22, 2024 @ 10:34am 
If you're using nVidia: that's normal.
If you're using closed source drivers: that's probably the reason.
Otherwise: probably a hardware problem. The game shouldn't be able to crash the entire system.
DarklinkFighter Sep 22, 2024 @ 10:43am 
Yes I have a Nvidia GTX 1080.
But I never had issues with the game...
The problem realy started today. But maybe it is also save file related somehow?
Last edited by DarklinkFighter; Sep 22, 2024 @ 10:44am
cswiger Sep 22, 2024 @ 11:08am 
If you have to power-cycle or reset your machine, you have a hardware problem. Likely causes are insufficient cooling or a marginal PSU which cannot handle full load.

Do diagnostics followed by an appropriate stress test to confirm.
Bedna Sep 22, 2024 @ 11:39am 
Originally posted by Rena:
If you're using nVidia: that's normal.
If you're using closed source drivers: that's probably the reason.
Otherwise: probably a hardware problem. The game shouldn't be able to crash the entire system.

A complete lie. Arguably the proprietary nvidia drivers are even better than the radeon (open source) gpu drivers for amd.
This is just an old sentement that "if you use linux you SHOULD dislike and blame nvidia for everything" (even though nvidia is one of the biggest contributors of code to the linux kernel). Don't listen to ppl that claims such things.

Originally posted by DarklinkFighter:
Yes I have a Nvidia GTX 1080.
But I never had issues with the game...
The problem realy started today. But maybe it is also save file related somehow?

What distro and desktop environment?
Since it started after 1.0, my wild guess is it's something with memory or cache. (or maybe I misunderstood it started with 1.0, and it just randomly started?)

What does dmesg log?
journalctl?
Did your fans run like crazy so it might be a temperature thing?
Did you try other proton versions?

Without further information it is impossible to know.

You can also start steam with gdb as debugger to get a nice logfile to read.
Last edited by Bedna; Sep 22, 2024 @ 11:48am
Same problem and GPU. Didn't have the problem before but ran the game without a server. Now that it is 1.0 and I run the server in the terminal.


Originally posted by Bedna:
If you're
What distro and desktop environment?
Since it started after 1.0, my wild guess is it's something with memory or cache. (or maybe I misunderstood it started with 1.0, and it just randomly started?)

Start with 1.0 but also started hosting server in terminal then.

NVIDIA 550.107.02 Driver Version: 550.107.02 CUDA Version: 12.4 Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.1.106-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C91 System Version: 2.0



Originally posted by Bedna:
What does dmesg log?


[ 13.850727] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 13.853213] Bridge firewalling registered [ 1854.325384] TCP: request_sock_TCP: Possible SYN flooding on port 16587. Sending cookies. Check SNMP counters. [ 2383.534632] NVRM: GPU at PCI:0000:2b:00: GPU-9838f634-fb73-afc6-c254-070ee763ff3a [ 2383.534641] NVRM: Xid (PCI:0000:2b:00): 32, pid='<unknown>', name=<unknown>, Channel ID 000000c7 intr 00040000


Originally posted by Bedna:
journalctl?

session-18.scope: Deactivated successfully. Sep 22 19:20:06 user-ryzen systemd[1]: session-18.scope: Consumed 382ms CPU time, 65.3M memory peak. Sep 22 19:21:12 user-ryzen systemd[1]: Starting Time & Date Service... Sep 22 19:21:12 user-ryzen systemd[1]: Started Time & Date Service. Sep 22 19:21:42 user-ryzen systemd[1]: systemd-timedated.service: Deactivated successfully. Sep 22 19:23:44 user-ryzen kernel: NVRM: GPU at PCI:0000:2b:00: GPU-9838f634-fb73-afc6-c254-070ee763ff3a Sep 22 19:23:44 user-ryzen kernel: NVRM: Xid (PCI:0000:2b:00): 32, pid='<unknown>', name=<unknown>, Channel ID 000000c7 intr 00040000 Sep 22 19:24:00 user-ryzen kwin_x11[5492]: kwin_core: XCB error: 152 (BadDamage), sequence: 12211, resource id: 21092439, major code: 143 (DAMAGE), minor code: 3 (Subtract) Sep 22 19:24:07 user-ryzen systemd[3820]: Started System Monitor - System Monitor. Sep 22 19:24:09 user-ryzen systemd[3820]: Starting Track hardware statistics... Sep 22 19:24:09 user-ryzen ksystemstats[96340]: Loaded plugin "ksystemstats_plugin_lmsensors" from file "/usr/lib/qt6/plugins/ksystemstats/ksystemstats_plugin_lmsensors.so" Sep 22 19:24:09 user-ryzen ksystemstats[96340]: Loaded plugin "ksystemstats_plugin_network" from file "/usr/lib/qt6/plugins/ksystemstats/ksystemstats_plugin_network.so" Sep 22 19:24:09 user-ryzen ksystemstats[96340]: Loaded plugin "ksystemstats_plugin_memory" from file "/usr/lib/qt6/plugins/ksystemstats/ksystemstats_plugin_memory.so" Sep 22 19:24:09 user-ryzen ksystemstats[96340]: Loaded plugin "ksystemstats_plugin_cpu" from file "/usr/lib/qt6/plugins/ksystemstats/ksystemstats_plugin_cpu.so" Sep 22 19:24:09 user-ryzen NetworkManager[880]: <info> [1727047449.7798] audit: op="statistics" interface="enp36s0" ifindex=2 args="500" pid=96340 uid=1000 result="success" Sep 22 19:24:09 user-ryzen NetworkManager[880]: <info> [1727047449.7849] audit: op="statistics" interface="enp42s0" ifindex=3 args="500" pid=96340 uid=1000 result="success" Sep 22 19:24:09 user-ryzen ksystemstats[96340]: Loaded plugin "ksystemstats_plugin_disk" from file "/usr/lib/qt6/plugins/ksystemstats/ksystemstats_plugin_disk.so" Sep 22 19:24:09 user-ryzen ksystemstats[96340]: Loaded plugin "ksystemstats_plugin_gpu" from file "/usr/lib/qt6/plugins/ksystemstats/ksystemstats_plugin_gpu.so" Sep 22 19:24:09 user-ryzen ksystemstats[96340]: Loaded plugin "ksystemstats_plugin_power" from file "/usr/lib/qt6/plugins/ksystemstats/ksystemstats_plugin_power.so" Sep 22 19:24:09 user-ryzen ksystemstats[96340]: Loaded plugin "ksystemstats_plugin_osinfo" from file "/usr/lib/qt6/plugins/ksystemstats/ksystemstats_plugin_osinfo.so" Sep 22 19:24:09 user-ryzen systemd[3820]: Started Track hardware statistics. Sep 22 19:24:09 user-ryzen systemd[1]: Starting Hostname Service... Sep 22 19:24:09 user-ryzen plasma-systemmonitor[96086]: qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "calculatedImplic> Sep 22 19:24:09 user-ryzen plasma-systemmonitor[96086]: qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:401:33: QML Binding: Binding loop detected for property "value" Sep 22 19:24:09 user-ryzen plasma-systemmonitor[96086]: qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:401:33: QML Binding: Binding loop detected for property "target" Sep 22 19:24:09 user-ryzen NetworkManager[880]: <info> [1727047449.9487] audit: op="statistics" interface="enp42s0" ifindex=3 args="500" pid=96340 uid=1000 result="success" Sep 22 19:24:09 user-ryzen systemd[1]: Started Hostname Service. Sep 22 19:24:14 user-ryzen FactoryServer-Linux-Shipping[11185]: LogNet: Error: UEngine::BroadcastNetworkFailure: FailureType = ConnectionTimeout, ErrorString = UNetConnection::Tick> Sep 22 19:24:14 user-ryzen FactoryServer-Linux-Shipping[11185]: LogGame: Error: Network Error Recived: Type: ConnectionTimeout, MSG: UNetConnection::Tick: Connection TIMED OUT. Clo> Sep 22 19:24:16 user-ryzen plasma-systemmonitor[96086]: qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "implicitHeight" Sep 22 19:24:16 user-ryzen plasma-systemmonitor[96086]: qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "calculatedImplic> Sep 22 19:24:16 user-ryzen plasma-systemmonitor[96086]: qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:401:33: QML Binding: Binding loop detected for property "value" Sep 22 19:24:16 user-ryzen plasma-systemmonitor[96086]: qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:401:33: QML Binding: Binding loop detected for property "target" Sep 22 19:24:30 user-ryzen plasma-systemmonitor[96086]: qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "implicitHeight" Sep 22 19:24:40 user-ryzen systemd[1]: systemd-hostnamed.service: Deactivated successfully.

Originally posted by Bedna:
Did your fans run like crazy so it might be a temperature thing?

So my GPU probably needs to be cleaned but this started with 1.0.

Originally posted by Bedna:
Did you try other proton versions?

Just the default version on Steam. Might try some GloriousEggroll?

Originally posted by Bedna:

Without further information it is impossible to know.

You can also start steam with gdb as debugger to get a nice logfile to read.

How about just the Proton log, a lot easier to get!
Last edited by cyb3rkn19ht [CSPK]; Sep 22, 2024 @ 4:47pm
Better log example:

Sep 22 20:01:00 user-ryzen CROND[204518]: (root) CMDEND (run-parts /etc/cron.hourly) Sep 22 20:01:01 user-ryzen kdeconnectd[5683]: 2024-09-22T20:01:01 kdeconnect.plugin.sendnotifications: Unimplemented conversation of type 'r' 114 Sep 22 20:01:03 user-ryzen kdeconnectd[5683]: 2024-09-22T20:01:03 kdeconnect.plugin.sendnotifications: Unimplemented conversation of type 'r' 114 Sep 22 20:01:18 user-ryzen kdeconnectd[5683]: 2024-09-22T20:01:18 kdeconnect.plugin.sendnotifications: Unimplemented conversation of type 'r' 114 Sep 22 20:03:30 user-ryzen kernel: NVRM: Xid (PCI:0000:2b:00): 32, pid='<unknown>', name=<unknown>, Channel ID 000000c7 intr 00040000 Sep 22 20:03:38 user-ryzen kwin_x11[5492]: kwin_core: XCB error: 152 (BadDamage), sequence: 58007, resource id: 21317643, major code: 143 (DAMAGE), minor code: 3 (Subtract) Sep 22 20:04:00 user-ryzen FactoryServer-Linux-Shipping[11185]: LogNet: Error: UEngine::BroadcastNetworkFailure: FailureType = ConnectionTimeout, ErrorString = UNetConnection::Tick: Connection TIMED OUT. Closing connection.. Elapsed: 30.02, Real: 30.03, Good: 30.03, DriverTime: 4457.32, Threshold: 30.00, [UNetConnection] RemoteAddr: 127.0.0.1:52846, Name: IpConnection_2147447803, Driver: GameNetDriver FGDSIpNetDriver_2147482258, IsServer: YES, PC: BP_PlayerController_C_2147447794, Owner: BP_PlayerController_C_2147447794, UniqueId: Steam:3 (ForeignId=[Type=6 Handle=2 RepData=[67B3CC0301001001]), Driver = GameNetDriver FGDSIpNetDriver_2147482258 Sep 22 20:04:00 user-ryzen FactoryServer-Linux-Shipping[11185]: LogGame: Error: Network Error Recived: Type: ConnectionTimeout, MSG: UNetConnection::Tick: Connection TIMED OUT. Closing connection.. Elapsed: 30.02, Real: 30.03, Good: 30.03, DriverTime: 4457.32, Threshold: 30.00, [UNetConnection] RemoteAddr: 127.0.0.1:52846, Name: IpConnection_2147447803, Driver: GameNetDriver FGDSIpNetDriver_2147482258, IsServer: YES, PC: BP_PlayerController_C_2147447794, Owner: BP_PlayerController_C_2147447794, UniqueId: Steam:3 (ForeignId=[Type=6 Handle=2 RepData=[67B3CC0301001001])
Dark Sceptor Sep 22, 2024 @ 5:14pm 
Originally posted by Bedna:
Originally posted by Rena:

(even though nvidia is one of the biggest contributors of code to the linux kernel). Don't listen to ppl that claims such things.

Hmmm...is that why Linus told NVidia to ♥♥♥♥ off???
infiniteteatime Sep 22, 2024 @ 5:37pm 
I had the same issue which was fixed by updating the drivers for my 1070 Ti. I was on 530 server and upgrading to 550 fixed everything. Now I can play for so long I forget that I have homework to do. Win-win really. :crtcool:
Ghost Sep 22, 2024 @ 5:45pm 
switch the api, directx to vulkan
If it's anything like mine was turn all the conveyor settings down to the minimum. There are three of them and that stopped the issue. No need to run DX11 or Vulkan unless you really want to. Switching to Vulkan forced DX11 instead and then all the shadows were super dark.
Driver update did nothing for me either honestly. Was also a fresh install of Steam and Satisfactory as I am just starting to make the switch.

Asrock X470 Fat1lity
Ryzen 5800X
32GB Gskill DDR4 3200
EVGA Gtx 1080 ti
Mellanox ConnextX2 10G NIC
Ubuntu Cinnamon 24.04
Bedna Sep 22, 2024 @ 6:28pm 
Oh crap, it's 3am here, but I can take quick glance...

Originally posted by cyb3rkn19ht CSPK:
Same problem and GPU. Didn't have the problem before but ran the game without a server. Now that it is 1.0 and I run the server in the terminal.

Does it work if you do not run the server? Ie just start a game?

Originally posted by cyb3rkn19ht CSPK:
NVIDIA 550.107.02 Driver Version: 550.107.02 CUDA Version: 12.4 Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.1.106-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C91 System Version: 2.0

You seem to be up to date with nvidia drivers for manjaro stable, and you are on the LTS kernel, nothing strange there.
But might I ask why you are using x11 with plasma 6?
Wayland works really well, even with nvidia. xD
I have both as well, but last time I logged in using x11 like a month or so ago, it felt like a proper regression. Try wayland, that might actually help.

Originally posted by cyb3rkn19ht CSPK:
Originally posted by Bedna:
journalctl?

<snip> Sep 22 19:23:44 user-ryzen kernel: NVRM: GPU at PCI:0000:2b:00: GPU-9838f634-fb73-afc6-c254-070ee763ff3a Sep 22 19:23:44 user-ryzen kernel: NVRM: Xid (PCI:0000:2b:00): 32, pid='<unknown>', name=<unknown>, Channel ID 000000c7 intr 00040000 Sep 22 19:24:00 user-ryzen kwin_x11[5492]: kwin_core: XCB error: 152 (BadDamage), sequence: 12211, resource id: 21092439, major code: 143 (DAMAGE), minor code: 3 (Subtract) <snip>

I assume you have double checked that that pci IS your nvidia, and not your iGPU on your cpu?
And again, x11 error... Try Wayland.

Originally posted by cyb3rkn19ht CSPK:
Originally posted by Bedna:
Did you try other proton versions?

Just the default version on Steam. Might try some GloriousEggroll?

Make that your default proton, it is just way better with tons of tiny tweaks for a whole range of games.
You can use pamac and get proton-ge-custom-bin from the AUR.
IIRC you can build it with:
pamac build proton-ge-custom-bin

Select it in steam and that's it.

Originally posted by cyb3rkn19ht CSPK:
Originally posted by Bedna:

Without further information it is impossible to know.

You can also start steam with gdb as debugger to get a nice logfile to read.

How about just the Proton log, a lot easier to get!

I am starting to think this has less to do with proton and more with some general system thing...
Last edited by Bedna; Sep 22, 2024 @ 6:35pm
Thanks for all the help, Wayland, will try conveyor, and Proton GE!

Edit: Using -vulkan worked!

Vulkan defaults to DX11 (Forced) for me as well. Got the game back into DX12 and turned down the conveyor settings.

Wayland for Plasma still crashes for me. I think it is due to my older GPU (1080) or something I changed trying to get it working earlier.

Right now it is late, will try fixes and tests later this week.
Last edited by cyb3rkn19ht [CSPK]; Oct 27, 2024 @ 9:51pm
Man's Best Friend Sep 22, 2024 @ 8:35pm 
Originally posted by cyb3rkn19ht CSPK:
Thanks for all the help, will try conveyor, and Proton GE!

Vulkan defaults to DX11 (Forced) for me as well.

Wayland still crashes for me :( Got the game back into DX12 and turned down the conveyor settings.

Right now it is late, will try fixes and tests later this week.
I'm about 99% sure the "DX11 (forced)" after picking Vulkan is just a menu bug since MangoHUD reports that the game is in fact using straight Vulkan in spite of what the menu says. If I attempt to force DX11 like it claims it already is, MangoHUD reports that it's using something like DXVK instead (and all my graphics settings automatically get set to low).

But as for the game having issues? None here. Official Nvidia drivers and all. I'm even using the drivers direct from Nvidia instead of from my distro's repository, which if the comments I've seen are to be believed should have set my computer on fire and shot my dog. I'm running Debian with an RTX 3070 on driver version 550.107.02. Not using Wayland as that doesn't seem to work. Xorg does though. Proton Experimental.
Bedna Sep 22, 2024 @ 10:23pm 
Originally posted by Man's Best Friend:
I'm about 99% sure the "DX11 (forced)" after picking Vulkan is just a menu bug since MangoHUD reports that the game is in fact using straight Vulkan in spite of what the menu says. If I attempt to force DX11 like it claims it already is, MangoHUD reports that it's using something like DXVK instead (and all my graphics settings automatically get set to low).

But as for the game having issues? None here. Official Nvidia drivers and all. I'm even using the drivers direct from Nvidia instead of from my distro's repository, which if the comments I've seen are to be believed should have set my computer on fire and shot my dog. I'm running Debian with an RTX 3070 on driver version 550.107.02. Not using Wayland as that doesn't seem to work. Xorg does though. Proton Experimental.

Naa, it wont set anything on fire, but you will have an extremely unnecessary lot of extra work to do when you update, or rather, remove the old and install new.
You REALLY have to make sure you remove every single little file where the install script put stuff. IIRC there is a uninstall.sh script you can use, but I have also heard it is not 100% foolproof, witch is why even nvidia recommends the user using a maintainers script for the distro you are using instead.
They even have a warning text about it on the nividia download website now, did you miss that? xD
You really should use tools that exist, and if your distro has a tool to install the drivers, you really should use it.

And you are probably running vkd3d with the -dx11 option, not dxvk...

Originally posted by cyb3rkn19ht CSPK:
Wayland for Plasma still crashes for me. I think it is due to my older GPU (1080) or something I changed trying to get it working earlier.

Right now it is late, will try fixes and tests later this week.

There you have it. If you fix that you should be able to use dx instead of vulcan (if you care about that kind of stuff).
Kinda confusing if it works with vulkan instead of dx as api, because it is all being translated by proton anyway and should not have an impact on weather it runs or not.
But then again, gremlins... And sometimes it's just better to "take the win" than growing old from trying to figure things out 100%...

But you should use proton-GE, there is no question about that.
Last edited by Bedna; Sep 22, 2024 @ 10:39pm
GI Ged Sep 22, 2024 @ 11:11pm 
The crashes are related to the 4K monitor resolution, i had crashes to, tried every Proton, dx11, dx12, vulkan.
Repaired Linux Ubuntu 24.04 ( press shift at startup )
repaired Steam ( terminal steam -repair )
verified Satisfactory files
my desktop was set to 4K, i set SF to 1920x1080 and than to 4K
sometimes i cant get into main menue, other times it crashed open a save.
if i got lucky i can play for 4 -6 hours until it crashed again

now i set my desktop to 1920x1080 and SF too, with vulkan and ultra settings (150-200 fps)
no crashes but when i end the game via exit to desktop ive got this error:
https://www.gamers-in.de/pics/SFerror.jpg
it can be avoided if you first go to the main menue and stop the game from the
steam library.

ASUSTeK COMPUTER INC. ROG STRIX X570-F GAMING
G-Skill 2x 16,0 GiB 4000 MHz
AMD Ryzen™ 7 5800X3D × 16
NVIDIA GeForce RTX™ 4060 4.6.0 NVIDIA 535.183.01
Samsung U28E590D 4k Monitor
Samsung 980 NVME 1 TB

## Software-Informationen:
- **Firmware-Version:** 4802
- **Name des Betriebssystems:** Ubuntu 24.04.1 LTS
- **Betriebssystem-Typ:** 64-bit
- **GNOME-Version:** 46
- **Fenstermanager:** X11
- **Kernel-Version:** Linux 6.8.0-45-generic
Last edited by GI Ged; Sep 22, 2024 @ 11:19pm
< >
Showing 1-15 of 37 comments
Per page: 1530 50

Date Posted: Sep 22, 2024 @ 10:25am
Posts: 37