I can confirm this issue. Looking at wireshark it appears to be having issues with Epic Online Service's STUN service (possibly):

My NAT was set to "Moderate" in-game.

steam-526870.log

My steam log, nothing too useful in there I am afraid. Is there a way I can more effectively diagnose network settings, or get wine / proton to use a specific network interface to help diagnose this a bit better?

Tested with Proton 5.0-9 and 4.11-13. Tested the Epic Games version through Proton as well, which used to work in multiplayer. Same issue across the board on two different Ubuntu 18.04.4 boxes. Whatever they did upto the Steam release broke multiplayer under Proton.

When you were testing the steam version, did you also do the steam connection to EOS instead of the steam to epic account linking?

I wonder if the steam to epic account link would work better in case there is something being lost in translation between steam proton and the epic online service communication framework.

But this would be difficult to test because I would need to open a ticket with the satisfactory in manually adjust my account.

When you were testing the steam version, did you also do the steam connection to EOS instead of the steam to epic account linking?

I chose the option on the right, linking both accounts so I can see both Epic and Steam friends online in-game.

Can confirm, the exact same error in wireshark with STUN and epic

I get the same error message, but only if the target server/session is running inside Proton as well. If I connect from my Proton client to a Satisfactory session running on windows, it works.

I get the same error message, but only if the target server/session is running inside Proton as well. If I connect from my Proton client to a Satisfactory session running on windows, it works.

Could you do a network trace of a working join and compare it with one that failed?

@JackTemaki in the case in which it works vs doesnt, does the account change? Like does the host that work not have an account linked to epic and the host that doesnt work have its account linked to epic?

I am also experiencing this, my (linux) account is not linked to an epic account, but the host (windows) account is

I've tried with and without being logged into an Epic account (on the steam version of the game) and neither seem to work. Will post network trace comparison shortly.

Game log files, joining the same session on Windows (VM) successfully vs Proton unsuccessfully. These files can be produced by turning up network logging verbosity by appending the following lines to Saved/Config/WindowsNoEditor/Game.ini:

[Core.Log]
LogOnline=All
LogOnlineGame=All

proton.txt
windows.txt

You can specify the location of your log file by adding LOG=[your-log-file-name].txt to your launch options, and it will create it relative to Saved/Logs.

@JackTemaki in the case in which it works vs doesnt, does the account change? Like does the host that work not have an account linked to epic and the host that doesnt work have its account linked to epic?

No, in both cases we did not link to an (explicit, only the interal dummy) epic account, on neither the server nor the client side.

I had the same problem. It seems to be somehow related to the fact that there are multiple network interfaces. When I remove all network interfaces except the one used for connecting to the internet, multiplayer works.

@steffen-kiess Can you provide more details on how to perform this workaround?

There seems to be no request under the proton with CreatePermission
Windows:

Proton:

I had the same problem. It seems to be somehow related to the fact that there are multiple network interfaces. When I remove all network interfaces except the one used for connecting to the internet, multiplayer works.

Thanks for this observation, I'll try this out.

When I remove all network interfaces except the one used for connecting to the internet, multiplayer works

This is not desirable considering that many here would use some form or another of VM (virtualbox, VMWare, etc). So removing network interfaces is a major pain in the you know where.

What would be desirable is an environment var to force an interface to be used only.

Would it be possible to run a command prior to FactoryGame.exe that sets the primary interface as shown in this forum post? https://forum.winehq.org/viewtopic.php?p=1363#p1363

Edit: Never mind, that's using the linux route command!

My friend and I have been troubleshooting this on and off for two days. Try this command in linux:

sudo virsh net-destroy default

He did that, and i was able to connect to his game instantly.

He did that, and i was able to connect to his game instantly.

I have docker installed and a virsh interface for my Windows VM, I am guessing I'd need to remove all of these to test.

To be honest with you I have no idea

He did that, and i was able to connect to his game instantly.

I have docker installed and a virsh interface for my Windows VM, I am guessing I'd need to remove all of these to test.

To be honest with you I have no idea. We just started another session and I was able to connect again.

I am going to test shutting all of my interfaces and connecting to a game. likely wont be able to get to it for a couple hours however.

I am going to test shutting all of my interfaces and connecting to a game. likely wont be able to get to it for a couple hours however.

Using the method I recommended, it worked perfectly as soon as we ran the command. It appears the code is forcing use of a virtual network interface as the default. If you destroy it, all is well. The command my friend used is in my initial post

I am going to test shutting all of my interfaces and connecting to a game. likely wont be able to get to it for a couple hours however.

Using the method I recommended, it worked perfectly as soon as we ran the command. It appears the code is forcing use of a virtual network interface as the default. If you destroy it, all is well. The command my friend used is in my initial post

The virtual network interfaces (Hamachi in this particular case) were also the issue for us, after removing them everything worked fine.

For VMware, as root;

vmware-networks --stop.
You can later re-enable with vmware-networks --start

This is still not a proper solution - there still needs to be a way for wine/proton to force bind to a network interface.

Disabling network interfaces is lipstick on a pig.

@steffen-kiess Can you provide more details on how to perform this workaround?

You can list the interfaces with ip a and then use e.g. ip link set dev virbr0 down to disable the interface virbr0. (You can use ip link set dev virbr0 up to enable it again.) You probably should disable every interface which is listed as UP and has an IPv4 address except lo and the interface you need for network access.

I need my other interfaces, unfortunately. No wine trickery possible to get around this?

I need my other interfaces, unfortunately. No wine trickery possible to get around this?

You can use namespaces to launch Steam with a single network interface. Change IP_SUBNET if you already have the same and USER_NAME_TO_RUN_STEAM. Check net.ipv4.ip_forward, if you don't need to change it.
Script example:

#!/bin/bash

USER_NAME_TO_RUN_STEAM="YourUser"
IP_SUBNET="10.10.10"

sudo ip netns add steam_ns
sudo ip netns exec steam_ns ip addr add 127.0.0.1/8 dev lo
sudo ip netns exec steam_ns ip link set lo up
sudo ip link add steam_ns0 type veth peer name steam_ns1
sudo ip link set steam_ns0 up
sudo ip link set steam_ns1 netns steam_ns up
sudo ip addr add $IP_SUBNET.1/24 dev steam_ns0
sudo ip netns exec steam_ns ip addr add $IP_SUBNET.2/24 dev steam_ns1
sudo ip netns exec steam_ns ip route add default via $IP_SUBNET.1 dev steam_ns1
sudo iptables -A INPUT ! -i steam_ns0 -s $IP_SUBNET.0/24 -j DROP
sudo iptables -t nat -A POSTROUTING -s $IP_SUBNET.0/24 -o en+ -j MASQUERADE
sudo sysctl -q net.ipv4.ip_forward=1
sudo mkdir -p /etc/netns/steam_ns
echo "nameserver 8.8.8.8" | sudo tee /etc/netns/steam_ns/resolv.conf

sudo ip netns exec steam_ns su - $USER_NAME_TO_RUN_STEAM -c "DISPLAY=:0 steam"

sudo ip netns pids steam_ns | xargs -rd'\n' sudo kill
sudo rm -rf /etc/netns/steam_ns
sudo sysctl -q net.ipv4.ip_forward=0
sudo iptables -D INPUT ! -i steam_ns0 -s $IP_SUBNET.0/24 -j DROP
sudo iptables -t nat -D POSTROUTING -s $IP_SUBNET.0/24 -o en+ -j MASQUERADE
sudo ip link del steam_ns0
sudo ip netns delete steam_ns

Reporting back that shutting all other interfaces than your internet and loopback will allow you to play Satisfactory multiplayer without issues.

For now I have a workaround. huzzah!
Thank you all for the help.

You can use namespaces to launch Steam with a single network interface. Change IP_SUBNET if you already have the same and USER_NAME_TO_RUN_STEAM. Check net.ipv4.ip_forward, if you don't need to change it.

You absolute champion, thanks!

Thanks, removing the virt-manager network interface via 'sudo virsh net-destroy default' did the trick for me!

This finally did the trick. I had to ifconfig down my other interfaces (docker0, wifi) and then I was able to join other games without problems.
(Though I still needed to have ports 50000-65000 forwarded to host)

Neither this suggestion (link to my own gist here), nor this one worked for me (see below copy/paste).

My system's details

$ ip addr

[2020-07-11 13:38:43] 0 x10an14@x10-desktop:~
-> $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp42s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 70:85:c2:83:67:04 brd ff:ff:ff:ff:ff:ff
    inet 192.168.14.4/24 brd 192.168.14.255 scope global dynamic enp42s0
       valid_lft 85296sec preferred_lft 85296sec
    inet6 fe80::7285:c2ff:fe83:6704/64 scope link 
       valid_lft forever preferred_lft forever
3: enp45s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 70:85:c2:83:67:02 brd ff:ff:ff:ff:ff:ff
4: wlp39s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 94:b8:6d:2e:c9:a8 brd ff:ff:ff:ff:ff:ff
5: br-223757ae9ac0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:1f:24:62:22 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-223757ae9ac0
       valid_lft forever preferred_lft forever
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:87:e1:1a:64 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
[2020-07-11 13:41:47] 0 x10an14@x10-desktop:~
-> $

I'm on;

$ lsb_release -a
$ uname -a

[2020-07-11 13:41:47] 0 x10an14@x10-desktop:~
-> $ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 10 (buster)
Release:	10
Codename:	buster
[2020-07-11 13:42:26] 0 x10an14@x10-desktop:~
-> $ uname -a
Linux x10-desktop 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux
[2020-07-11 13:42:32] 0 x10an14@x10-desktop:~
-> $

[448]LogNet: Browse: EOS.00020fe2d4014e23a343a18773216d32e330c946493e4476ba5dfb4d82dfbfce//Game/FactoryGame/Map/MenuScenes/MenuScene_02
[448]PacketHandlerLog: Loaded PacketHandler component: Engine.EngineHandlerComponentFactory (StatelessConnectHandlerComponent)
[ 36]LogSocketSubsystemEOS: EOSSDK::OnRemoteConnectionClosedCb 0x00000000005FE3E0
[ 36]LogSocketSubsystemEOS: Connection closed from 00020fe2d4014e23a343a18773216d32, with reason EOS_CCR_ClosedByPeer
[636]LogSocketSubsystemEOS: EOSSDK::OnRemoteConnectionClosedCb 0x00000000005FE3E0
[636]LogSocketSubsystemEOS: Connection closed from 00020fe2d4014e23a343a18773216d32, with reason EOS_CCR_ClosedByPeer
[235]LogSocketSubsystemEOS: EOSSDK::OnRemoteConnectionClosedCb 0x00000000005FE3E0
[235]LogSocketSubsystemEOS: Connection closed from 00020fe2d4014e23a343a18773216d32, with reason EOS_CCR_ClosedByPeer
[317]LogSlate: FSceneViewport::OnFocusLost() reason 0
[669]LogNet: Warning: UNetConnection::Tick: Connection TIMED OUT. Closing connection.. Elapsed: 60.05, Real: 60.02, Good: 60.02, DriverTime: 60.05, Threshold: 60.00, [UNetConnection] RemoteAddr: EOS.00020fe2d4014e23a343a18773216d32e330c946493e4476ba5dfb4d82dfbfce:7777, Name: EOSNetConnection_0, Driver: PendingNetDriver EOSNetDriver_0, IsServer: NO, PC: NULL, Owner: NULL, UniqueId: INVALID
[669]LogNet: Warning: Network Failure: PendingNetDriver[ConnectionTimeout]: UNetConnection::Tick: Connection TIMED OUT. Closing connection.. Elapsed: 60.05, Real: 60.02, Good: 60.02, DriverTime: 60.05, Threshold: 60.00, [UNetConnection] RemoteAddr: EOS.00020fe2d4014e23a343a18773216d32e330c946493e4476ba5dfb4d82dfbfce:7777, Name: EOSNetConnection_0, Driver: PendingNetDriver EOSNetDriver_0, IsServer: NO, PC: NULL, Owner: NULL, UniqueId: INVALID
[669]LogGame: Error: Network Error Recived: Type: 1121126232, MSG: UNetConnection::Tick: Connection TIMED OUT. Closing connection.. Elapsed: 60.05, Real: 60.02, Good: 60.02, DriverTime: 60.05, Threshold: 60.00, [UNetConnection] RemoteAddr: EOS.00020fe2d4014e23a343a18773216d32e330c946493e4476ba5dfb4d82dfbfce:7777, Name: EOSNetConnection_0, Driver: PendingNetDriver EOSNetDriver_0, IsServer: NO, PC: NULL, Owner: NULL, UniqueId: INVALID
[669]LogNet: NetworkFailure: ConnectionTimeout, Error: 'UNetConnection::Tick: Connection TIMED OUT. Closing connection.. Elapsed: 60.05, Real: 60.02, Good: 60.02, DriverTime: 60.05, Threshold: 60.00, [UNetConnection] RemoteAddr: EOS.00020fe2d4014e23a343a18773216d32e330c946493e4476ba5dfb4d82dfbfce:7777, Name: EOSNetConnection_0, Driver: PendingNetDriver EOSNetDriver_0, IsServer: NO, PC: NULL, Owner: NULL, UniqueId: INVALID'

Request

Does any kind, samaritan soul have any suggestion on how to debug this further?
It's the "Timeout"/"Connection not found" error I get in-game when trying to connect to friends (on Windows), or they try to connect to me.

EDIT: Added headings, and an older error log of the same error.
EDIT2: Clean-up after Valve's edit - whose edit made the post more digestible =).

This did work, however that required both taking down my VMs and my VPN. Those interfaces were completely gone not shutdown, which may have played a part. (When I did this, I only had lo, enp10s0, enp15s0, enp0s31f6, and wlp9s0.

This other solution which I far preferred doesn't really translate over to firewalld sadly, even with the iptables input mode.

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp10s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether [BLOCKED] brd ff:ff:ff:ff:ff:ff
    inet [BLOCKED] brd [BLOCKED] scope global dynamic noprefixroute enp10s0
       valid_lft 2538413sec preferred_lft 2538413sec
    inet6 [BLOCKED] scope link noprefixroute
       valid_lft forever preferred_lft forever
3: enp15s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether [BLOCKED] brd ff:ff:ff:ff:ff:ff
4: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether [BLOCKED] brd ff:ff:ff:ff:ff:ff
5: wlp9s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether [BLOCKED] brd ff:ff:ff:ff:ff:ff permaddr [BLOCKED]
6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1380 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none
    inet [BLOCKED] scope global tun0
       valid_lft forever preferred_lft forever
    inet6 [BLOCKED] scope global
       valid_lft forever preferred_lft forever
    inet6 [BLOCKED] scope link stable-privacy
       valid_lft forever preferred_lft forever
7: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
    inet 172.16.206.1/24 brd 172.16.206.255 scope global vmnet1
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:fec0:1/64 scope link
       valid_lft forever preferred_lft forever
8: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
    inet 192.168.237.1/24 brd 192.168.237.255 scope global vmnet8
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:fec0:8/64 scope link
       valid_lft forever preferred_lft forever

$ lsb_release -a
LSB Version:	:core-4.1-amd64:core-4.1-noarch
Distributor ID:	Fedora
Description:	Fedora release 32 (Thirty Two)
Release:	32
Codename:	ThirtyTwo

$ uname -a
Linux neodymium 5.7.8-200.fc32.x86_64 #1 SMP Thu Jul 9 14:34:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

I also had this problem where I had 4/4 connecting to host and then everything would time out after 30-60 seconds or so.

Following the discussion above:

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1:  mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether xxxxxxxxxxxx brd ff:ff:ff:ff:ff:ff
3: wlx001325ac0fed:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether xxxxxxxxxxxxxxx brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.44/24 brd 192.168.1.255 scope global noprefixroute wlx001325ac0fed
       valid_lft forever preferred_lft forever
    inet6 xxxxxxxxxxxxxxx/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
4: docker0:  mtu 1500 qdisc noqueue state DOWN group default
    link/ether xxxxxxxxxxxxxxx ff:ff:ff:ff:ff:ff
    inet xxxxxxxxxxxxxxxxx scope global docker0
       valid_lft forever preferred_lft forever

This was what I was dealing with originally

then i did

sudo ip link delete docker0

which removed the above lines (4: docker0 and everything below it)

and then everything worked perfectly!

Since I absolutely require my Docker and Libvirt interfaces, net namespaces were the only way to get Satisfactory running in a way that my friend (also using Proton) could connect to, but the above script didn't work for me (Steam couldn't log in on launch).

I ended up using https://gist.github.com/dpino/6c0dca1742093346461e11aa8f608a99, though using sudo -E (to preserve environment variables) was necessary so that dbus (and thus PulseAudio) would be accessible for the game to have sound.

sudo -E  ~/bin/ns-inet.sh enp7s0

ns1> sudo -E -u j steam

The script worked without modifications on my Gentoo system. My friend runs Artix and had to change L85 from routing via VPEER_ADDR to routing via VETH_ADDR - this was discussed in a comment in that gist, https://gist.github.com/dpino/6c0dca1742093346461e11aa8f608a99#gistcomment-2001534. YMMV.

Thats strange, because I'm using pulseaudio, winecfg running from protontricks show me that I use pulseaudio and sound test from winecfg are working. Also when I changing Proton version back to previous all working fine too (with pulseaudio ofc)

That's a log after successful start with Proton 5.9-GE-8-ST, I just selected it back without removing ~/.steam/steam/steamapps/compatdata/526870

steam-526870.log

@Optimus22Prime There is a potential dxvk regression that we are investigating, and your log looks similar to a failure log related to that regression. Could you try putting an older version of dxvk into your Proton 5.13/dist folder and checking if you still get the launch failure? The easiest way to do this is to just copy the contents of Proton 5.0/dist/lib/wine/dxvk/* and Proton 5.0/dist/lib64/wine/dxvk/* into the corresponding dxvk folders in Proton 5.13/dist. Let me know if you need more detailed instructions :)

After you are done testing, just delete the entire Proton 5.13/dist folder to reset everything.

@alasky17 I did as you said to do, game not starting anyway. There is a log
steam-526870.log

@Optimus22Prime I just realized my request was a bit silly. Could you try just disabling dxvk entirely? PROTON_USE_WINED3D=1 %command% in the launch options or via usersettings.py. Not likely to give a different result, but since I can't reproduce what you are seeing to troubleshoot more easily, I think its worth a shot :)

@alasky17 Did it, no go, log attached. I see Satisfactory splash, then black screen, then it's crash to desktop without any wine error message window. Btw I'm experienced linux and wine user, so you can give some complex orders to troubleshoot issue if you wish
steam-526870.log
.

@Optimus22Prime That's very good to know.. Hard to tell without context :) My co-worker will definitely be better suited to that kind of troubleshooting when they get back next week. I'll direct them to this thread :+1: Thank you for putting up with my troubleshooting so far! It would have been so convenient if it was the same failure haha. At least you have 5.0 in the meantime :)

Edit: Well, you could always try to do a bisect in the meantime if you feel like it ;) If the failure also happens on plain wine-5.13 that would be super convenient. Also would be telling if the game works there even if you don't have time to run the full bisect.

Edit2: Forgot to mention - the reason I'm asking this is because I can't repro the problem. So be aware it could be a race condition :D

@alasky17 lol, stock 5.0 have some small glitch with starting cartoon not playing at capsule screen during planetfall, its not game breaking anyway. Latest GE Proton btw works like a charm :)

Well will try some bisecting, I can do this. And I'm not going anywhere, so I can wait for your co-worker returning. Hmm, about race condition, It's interesting suggestion, because a have NUMA workstation, presume I will try to bind the game to only one node...

@alasky17 Well, playing with numactl give me nothing, so I will begin to compile plain wine-5.13 and wine-staging-5.13 then, will see whats happens

@alasky17 Well, game started fine with latest wine-staging-5.19 (sorry, there is no 5.13 in gentoo portage tree, too old, lol), but I can build 5.13 from overlay, and if it not running the game I can find some next one that run and do some bisecting then.

@alasky17 so, plain wine-vanilla-5.13, wine-staging-5.13, wine-staging-5.13+dxvk-1.7.2 all fine, game are starting with them as usual. So, looks like its a time to compile proton locally by myself?

@alasky17 @kisak-valve Finally after some meditation over Proton log I'm figured out what happens and can fix issue. I was not enabling BPF JIT Compiler as default in my custom linux kernel. Dunno why, but enabling BPF JIT Compiler as default are matter for prebuilded Proton 5.13-1 to work, and not so matter for previous and my own local builds. After rebuilding kernel with option "BPF JIT Compiler enabled as default" game starting fine with Proton 5.13-1 out of the box. Sorry for spam, you can remove Regression label now.

@Optimus22Prime nice work! No worries about the spam, this is super good to know. I'm not sure where that requirement is coming from but it is definitely something we should investigate :+1:

@pherralis Thanks for the suggestion to simply taking the connections down for the short term!

I need my other interfaces, unfortunately. No wine trickery possible to get around this?

You can use namespaces to launch Steam with a single network interface. Change IP_SUBNET if you already have the same and USER_NAME_TO_RUN_STEAM. Check net.ipv4.ip_forward, if you don't need to change it.
Script example:

#!/bin/bash

USER_NAME_TO_RUN_STEAM="YourUser"
IP_SUBNET="10.10.10"

sudo ip netns add steam_ns
sudo ip netns exec steam_ns ip addr add 127.0.0.1/8 dev lo
sudo ip netns exec steam_ns ip link set lo up
sudo ip link add steam_ns0 type veth peer name steam_ns1
sudo ip link set steam_ns0 up
sudo ip link set steam_ns1 netns steam_ns up
sudo ip addr add $IP_SUBNET.1/24 dev steam_ns0
sudo ip netns exec steam_ns ip addr add $IP_SUBNET.2/24 dev steam_ns1
sudo ip netns exec steam_ns ip route add default via $IP_SUBNET.1 dev steam_ns1
sudo iptables -A INPUT ! -i steam_ns0 -s $IP_SUBNET.0/24 -j DROP
sudo iptables -t nat -A POSTROUTING -s $IP_SUBNET.0/24 -o en+ -j MASQUERADE
sudo sysctl -q net.ipv4.ip_forward=1
sudo mkdir -p /etc/netns/steam_ns
echo "nameserver 8.8.8.8" | sudo tee /etc/netns/steam_ns/resolv.conf

sudo ip netns exec steam_ns su - $USER_NAME_TO_RUN_STEAM -c "DISPLAY=:0 steam"

sudo ip netns pids steam_ns | xargs -rd'\n' sudo kill
sudo rm -rf /etc/netns/steam_ns
sudo sysctl -q net.ipv4.ip_forward=0
sudo iptables -D INPUT ! -i steam_ns0 -s $IP_SUBNET.0/24 -j DROP
sudo iptables -t nat -D POSTROUTING -s $IP_SUBNET.0/24 -o en+ -j MASQUERADE
sudo ip link del steam_ns0
sudo ip netns delete steam_ns

This script looks promising. Unfortunately Steam doesn't reach the internet at all when I use it. What do you mean with "Check net.ipv4.ip_forward, if you don't need to change it."? How do I know and what would I need to change it to?

Another issue:

Am unable to complete the initial login on game start, Attempting to use an existing epic account., it simply loops with the message "Working... Check Browser". Nothing in any browser ever opens.

[2020.12.30-06.58.37:842][ 13]LogOnlineIdentity: STEAM: Got Steam Login Token with length 126
[2020.12.30-06.58.37:842][ 13]LogOnlineIdentity: OSS: Got Steam Login Token result: True
[2020.12.30-06.58.37:842][ 13]LogOnlineIdentity: OSS: Calling EOS_Connect_Login
[2020.12.30-06.58.37:892][ 18]LogOnline: Warning: OSS: EOSSDK-LogEOSEcom: Purchase flow is disabled due to overlay setup failure (EOS_NotConfigured).
[2020.12.30-06.58.38:118][ 44]LogOnline: Warning: OSS: EOSSDK-LogEOS: Error response received from backend. ServiceName=[EOSAuth], OperationName=[TokenGrant], Url=[<Redacted>], HttpStatus=[404], ErrorCode=[errors.com.epicgames.eos.auth.user_not_found], NumericErrorCode=[110016], ErrorMessage=[EOS User Identity not found. identityProviderId: steam accountId: <Redacted>], CorrId=[<Redacted>]
[2020.12.30-06.58.38:135][ 46]LogOnlineIdentity: OSS: Got reply from EOS_Connect_Login
[2020.12.30-06.58.38:135][ 46]LogOnlineIdentity: OSS: EEosAccountConnectionResult::NoConnecedId
[2020.12.30-06.58.38:135][ 46]LogOnlineIdentity: OSS: Update account connection GUI with event
[2020.12.30-06.58.38:135][ 46]LogOnline: OSS: BroadcastAccountConnectionStepResult: EEosAccountConnectionResult::NoConnecedId
[2020.12.30-06.58.42:072][490]LogSlate: FSceneViewport::OnFocusLost() reason 0
[2020.12.30-06.58.43:605][662]LogOnlineIdentity: Error: OSS: EOS-OSS: GetProductUserId() failed. Non EOS User queried, had no local maping or ID stored in presence, or presence was unavailable. USER: (STEAM)Diana [<Redacted>]
[2020.12.30-06.58.44:560][769]LogOnlineIdentity: OSS:  Logging In with Account Portal
[2020.12.30-06.54.34:707][120]LogOnline: Warning: OSS: EOSSDK-LogEOS: Error response received from backend. ServiceName=[OAuth], OperationName=[TokenGrant], Url=[<Redacted>], HttpStatus=[400], ErrorCode=[errors.com.epicgames.account.oauth.authorization_pending], NumericErrorCode=[1012], ErrorMessage=[The authorization server request is still pending as the end user has yet to visit and enter the verification code.], CorrId=[<Redacted>]

Attempting to use an existing epic account [without xdg-desktop-portal installed], it simply loops with the message "Working... Check Browser"

In SteamLinuxRuntime_soldier version 0.20210406.0 and up (currently in the beta branch of Steam Linux Runtime - Soldier but not in the default branch), if we can't contact xdg-desktop-portal for a http or https URL, we fall back to sending the URL to Steam instead. This should fix that particular issue for people who don't have xdg-desktop-portal.

Installing xdg-desktop-portal is still recommended.

for those googling and finding this thread, installing xdg-desktop-portal worked for me on Arch Linux. Before, the game was saying "Check browser" but nothing was being opened.

Installing xdg-desktop-portal fixed it for me, and a web browser opened so I could log in to Epic

Thanks!

Satisfactory has been freezing for me while loading the main menu ever since update 4 left the experimental branch. (I played update 4 on Experimental just fine).

OS: Arch Linux
CPU: Ryzen 3700X
GPU: AMD 5700XT
Memory: 32 G

I've tried mesa and mesa-git- same behavior on both. I have a feeling it's something weird with my system but idk how to find out what the problem is.

https://gist.github.com/Berinth/d5b10f4d7a97ebe874df0176c8834dd3

@Berinth Since update 4 I had the same issue where it would freeze and eventually quit during the loading screen. I was able to fix it by going to Properties -> General -> "Enable the Steam Overlay while in-game" and disabling it and that seemed to clear up the problem. I've got it to run on Proton 6.3-4 and 5.13-6.

As it was mentioned back in the day above in the thread have you tried running virsh net-destroy default as root?

Also, if you use VMware on your computer run vmware-networks --stop as root after running the command above. The game does not like the virtual network adapters that VMware creates for your virtual machines.

It works for me on Mageia 8. After I start the server I run this script and my friend can connect immediately after:

#!/bin/sh
sudo virsh net-destroy default
sudo vmware-networks --stop

I hope it helps!

Unfortunately, that didn't work. I do have VirtualBox and Docker installed, if either of those could be messing something up.

I've been just nuking virtual network interfaces whenever I want to play. Identify your real interfaces, ip link list helps. (for me I have two physical nics that start with enp, and one wifi that starts with wlp). And then delete the rest ip link delete <interface>. For my I have two virtual interfaces for vms, and the docker interface. So it's something like ip link delete docker0 etc.

In my case, these will be re-created on reboot. Make sure you know what you're deleting, and how to get them back if necessary. I can't guarantee they'll get re-created like mine are.

I am having the same network problem being discussed here, but I only have2 interfaces (wired + loopback) and nothing else.
This has started happening very recently, a few weeks ago I was playing with friends with no problems, while today I just can't (same friends!)

Similar issue to that of @Darkhogg, I have only 2 network interfaces (enp3s0 + lo), docker and libvirtd are installed but not running. I already tried enabling UPnP/PCP and forwarding ports 5222 (TCP/UDP), 6666 (TCP/UDP), 7777-7827 (UDP) but the problem persists. Everything worked 1-2 months ago.

Most of the time the game is stuck on this screen when trying to connect to a session:

which then results in this error message:

Hosting does not work either, the person trying to connect is also stuck on the "connecting to host 4/4" screen. Once the host was able to see me connect, but I was once again kicked out during the respawn sequence with the same timeout error.

Tested on Arch Linux with Proton-6.14-GE-2.

With some recent update on Manjaro Linux, Proton 6.3-6 i can no longer unfocus the game or alt-tab out from it
It has randomly come back.

Regarding the network issues, this is usually caused by additional NICs, or Epic Online Services being weird.

Potential workaround: Join other people's session via session ID.

@TheHooly In my case at least, joining via code doesn't change anything, and I only have my wired interface (checked via terminal). Also it started happening randomly, nothing changed on my part that I know of. Weird.

Experimental build from today won't start with vulkan renderer.
With launch option: %command% -vulkan or after selecting vulkan in the games settings I get the following errors:

LogWindows: Error: === Critical error: ===
LogWindows: Error:
LogWindows: Error: Fatal error: [File:D:/ws/SB-160502110050-fad/UE4/Engine/Source/Runtime/VulkanRHI/Private/VulkanUt
il.cpp] [Line: 803]
LogWindows: Error: VulkanRHI::vkEnumerateDeviceExtensionProperties(Device, LayerName, &Count, nullptr) failed, VkRes
ult=-6
LogWindows: Error:  at D:/ws/SB-160502110050-fad/UE4/Engine/Source/Runtime/VulkanRHI/Private/VulkanLayers.cpp:196 
LogWindows: Error:  with error VK_ERROR_LAYER_NOT_PRESENT
LogWindows: Error:
LogWindows: Error:
LogWindows: Error: [Callstack] 0x000000007b01236e EntryPoint() []
LogWindows: Error: [Callstack] 0x000000018025eec6 ReportAssert() []
LogWindows: Error: [Callstack] 0x00000001802616c6 FWindowsErrorOutputDevice::Serialize() []
LogWindows: Error: [Callstack] 0x00000001801de57d FOutputDevice::LogfImpl() []
LogWindows: Error: [Callstack] 0x0000000026c04afd VulkanRHI::VerifyVulkanResult() []
LogWindows: Error: [Callstack] 0x0000000026b8dbf0 FVulkanDevice::GetDeviceExtensionsAndLayers() []
LogWindows: Error: [Callstack] 0x0000000026b9302b FVulkanDevice::QueryGPU() []
LogWindows: Error: [Callstack] 0x0000000026bfff08 FVulkanDynamicRHI::SelectAndInitDevice() []
LogWindows: Error: [Callstack] 0x0000000026bef04d FVulkanDynamicRHI::InitInstance() []
LogWindows: Error: [Callstack] 0x0000000026beed78 FVulkanDynamicRHI::Init() []
LogWindows: Error: [Callstack] 0x00000000032a8820 RHIInit() []
LogWindows: Error: [Callstack] 0x000000014001068e FEngineLoop::PreInitPreStartupScreen() []
LogWindows: Error:

With regards to network issues:

I've had some success solving the join game timeout using https://github.com/netblue30/firejail/. I use the following launch command:

firejail --name=satisfactory --noprofile --net=eth0 --ip=dhcp --keep-dev-shm -- %command%

--net=eth0 must match your network interface.

Note that this breaks the Steam overlay (and it doesn't know you're logged into Steam) but the Epic login seems fine and I can join games with no other issues.

@taisph @Darkhogg @TheHooly @cdgriffith @p-mng @UnstoppableMango @alaskanpuffin And everyone else who's had networking troubles with this game :) The most recent experimental release (experimental-6.3-20211013) has a fix for the problem with multiple network interfaces. Please try disabling any workarounds you are currently using and see if you still see the networking failures with this build.

Thank you for the ping @alasky17, I have tested with the latest experimental on a known "bad" setup and it now works both via local network and when using a VPN!

@alasky17 I can also confirm it is now working with no need to delete network interfaces! Thanks!

OS: Arch Linux
KERNEL: 5.14.15-zen1-1-zen
CPU: AMD Ryzen 7 3800XT 8-Core
GPU: AMD Radeon RX Vega (VEGA10, DRM 3.42.0, 5.14.15-zen1-1-zen, LLVM 13.0.0)
GPU DRIVER: 4.6 Mesa 21.2.5
RAM: 32 GB

About the same here. Starting the game in steam result in compiling of vulkan =shaders, and then... nothing else just the steam play button goes back to green.

In log files theres something:

[2021.10.30-10.35.08:145][  0]LogSlate: New Slate User Created.  User Index 0, Is Virtual User: 0
[2021.10.30-10.35.08:145][  0]LogSlate: Slate User Registered.  User Index 0, Is Virtual User: 0
[2021.10.30-10.35.08:147][  0]LogSlate: Using FreeType 2.10.0
[2021.10.30-10.35.08:148][  0]LogSlate: SlateFontServices - WITH_FREETYPE: 1, WITH_HARFBUZZ: 1
[2021.10.30-10.35.08:275][  0]LogStandaloneRenderer: Warning: SlateD3DShaders::CompileShader() - D3DCompilerFunc Result: DXGI_ERROR_80004005 [80004005]
[2021.10.30-10.35.08:275][  0]LogStandaloneRenderer: Warning: <anonymous>:10:8: E5005: Function "min" is not defined.
 Result: DXGI_ERROR_80004005 [80004005]
[2021.10.30-10.35.08:276][  0]LogStandaloneRenderer: Warning: SlateD3DShaders::CompileShader() - D3DCompilerFunc Result: DXGI_ERROR_80004005 [80004005]
[2021.10.30-10.35.08:276][  0]LogStandaloneRenderer: Warning: <anonymous>:7:1: W4300: Redefinition of ESlateShader.
<anonymous>:8:1: W4300: Redefinition of ESlateShader.
<anonymous>:9:1: W4300: Redefinition of ESlateShader.
<anonymous>:10:1: W4300: Redefinition of ESlateShader.
<anonymous>:10:8: E5005: Function "min" is not defined.
 Result: DXGI_ERROR_80004005 [80004005]
[2021.10.30-10.35.26:347][  0]LogSlate: Slate User Destroyed.  User Index 0, Is Virtual User: 0
[2021.10.30-10.35.26:347][  0]LogCore: Engine exit requested (reason: CrashReportClientApp RequestExit)
[2021.10.30-10.35.26:347][  0]LogExit: Preparing to exit.
[2021.10.30-10.35.26:348][  0]LogExit: Object subsystem successfully closed.
[2021.10.30-10.35.26:351][  0]LogModuleManager: Shutting down and abandoning module ImageWrapper (12)
[2021.10.30-10.35.26:351][  0]LogModuleManager: Shutting down and abandoning module InputCore (10)
[2021.10.30-10.35.26:351][  0]LogModuleManager: Shutting down and abandoning module CrashDebugHelper (8)
[2021.10.30-10.35.26:351][  0]LogModuleManager: Shutting down and abandoning module CoreUObject (6)
[2021.10.30-10.35.26:352][  0]LogModuleManager: Shutting down and abandoning module PakFile (4)
[2021.10.30-10.35.26:352][  0]LogModuleManager: Shutting down and abandoning module RSA (3)
[2021.10.30-10.35.26:353][  0]LogExit: Exiting.
[2021.10.30-10.35.26:364][  0]Log file closed, 10/30/21 12:35:26

steam-526870.log
CrashReportClient.log

Maybe @Joshua-Ashton have an idea?

PS:

Another log snippet from a crashlog with 6.20-GE proton:

[2021.10.30-11.45.42:889][  0]LogCrashDebugHelper: BuildVersion: ++FactoryGame+main-CL-170636
[2021.10.30-11.45.42:899][  0]LogWindowsTextInputMethodSystem: Display: IME system deactivated.
[2021.10.30-11.45.42:915][  0]LogSlate: New Slate User Created.  User Index 0, Is Virtual User: 0
[2021.10.30-11.45.42:915][  0]LogSlate: Slate User Registered.  User Index 0, Is Virtual User: 0
[2021.10.30-11.45.42:916][  0]LogSlate: Using FreeType 2.10.0
[2021.10.30-11.45.42:916][  0]LogSlate: SlateFontServices - WITH_FREETYPE: 1, WITH_HARFBUZZ: 1
[2021.10.30-11.45.43:044][  0]LogStandaloneRenderer: Warning: SlateD3DShaders::CompileShader() - D3DCompilerFunc Result: DXGI_ERROR_80004001 [80004001]
[2021.10.30-11.45.43:044][  0]LogStandaloneRenderer: Warning: D3DCompilerFunc failed, no error text provided Result: DXGI_ERROR_80004001 [80004001]
[2021.10.30-11.45.43:044][  0]LogStandaloneRenderer: Warning: SlateD3DShaders::CompileShader() - D3DCompilerFunc Result: DXGI_ERROR_80004001 [80004001]
[2021.10.30-11.45.43:044][  0]LogStandaloneRenderer: Warning: D3DCompilerFunc failed, no error text provided Result: DXGI_ERROR_80004001 [80004001]
[2021.10.30-11.46.01:068][  0]LogSlate: Slate User Destroyed.  User Index 0, Is Virtual User: 0
[2021.10.30-11.46.01:068][  0]LogCore: Engine exit requested (reason: CrashReportClientApp RequestExit)
[2021.10.30-11.46.01:068][  0]LogExit: Preparing to exit.
[2021.10.30-11.46.01:068][  0]LogExit: Object subsystem successfully closed.

Another log while im trying to start the game with 6.20-ge with -vulkan:
FactoryGame.log
CrashReportClient.log

With the latest experimental update I am now having the same symptoms as @plasticbomb1986, after compiling vulkan shaders the play button turns green again but nothing happens

EDIT: With the launch option "d3d11" to disable vulkan, I am getting my old behavour, as in splash screen, then black screen, then crash to desktop

does dx12 work any better?

does dx12 work any better?

Same result

Experimental does something different with the bottles, so if you have an issue with the game crsahing, I recommend to first reset the bottle. <yourSteamLib>/steamapps/compatdata/526870 rename that folder and launch the game again. Don't delete it, you maybe want to copy over some settings... ;)

I just tried that, it still does not work for me

EDIT: Also tried with -vulkanlaunch option, still same result with blackscreen and crash to desktop

Just installed the 495 drivers, added the vulkan settings to the engine.ini file and tested with different Proton versions (always creating a new folder in compatdata, and adjusting engine.ini again).

However, it still not works, although behaviour is a bit different now. It shows the splash screen for a few seconds (much longer than before), and cpu usage goes up, but then crashes.

My proton log for 6.3:
steam-526870.log

Saw some people complaining similar crashes on steam with experimentel branhc, so its possible wont be a wine/proton issue, but at Coffe Stain they have made a mistake, probably.

In the FactoryGame.log I am finding this error:

[2021.10.31-11.14.28:360][  0]LogVulkanRHI: Error: VulkanRHI::vkEnumerateDeviceExtensionProperties(Device, LayerName, &Count, nullptr) failed, VkResult=-6
 at D:/ws/SB-160502110050-fad/UE4/Engine/Source/Runtime/VulkanRHI/Private/VulkanLayers.cpp:196  with error VK_ERROR_LAYER_NOT_PRESENT

Im getting the same error across all render api implementation:

[2021.10.31-18.22.41:653][  0]LogWindows: Warning: SymLoadModuleExW. Error: 6
[2021.10.31-18.22.41:653][  0]LogWindows: Warning: SymLoadModuleExW. Error: 6
[2021.10.31-18.22.41:653][  0]LogWindows: Warning: SymLoadModuleExW. Error: 6
[2021.10.31-18.22.41:653][  0]LogWindows: Warning: SymLoadModuleExW. Error: 6
[2021.10.31-18.22.41:653][  0]LogWindows: Warning: SymLoadModuleExW. Error: 6
[2021.10.31-18.22.41:653][  0]LogWindows: Warning: SymLoadModuleExW. Error: 6
[2021.10.31-18.22.41:653][  0]LogWindows: Error: === Critical error: ===
[2021.10.31-18.22.41:653][  0]LogWindows: Error: 
[2021.10.31-18.22.41:653][  0]LogWindows: Error: Fatal error!
[2021.10.31-18.22.41:653][  0]LogWindows: Error: 
[2021.10.31-18.22.41:653][  0]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000018
[2021.10.31-18.22.41:653][  0]LogWindows: Error: 
[2021.10.31-18.22.41:653][  0]LogWindows: Error: [Callstack] 0x00000000014688b9 UE4CodeGen_Private::ConstructFProperty() []
[2021.10.31-18.22.41:653][  0]LogWindows: Error: [Callstack] 0x000000000146a281 UE4CodeGen_Private::ConstructFProperty() []
[2021.10.31-18.22.41:653][  0]LogWindows: Error: [Callstack] 0x000000000146b1d9 UE4CodeGen_Private::ConstructUScriptStruct() []
[2021.10.31-18.22.41:653][  0]LogWindows: Error: 
[2021.10.31-18.22.41:672][  0]LogExit: Executing StaticShutdownAfterError
[2021.10.31-18.22.41:677][  0]LogWindows: FPlatformMisc::RequestExit(1)
[2021.10.31-18.22.41:677][  0]LogCore: Engine exit requested (reason: Win RequestExit)

Went into the proton 6.3.7 folder and replaced both dxvk and vkd3d-proton files, thought maybe thats the issue, but no go.

Experimental build from today won't start with vulkan renderer.

I can confirm that adding launch option -d3d11 in steam resolves this. Then change it back to DX11 in the game's options.

When I have VRR (FreeSync) enabled, I just get a black screen. This happens with both the stable and experimental branches, and with D3D11 (DXVK) and native Vulkan.

Disabling VRR in my compositor makes this game run as it should, but that of course robs me of FreeSync...

Even with -d3d11 start flag, it crashes with exitcode 0 on startup and no visible debug output or symbols, e.g.:
Start monitoring process... Initial process has exited (return code: 0)

Is anyone else still having multiplayer connectivity issues?

I'm on Fedora 34 and had issues connecting to my brother's session (Windows). Booting to a Windows partition on the same box, I am able to connect so I don't believe the issue is on the other end or in my network... but I'd really like to play from Linux if possible. We both selected the Steam / new EOS account (left option) when setting up the game.

On Fedora with my out-of-the-box setup (no specifi proton version selected), I had some minor issues with the tutorial "videos" not playing and got the same connectivity error message (UNetConnection TIMEOUT) as in the OP.

Based on protondb, I updated my launch params as WINE_FULLSCREEN_FSR=1 gamemoderun %command% and had run protontricks 526870 vc2017 and protontricks 526870 dotnet472 vcrun2015 faudio d3dcompiler_47 (I did not use the force option) but neither of these seemed to do much.

I tried Proton-vGE 6.21-GE-2 after seeing the release notes for the 6.20-GE-1 mentioned

-proton-valve: Imported fixes for Satisfactory multiplayer from proton upstream

Installing this and setting the game to force that proton ge version did fix my "video" issues in the tutorial but not my connectivity issues. Based on other comments here, I also tried sudo virsh net-destroy default (as I do have QEmu / virt-manager installed but I do not have docker... I use rootless podman instead so no perma net interface). Unfortunately, this didn't do anything to resolve the issues, connecting by steam id (timeout error) or by session id (session not found).

Any suggestions?

I saw the iptables scripts in the comments by pekhterev and some gist variants of it. I was thinking about trying this next but wasn't clear on the usage instructions outside of editing the username/ip subnet in the script. None of those appear to be making permanent changes and I assume that rebooting the system would be enough to "undo" them. Is that correct? Other than that, I assume from klardotsh's comment that you just close steam, run the script (after editing for user name and ip subnet), and then start steam again, then launch the game?

@alaskanpuffin just switched to Experimental (didn't mess with compatdata) and joined his session; no issues. Thanks for the suggestion! Saved me diving down a wrong path for nothing :-)

Replying to https://github.com/ValveSoftware/Proton/issues/3957#issuecomment-1005758353

In Steam, right click Satisfactory in your Library, properties, general, in launch options add the below line:
PROTON_LOG=1 %command%

Start the game, a file called steam-526870.log will be created in your home folder: /home/username, if you could attach that to a comment here?

Just in case it helps, i had the same issues after reinstalling it after a long time.
Deleted the proton bottle, tried different versions / different parameter, verified integrity, but always got the crash at startup (sometimes after the logo was shown),

Finally i tried to just uninstall it, delete the game folder (which at that point only contained logs) and installed it again.
That did the trick and now it runs.
My assumption is that there WAS a bug with the uninstaller when i uninstalled it way back then which left files which somehow did lead to problems.

For me the game runs just fine on vulkan. The issue im facing is basically screwed up audio:

https://user-images.githubusercontent.com/16738302/159385586-49acc49f-ec17-498f-b037-85032f2baae0.mp4

The game is basically unplayable like this sadly.

For me the game runs just fine on vulkan. The issue im facing is basically screwed up audio:
The game is basically unplayable like this sadly.

Try reverting to dx12 in the meantime.

For me the game runs just fine on vulkan. The issue im facing is basically screwed up audio:
The game is basically unplayable like this sadly.

Try reverting to dx12 in the meantime.

This also happens on dx12 dx11 and any other graphics api.

This also happens on dx12 dx11 and any other graphics api.

Sounds more like a problem with the sound device/driver. Does other unreal engine based games work for you?

This also happens on dx12 dx11 and any other graphics api.

Sounds more like a problem with the sound device/driver. Does other unreal engine based games work for you?

They indeed do. Tested by playing The Turing Test.

Sound there works flawlessly.

Sound driver is pipewire.

EDIT: Today i tried temp switch to pulseaudio which works surprisingly. Seems to be pipewire issue.

For me It also crashed for me after the splash screen, then black screen, then crash.
Launched with %command% -vulkan, with Proton 7.0-1.

LogPakFile: Display: Found Pak file ../../../FactoryGame/Content/Paks/FactoryGame-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../FactoryGame/Content/Paks/FactoryGame-WindowsNoEditor.pak.
LogFileManager: Error: Requested read of 160 bytes when 157 bytes remain (file=../../../FactoryGame/Mods/AreaActions/Content/Paks/WindowsNoEditor/AreaActionsFactoryGame-WindowsNoEditor.pak, size=2056928)
LogFileManager: Error: Requested read of 160 bytes when 157 bytes remain (file=../../../FactoryGame/Mods/SML/Content/Paks/WindowsNoEditor/SMLFactoryGame-WindowsNoEditor.pak, size=997408)
LogFileManager: Error: Requested read of 160 bytes when 157 bytes remain (file=../../../FactoryGame/Mods/x3_signs/Content/Paks/WindowsNoEditor/x3_signsFactoryGame-WindowsNoEditor.pak, size=387714182)
[...]
LogWindows: Error: === Critical error: ===
LogWindows: Error:
LogWindows: Error: Fatal error!
LogWindows: Error:
LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000018
LogWindows: Error:
LogWindows: Error: [Callstack] 0x00000000014bc129 FactoryGame-CoreUObject-Win64-Shipping.dll!UE4CodeGen_Private::ConstructFProperty() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp:3959]
LogWindows: Error: [Callstack] 0x00000000014bdaf1 FactoryGame-CoreUObject-Win64-Shipping.dll!UE4CodeGen_Private::ConstructFProperty() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp:4413]
LogWindows: Error: [Callstack] 0x00000000014be979 FactoryGame-CoreUObject-Win64-Shipping.dll!UE4CodeGen_Private::ConstructUScriptStruct() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp:4554]
LogWindows: Error: [Callstack] 0x000000006c08d134 FactoryGame-SML-Win64-Shipping.dll!Z_Construct_UScriptStruct_FSchematicRegistrationInfo() [C:\jnk\workspace\SML2_master\SML\Plugins\SML\Intermediate\Build\Win64\FactoryGame\Inc\SML\ModContentRegistry.gen.c
pp:303]
LogWindows: Error: [Callstack] 0x00000000014bd409 FactoryGame-CoreUObject-Win64-Shipping.dll!UE4CodeGen_Private::ConstructFProperty() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp:4308]
LogWindows: Error: [Callstack] 0x00000000014be567 FactoryGame-CoreUObject-Win64-Shipping.dll!UE4CodeGen_Private::ConstructUFunction() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp:4496]
LogWindows: Error: [Callstack] 0x000000006c08d104 FactoryGame-SML-Win64-Shipping.dll!Z_Construct_UDelegateFunction_SML_OnSchematicRegistered__DelegateSignature() [C:\jnk\workspace\SML2_master\SML\Plugins\SML\Intermediate\Build\Win64\FactoryGame\Inc\SML\Mo
dContentRegistry.gen.cpp:142]
LogWindows: Error: [Callstack] 0x00000000014be6f4 FactoryGame-CoreUObject-Win64-Shipping.dll!UE4CodeGen_Private::ConstructUPackage() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp:4595]
LogWindows: Error: [Callstack] 0x000000006c093564 FactoryGame-SML-Win64-Shipping.dll!Z_Construct_UPackage__Script_SML() [C:\jnk\workspace\SML2_master\SML\Plugins\SML\Intermediate\Build\Win64\FactoryGame\Inc\SML\SML.init.gen.cpp:40]
LogWindows: Error: [Callstack] 0x000000006c082665 FactoryGame-SML-Win64-Shipping.dll!EReflectedPropertyType_StaticEnum() [C:\jnk\workspace\SML2_master\SML\Plugins\SML\Intermediate\Build\Win64\FactoryGame\Inc\SML\BlueprintReflectedObject.gen.cpp:28]
LogWindows: Error: [Callstack] 0x000000000149c0b7 FactoryGame-CoreUObject-Win64-Shipping.dll!ProcessNewlyLoadedUObjects() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectBase.cpp:995]
LogWindows: Error: [Callstack] 0x0000000001430505 FactoryGame-CoreUObject-Win64-Shipping.dll!TBaseStaticDelegateInstance::ExecuteIfSafe() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\Core\Public\Delegate
s\DelegateInstancesImpl.h:731]
LogWindows: Error: [Callstack] 0x000000018020cab6 FactoryGame-Core-Win64-Shipping.dll!TMulticastDelegate::Broadcast() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\Core\Public\Delegates\DelegateSignatureI
mpl.inl:955]
LogWindows: Error: [Callstack] 0x0000000180226907 FactoryGame-Core-Win64-Shipping.dll!FModuleManager::LoadModuleWithFailureReason() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\Core\Private\Modules\ModuleManager.cpp:519]
LogWindows: Error: [Callstack] 0x00000000016480a2 FactoryGame-Projects-Win64-Shipping.dll!FModuleDescriptor::LoadModulesForPhase() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\Projects\Private\ModuleDescriptor.cpp:561]
LogWindows: Error: [Callstack] 0x000000000165a645 FactoryGame-Projects-Win64-Shipping.dll!FPluginManager::TryLoadModulesForPlugin() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\Projects\Private\PluginManager.cpp:1295]
LogWindows: Error: [Callstack] 0x0000000001647ed5 FactoryGame-Projects-Win64-Shipping.dll!FPluginManager::LoadModulesForEnabledPlugins() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\Projects\Private\PluginManager.cpp:1369]
LogWindows: Error: [Callstack] 0x000000014000c472 FactoryGame-Win64-Shipping.exe!FEngineLoop::PreInitPostStartupScreen() [D:\ws\SB-lowprio\UE4\Engine\Source\Runtime\Launch\Private\LaunchEngineLoop.cpp:3250]
LogWindows: Error:

You can see 3 files have some read offset errors.

The game files validates successfully though.

I then uninstalled Satisfactory because I suspected the above files are corrupt, and surprisingly, these files were not removed by the deinstallation process:

steamapps/common/Satisfactory
└── FactoryGame
    ├── Configs
    │   └── SML.cfg
    └── Mods
        ├── AreaActions
        │   ├── AreaActions.uplugin
        │   ├── Binaries
        │   │   └── Win64
        │   │       └── UE4-AreaActions-Win64-Shipping.dll
        │   ├── Content
        │   │   └── Paks
        │   │       └── WindowsNoEditor
        │   │           └── AreaActionsFactoryGame-WindowsNoEditor.pak
        │   └── Resources
        │       └── Icon128.png
        ├── SML
        │   ├── Binaries
        │   │   └── Win64
        │   │       ├── FactoryGame-SML-Win64-Shipping.dll
        │   │       ├── FactoryGame-SML-Win64-Shipping.pdb
        │   │       └── FactoryGame-Win64-Shipping.modules
        │   ├── Content
        │   │   └── Paks
        │   │       └── WindowsNoEditor
        │   │           └── SMLFactoryGame-WindowsNoEditor.pak
        │   ├── Resources
        │   │   └── Icon128.png
        │   └── SML.uplugin
        └── x3_signs
            ├── Content
            │   └── Paks
            │       └── WindowsNoEditor
            │           └── x3_signsFactoryGame-WindowsNoEditor.pak
            └── x3_signs.uplugin

I removed all these files manually, then reinstalled the game with Steam again.

Launched with %command% -vulkan again, with Proton 7.0-1, and now it works :)

(since some people have problems with audio, it works for me flawlessly, with =media-video/pipewire-0.3.48-r1)

I think I have the same issue on AMD ([#3957 (comment)](https://github.com/ValveSoftware/Proton/issues/3957#issuecomment-968154228)). Do you also get a black screen?

No aside from VRR/flipping not working everything else works as expected with Vulkan here. Only tested on Xorg though because Nvidia doesn't support VRR on Wayland yet.

Having a problem on the Steam Deck, where if I try to log in to Epic Online Services, Steam crashes and restarts the console UI. Haven't had any problems when playing solo at least.

For me the game just shows the splash logo, goes black screen and after a few seconds just closes.
Here's the error I found in my clipboard, hope it helps:

Fatal error!

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000018

0x000000000157655f FactoryGame-CoreUObject-Win64-Shipping.dll!UnknownFunction []
0x0000000001577f41 FactoryGame-CoreUObject-Win64-Shipping.dll!UnknownFunction []
0x0000000001578db9 FactoryGame-CoreUObject-Win64-Shipping.dll!UnknownFunction []
0x00000000372ed134 FactoryGame-SML-Win64-Shipping.dll!Z_Construct_UScriptStruct_FSchematicRegistrationInfo() [C:\jnk\workspace\SML2_master\SML\Plugins\SML\Intermediate\Build\Win64\FactoryGame\Inc\SML\ModContentRegistry.gen.cpp:303]
0x0000000001577862 FactoryGame-CoreUObject-Win64-Shipping.dll!UnknownFunction []
0x00000000015789a7 FactoryGame-CoreUObject-Win64-Shipping.dll!UnknownFunction []
0x00000000372ed104 FactoryGame-SML-Win64-Shipping.dll!Z_Construct_UDelegateFunction_SML_OnSchematicRegistered__DelegateSignature() [C:\jnk\workspace\SML2_master\SML\Plugins\SML\Intermediate\Build\Win64\FactoryGame\Inc\SML\ModContentRegistry.gen.cpp:142]
0x0000000001578b34 FactoryGame-CoreUObject-Win64-Shipping.dll!UnknownFunction []
0x00000000372f3564 FactoryGame-SML-Win64-Shipping.dll!Z_Construct_UPackage__Script_SML() [C:\jnk\workspace\SML2_master\SML\Plugins\SML\Intermediate\Build\Win64\FactoryGame\Inc\SML\SML.init.gen.cpp:40]
0x00000000372e2665 FactoryGame-SML-Win64-Shipping.dll!EReflectedPropertyType_StaticEnum() [C:\jnk\workspace\SML2_master\SML\Plugins\SML\Intermediate\Build\Win64\FactoryGame\Inc\SML\BlueprintReflectedObject.gen.cpp:28]
0x0000000001556dc8 FactoryGame-CoreUObject-Win64-Shipping.dll!UnknownFunction []
0x00000000014eaef5 FactoryGame-CoreUObject-Win64-Shipping.dll!UnknownFunction []
0x0000000180206075 FactoryGame-Core-Win64-Shipping.dll!UnknownFunction []
0x0000000180220353 FactoryGame-Core-Win64-Shipping.dll!UnknownFunction []
0x000000000170785b FactoryGame-Projects-Win64-Shipping.dll!UnknownFunction []
0x0000000001719ba6 FactoryGame-Projects-Win64-Shipping.dll!UnknownFunction []
0x0000000001707667 FactoryGame-Projects-Win64-Shipping.dll!UnknownFunction []
0x000000014000c2d9 FactoryGame-Win64-Shipping.exe!UnknownFunction []
0x0000000140008fec FactoryGame-Win64-Shipping.exe!UnknownFunction []
0x00000001400091da FactoryGame-Win64-Shipping.exe!UnknownFunction []
0x0000000140013e37 FactoryGame-Win64-Shipping.exe!UnknownFunction []
0x000000014001485a FactoryGame-Win64-Shipping.exe!UnknownFunction []
0x000000007b61467d kernel32.dll!UnknownFunction

Operating System: Manjaro Linux
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.1.31-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor
Memory: 31,3 GiB of RAM
Graphics Processor: AMD Radeon RX 5700 XT

Satisfactory Update 8 launches and runs fine on Ubuntu 23.10 kernel 6.5.0-10-generic x11 nvidia 545.29.02 using proton 1697712483 proton-8.0-4c.

They added DLSS support but I am only seeing TSR and AMD FSR under Vulkan plus Intel XeSS under DX12. Using PROTON_ENABLE_NVAPI=1 %command% seems necessary to make DLSS available (at least under Vulkan).

@kisak-valve That solved the issue for me, setting in /usr/share/drirc.d/00-mesa-defaults.conf

        <application name="Satisfactory" executable="FactoryGame-Win64-Shipping.exe">
            <option name="force_vk_vendor" value="-1" />
        </application>

Gets the game to load.

Edit:
Created Mesa issue to for fix: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10152

That fix has had no effect for me; the game's log files are essentially identical, with the only differences being the time codes.

Update 8 (up to 0.8.2.7) runs fine for me without a patch. I've not tried tried 0.8.2.9 on linux at the moment.

@Magicalus Not sure if its worth a try, not sure it mattered, but I did also delete my Config folder in the steam compatdata:
{steam folder}/steamapps/compatdata/526870/pfx/drive_c/users/steamuser/AppData/Local/FactoryGame/Saved/Config/

I just deleted my entire compatdata folder for Satisfactory. Twice actually, once when I did it manually, and once when I reinstalled. It did not help.

Hello @kisak-valve, I no longer wish to be the owner of this issue. Would you be able to create a new issue so that I can close this issue and remove it from my issue feed and status?

Thank you,

I got the same problem now on Satis 8.3.
Some mods gets problems with endless log warning:
Warning: SymLoadModuleExW. Error: 6
Debian, Steam, Proton 8

I got the same problem now on Satis 8.3. Some mods gets problems with endless log warning: Warning: SymLoadModuleExW. Error: 6 Debian, Steam, Proton 8

Mod support isn't related to this repo. Best is to get on the Satisfactory Modding Discord and check for announcements, mod updates and the like.

@Ryder17z
The launcher is not even starting (the game is said to start in Steam, then almost directly crashes?), I cannot get debug logs for Proton, here is the parameters in steam, I'm using :

PROTON_LOG=1 PROTON_LOG_DIR=/tmp  %command% -NO_EOS_OVERLAY -vulkan

@Ryder17z
The launcher is not even starting (the game is said to start in Steam, then almost directly crashes?), I cannot get debug logs for Proton, here is the parameters in steam, I'm using :

PROTON_LOG=1 PROTON_LOG_DIR=/tmp  %command% -NO_EOS_OVERLAY -vulkan

All I can recommend then is to try Proton-GE and see if the issue persists

@Ryder17z The game did work on a steam deck it did install something like Visual Studio libraries for UE (Unreal Engine?) something some kind of workaround before and it works but not really well, with a controller, so it can be run but the setup isn't clear under Linux.

@Ryder17z The game did work on a steam deck it did install something like Visual Studio libraries for UE (Unreal Engine?) something some kind of workaround before and it works but not really well, with a controller, so it can be run but the setup isn't clear under Linux.

Your probably thinking of the "Visual C/C++ runtime" stuff which is technically independent from Visual Studio. (I guess this is partly why they call it a "runtime" instead of an "sdk" ?)

@Ryder17z do you have any idea which winetricks would do the trick ? for this visual C/C++ runtime for Unreal Engine ?
I'm not sure why on the steam deck it is automatically installed and on desktop the experience is not the same, hmmm

@Ryder17z do you have any idea which winetricks would do the trick ? for this visual C/C++ runtime for Unreal Engine ?
I'm not sure why on the steam deck it is automatically installed and on desktop the experience is not the same, hmmm

Because Valve tweaks things a lot.

Anyway see: https://www.protondb.com/app/526870 there's several things to try here.

There is also Proton-GE that sometimes works better than regular Proton.

Also: https://github.com/Matoking/protontricks