Satisfactory - Latest Experimental Version Not Starting

OS Name/Version: Debian 4.19.282-1

Product Name/Version: AMP 2.4.4.0

Problem Description:
The public build installs and runs correctly but when I switch to the new experimental build, starting the server causes it to run a SteamCMD validation of the install files twice which exits successfully but the server does not attempt to start. This is what I see in the logs each time I press start:

SteamCMD
Redirecting stderr to '/home/amp/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1685487853
-- type 'quit' to exit --
Loading Steam API...OK
force_install_dir 1690800
Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
app_update 1690800 -beta experimental validate
Update state (0x5) verifying install, progress: 0.02 (1048576 / 5228545187)
Update state (0x5) verifying install, progress: 8.13 (425083678 / 5228545187)
Update state (0x5) verifying install, progress: 19.42 (1015287488 / 5228545187)
Update state (0x5) verifying install, progress: 29.74 (1554730790 / 5228545187)
Update state (0x5) verifying install, progress: 39.97 (2089867400 / 5228545187)
Update state (0x5) verifying install, progress: 49.12 (2568292851 / 5228545187)
Update state (0x5) verifying install, progress: 58.82 (3075335465 / 5228545187)
Update state (0x5) verifying install, progress: 71.21 (3723383396 / 5228545187)
Update state (0x5) verifying install, progress: 84.91 (4439605605 / 5228545187)
Update state (0x5) verifying install, progress: 98.41 (5145369809 / 5228545187)
Success! App '1690800' fully installed.
quit

Redirecting stderr to '/home/amp/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1685487853
-- type 'quit' to exit --
Loading Steam API...OK
force_install_dir 1690800
Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
app_update 1690800 -beta experimental validate
Update state (0x5) verifying install, progress: 0.12 (6291456 / 5228545187)
Update state (0x5) verifying install, progress: 9.09 (475436158 / 5228545187)
Update state (0x5) verifying install, progress: 22.69 (1186427372 / 5228545187)
Update state (0x5) verifying install, progress: 36.02 (1883420920 / 5228545187)
Update state (0x5) verifying install, progress: 49.44 (2585252385 / 5228545187)
Update state (0x5) verifying install, progress: 62.80 (3283468224 / 5228545187)
Update state (0x5) verifying install, progress: 76.63 (4006765713 / 5228545187)
Update state (0x5) verifying install, progress: 90.75 (4744963217 / 5228545187)
Success! App '1690800' fully installed.
quit

Steps to reproduce:

  • Create a new Satisfactory Instance
  • In Configuration → SteamCMD and Updates → Select ‘Server Release Stream’ of ‘Experimental’
  • Trigger an Update
  • Press Start

Actions taken to resolve so far:
Recreated instance from scratch, restarted AMP, ensured AMP was up to date. Noted that using the ‘Public’ build everything works as expected.

The name of the server binary was changed with the Experimental build.

To get around this:

Stop your instance. Open ADS’s file manager, find your Satisfactory instance, edit GenericModule.kvp, and change the following line:

App.ExecutableLinux=1690800/Engine/Binaries/Linux/UE4Server-Linux-Shipping

to

App.ExecutableLinux=1690800/Engine/Binaries/Linux/UnrealServer-Linux-Shipping
3 Likes

Thank you so much for the quick reply. I can confirm this works!

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