Foundry - Failure to launch

[Raptor2213]

Bug Report

System Information

• Operating System: Windows Server 2019
• AMP version and build date: v2.5.0.8, built 02/05/2024 04:53
• Which AMP release stream you're using: Mainline

I confirm:

• [x] that I have searched for an existing bug report for this issue.
• [x] that I am using the latest available version of AMP.
• [x] that my operating system is up-to-date.

Symptoms

• What are you trying to do? - Launch a Dedicated server
• What are you expecting to happen? - Server to launch
• What is actually happening? - Server fails to launch, returns error: Invalid arg 'map_seed=' Error parsing command line.

Reproduction

Create a new instance, start game. Reproducible 100% of the time, regardless of what the map seed value is set to.

Full startup log: 23:33:12 [UnityMemory] Configuration Parameters - Can be set up in boot.config "memorysetup-bucket-allocator-granularity=16" "memorysetup-bucket-allocator-bucket-count=8" "memorysetup-bucket-allocator-block-size=4194304" "memorysetup-bucket-allocator-block-count=1" "memorysetup-main-allocator-block-size=16777216" "memorysetup-thread-allocator-block-size=16777216" "memorysetup-gfx-main-allocator-block-size=16777216" "memorysetup-gfx-thread-allocator-block-size=16777216" "memorysetup-cache-allocator-block-size=4194304" "memorysetup-typetree-allocator-block-size=2097152" "memorysetup-profiler-bucket-allocator-granularity=16" "memorysetup-profiler-bucket-allocator-bucket-count=8" "memorysetup-profiler-bucket-allocator-block-size=4194304" "memorysetup-profiler-bucket-allocator-block-count=1" "memorysetup-profiler-allocator-block-size=16777216" "memorysetup-profiler-editor-allocator-block-size=1048576" "memorysetup-temp-allocator-size-main=4194304" "memorysetup-job-temp-allocator-block-size=2097152" "memorysetup-job-temp-allocator-block-size-background=1048576" "memorysetup-job-temp-allocator-reduction-small-platforms=262144" "memorysetup-temp-allocator-size-background-worker=32768" "memorysetup-temp-allocator-size-job-worker=262144" "memorysetup-temp-allocator-size-preload-manager=262144" "memorysetup-temp-allocator-size-nav-mesh-worker=65536" "memorysetup-temp-allocator-size-audio-worker=65536" "memorysetup-temp-allocator-size-cloud-worker=32768" "memorysetup-temp-allocator-size-gfx=262144" Mono path[0] = 'C:/AMPDatastore/Instances/FOUNDRY01/foundry/2915550/FoundryDedicatedServer_Data/Managed' Mono config path = 'C:/AMPDatastore/Instances/FOUNDRY01/foundry/2915550/MonoBleedingEdge/etc' Initialize engine version: 2021.3.20f1 (577897200b8b) [Subsystems] Discovering subsystems at path C:/AMPDatastore/Instances/FOUNDRY01/foundry/2915550/FoundryDedicatedServer_Data/UnitySubsystems Forcing GfxDevice: Null GfxDevice: creating device client; threaded=0; jobified=0 NullGfxDevice: Version: NULL 1.0 [1.0] Renderer: Null Device Vendor: Unity Technologies Begin MonoManager ReloadAssembly 23:33:13

• Completed reload, in 0.667 seconds 23:33:14 Microsoft Media Foundation video decoding to texture disabled: graphics device is Null, only Direct3D 11 and Direct3D 12 (only on desktop) are supported for hardware-accelerated video decoding. There is no texture data available to upload. UnloadTime: 1.549000 ms Odin Serializer ArchitectureInfo initialization with defaults (all unaligned read/writes disabled). Odin Serializer detected non-white-listed runtime platform WindowsServer; disabling all unaligned memory read/writes. There is no texture data available to upload. 23:33:15 Unloading 5 Unused Serialized files (Serialized files now loaded: 0) UnloadTime: 0.370000 ms 23:33:16 Time until GlobalStateManager.Awake(): 0.002191812s Loading App.cfg Invalid arg 'map_seed=' Error parsing command line. Use -help for a list of available commands. Mods Detected: None ErrorReporter.init() Floating Point Control Bits: _EM_INEXACT|_EM_UNDERFLOW|_EM_OVERFLOW|_EM_ZERODIVIDE|_EM_INVALID|_EM_DENORMAL

[Raptor2213]

Since this was the second dedicated server that failed to launch, and with all the issues with Server 2019, I updated it to 2022, and the server launched without issues. AMP seems to be experiencing issues with 2016/2019 at present.