Satisfactory - Update 8 - not starting after Update / only Updating application

Technical Support
1

OS Name/Version: Debian 12.2 ; AMP V2.4.6.6

Product Name/Version: Satisfactory 8 ( 0.8.0-CL-264901 )

Problem Description:
The Linux Server binary was renamed from “UE4Server-Linux-Shipping” → “UnrealServer-Linux-Shipping”

`Specified executable '/home/amp/.ampdata/instances/<SATISFACTORY_INSTANCE_NAME>/satisfactory/1690800/Engine/Binaries/Linux/UE4Server-Linux-Shipping does not exist. Updating application…

Steps to reproduce:

  • Update Satisfactory to the latest version Satisfactory 8 ( 0.8.0-CL-264901 )
  • Start Satisfactory via AMP Webgui

Workaround / temporary fix

  • su amp
  • cd ~/.ampdata/instances/<SATISFACTORY_INSTANCE_NAME>/satisfactory/1690800/Engine/Binaries/Linux/
  • ln UnrealServer-Linux-Shipping UE4Server-Linux-Shipping
  • start Satisfactory in AMP Webgui like usual
2 Likes
2

To confirm: you are using the Public/Early Access release stream? Not Experimental?

The devs previously renamed the Experimental binary, looks like the Public/Early Access binary has now caught up.

3

yes confirmed, i am using the Public/Early Access release stream.
The Version 8 was released today in EA.

4

OK, will raise a PR shortly.

5

perfect, thank you very much!

7

Is there an update here yet?

8

AMP Release “Decadeus” v2.4.6.6, built 05/10/2023 11:56 is still the latest version, maybe in the next version, give the devs a bit time :slight_smile:
But if you want, feel free to try the Workaround / temporary fix.
It dosnt modify the original files, just add a filelink with the old name to the new server binary, so AMP should be able to start the server with the old binary name.
You can simply remove this filelink after it will be fixed, but it wont be necessary.

  • su amp
  • cd ~/.ampdata/instances/<SATISFACTORY_INSTANCE_NAME>/satisfactory/1690800/Engine/Binaries/Linux/
  • ln UnrealServer-Linux-Shipping UE4Server-Linux-Shipping
  • start Satisfactory in AMP Webgui like usual
9

Template has already been updated. Right click on the instance, Refresh Configuration. Then manage and update the server

2 Likes
10

confirmed, works fine.
Thank you very much for your fast response & fix! :slight_smile:

1 Like
11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.