Satisfactory (526870) #3957
Comments
|
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. |
kisak-valve
added
the
Game compatibility - Unofficial
kisak-valve
changed the title
|
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? |
Relevant logs from game:
|
|
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.
|
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. |
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 You can specify the location of your log file by adding |
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 |
Thanks for this observation, I'll try this out. |
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. |
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
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. |
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;
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. |
|
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. Operating System: Manjaro Linux |
|
Satisfactory crash with recent update to unreal engine Issue transferred from #6849. Compatibility Report
System Information
I confirm:
SymptomsAs i have update my Satisfactoryversion to the newest experimental, the game crash in the initial loading screen Reproduction--> Download Satisfactory experimental latest version and start it with Proton 8. |
|
Hello @jitoxx, these look like some lines of interest from your log: |
|
Seeing the same crash trying the experimental branch with UE update. Looked through log and saw the same error lines as well. System Information |
|
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 |
|
While Update 7 ran fine on my laptop, Update 8 crashes on the splash screen. Here's an abbreviated issue report: Compatibility Report
System Information
ReproductionInstall Satisfactory and run with Proton Experimental. Log: Attached also are two logs from the game: |
|
Decided to test the game since Update 8 came out of experimental, still having same issues as before, reflecting the same as @Magicalus Wonder if this is an Intel Issue DX11 LogFactoryGame.log |
|
Hello @Magicalus, since you're using an Intel GPU and there's XeSS references in the log, you might get lucky adapting https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24194 to this game and seeing if it has an effect. |
|
@kisak-valve That solved the issue for me, setting in Gets the game to load. Edit: |
|
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: |
|
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, |
|
Hello @rwaltr, this is a relatively uncommon request. Go ahead and close this issue report and then the next person who wants to gives feedback on the game run with Proton can open a new compatibility report and we'll continue tracking feedback there. |
|
I got the same problem now on Satis 8.3. |
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. |
|
The game does not launch using Proton Experimental or Proton 8.0-5, using an AMD Ryzen 7 7840U with an AMD Radeon 780M, seems the launcher does even show up on my end, it just crashes, directly. This issue should be reopened @kisak-valve or a new one should be reported. |
It might work if you force vulkan through the launch options. |
|
@Ryder17z |
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. |
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 ? |
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. |
|
Hello, please use #7580 for continued discussion of how this game behaves when run with Proton. Locking per #3957 (comment). |
and others
Compatibility Report
526870System Information
Mesa 19.2.8, LLVM 9.0.05.6.11-200.fc31.x86_64I confirm:
steam-526870.log
Symptoms
When attempting to connect to a friend's session over multiplayer, the actual connection is timed out during initialization. The menu resets and shows a error message indicating that the Unreal component Unet timed out.
Functionality with matchmaking and friend's list appears to be fully functional.
Reproduction
The text was updated successfully, but these errors were encountered: