Will Satisfactory 1.0 Work On AMP Immeditely?

Hello! In a few days Satisfactory 1.0 comes out and makes a ton of tweaks to their dedicated servers. They are changing what ports are being used and changing them to use both TCP and UDP. They are making changes to their application itself allowing it to be ran as a window and console application. They are also changing many of the game settings that can be applied in the AMP config page. When 1.0 comes out on the 10th and I restart the sever so it updates, will everything work automatically? Or will I have to manually change what ports are being used or do I have to wait until AMP themselves modifies the files for the Satisfactory server for it to work with 1.0? Or does it automatically pull the newest dedicated server files from steam or something of the like? If AMP has to manually do it how long does that take? Thanks!

6 Likes

Great Question! I am also interested! If AMP canā€™t implement it directly, you can start local and then transfer it later.

1 Like

Thanks, my thoughts exactly.

+1 update will be today still no respons :frowning:

Probably? Thereā€™s no way to know that for certain - depends on how much has changed. But I donā€™t anticipate that youā€™d have to do anything other than hit update within AMP and carry on as normal.

3 Likes

Awesome, thank you very much.

Server is not updating :frowning:

1 Like

I installed the server on a new Instance there it looks like its updated but it can not start anymore

6 Likes

same here, just get a bash and it does not Start at all.

3 Likes

Can confirm the same issue as mentioned above. On start up, verify games files then quits.

ā€œSteamCMD12:01:14
Redirecting stderr to ā€˜/home/amp/Steam/logs/stderr.txtā€™
Logging directory: ā€˜/home/amp/Steam/logsā€™
[ 0%] Checking for available updatesā€¦
12:01:15
[----] Verifying installationā€¦
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1721172922
ā€“ type ā€˜quitā€™ to exit ā€“
Loading Steam APIā€¦OK
force_install_dir ā€œ1690800ā€
12:01:16
Connecting anonymously to Steam Publicā€¦OK
12:01:17
Waiting for client configā€¦OK
Waiting for user infoā€¦OK
app_update 1690800 -beta public validate
Update state (0x5) verifying install, progress: 0.46 (19922944 / 4303569976)
12:01:19
Update state (0x5) verifying install, progress: 25.86 (1113060804 / 4303569976)
12:01:21
Update state (0x5) verifying install, progress: 58.18 (2503693837 / 4303569976)
12:01:23
Update state (0x5) verifying install, progress: 90.74 (3905011865 / 4303569976)
Success! App ā€˜1690800ā€™ fully installed.
quit
12:01:24
bashā€

2 Likes

yes, can also confirm it closes upon update.

1 Like

Can confirm the behaviour too, from what i got they made quite big changes to the servers.

Would it be possible that there is a problem with ā€œServer Release Streamā€ in the SteamCMD and Update" section on AMP? I mean, the list show ā€œPublic/Early Accessā€ or ā€œExperimentalā€. Should there be another option called ā€œReleaseā€ or something? Iā€™m just trying to find clues too.

Just for more awarenes, Iā€™m having the same issue.
When trying to start, it verifies and updates the game, then the console just says QUIT

My guess is that the new executable is missing a dependency from the Docker container. Does anyone know where the Docker containers live? Are they publicly accessible?

Oh, I found them, and it looks like someone commited a change 23 minutes ago to update the Satisfactory server to 1.0:

Idk how to get that update thoughā€¦

Ah, I found it! They posted on Discord about it:

I can confirm that after following those steps, I can make a new instance of the server!

For those without discord:

Satisfactory 1.0 was released today, and we just merged the changes needed to get the latest changes! To get them on your system follow these steps:

For new instances - Search in the top right of AMP for Repo and click the Fetch button and make a new instance.

For existing instances - Update the instance from the main ADS screen and choose to update the Template if prompted. Also update inside the instance to get the latest game version.

2 Likes

Looks like Iā€™m getting an update loop when trying to install 1.0

 Update state (0x5) verifying install, progress: 0.19 (8388608 / 4303607233)

18:24:50

 Update state (0x5) verifying install, progress: 25.42 (1094060750 / 4303607233)

18:24:52

 Update state (0x5) verifying install, progress: 60.32 (2596138794 / 4303607233)

18:24:54

 Update state (0x5) verifying install, progress: 95.67 (4117337996 / 4303607233)
Success! App '1690800' fully installed.
quit

18:24:55

bash
18:24:55

SteamCMD
18:24:55

Redirecting stderr to '/home/amp/Steam/logs/stderr.txt'
Logging directory: '/home/amp/Steam/logs'
[  0%] Checking for available updates...

18:24:58

[----] Verifying installation...

18:24:59

UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1726088194
-- type 'quit' to exit --
Loading Steam API...OK
force_install_dir "1690800"

18:25:18

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
app_update 1690800 -beta public validate

18:25:19

 Update state (0x5) verifying install, progress: 0.27 (11534336 / 4303607233)

18:25:21

 Update state (0x5) verifying install, progress: 30.28 (1303301051 / 4303607233)

18:25:23

 Update state (0x5) verifying install, progress: 65.30 (2810270802 / 4303607233)

18:25:24

Success! App '1690800' fully installed.

18:25:25

quit

18:25:26

bash
18:25:26

SteamCMD
18:25:33

Redirecting stderr to '/home/amp/Steam/logs/stderr.txt'
Logging directory: '/home/amp/Steam/logs'
[  0%] Checking for available updates...

18:25:37

[----] Verifying installation...
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1726088194
-- type 'quit' to exit --
Loading Steam API...OK
force_install_dir "1690800"

18:25:38

Connecting anonymously to Steam Public...

yes getting the same error