| Field | Value |
|---|---|
| Operating System | Linux - Debian GNU/Linux 12 on x86_64 |
| Product | AMP ‘Callisto’ v2.5.1.8 (Mainline) |
| Virtualization | QEMU_KVM |
| Application | Satisfactory |
| Module | GenericModule |
| Running in Container | No |
| Current State | Stopped |
I tried this solution, but it appeares tha this was already changed in my case.
When they released 1.0 they changed the exe file name again. On Windows it’s currently FactoryServer.exe but I’m not sure what it is on Linux at the moment. When I’m done working for the day I will get an exact file name and directory that you can change for both windows and Linux.
It looks like on Linux its FactoryServer-Linux-Shipping
I tried it but still the same issue. I wonder if they changed something else aswell.
change it to
App.ExecutableWin=1690800\Engine\Binaries\Win64\FactoryServer-Win64-Shipping.exe
App.ExecutableLinux=1690800/Engine/Binaries/Linux/FactoryServer-Linux-Shipping
make sure you shut down the instance before editing it (as in shut it completely down, not just the app but the whole instance) then when you start it up hit the start button and its going to verify the game files again and then will start the server up. also case is important so dont do any lower case where i have uppercase or it wont work.
ok, i was still unable to connect to my own server but after checking out the satisfactory qa site, you need to remove -MultiHome={{$ApplicationIPBinding}} from the App.CommandLineArgs line
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
