avrignaud

Update: For those who might hit this, it looks like the issue was that I wasn't running the latest server version (32.12). This was a surprise since the batch file that launches the server checks for an update first. However, it looks like it doesn't pause and let that update finish - it launches the check, then launches the server immediately after. And I'm guessing the server running causes the update process that's already happening in background to fail. Simply updating server manually, then running the server fixed everything.

As title says, just received an update to ARK Survival Ascended on Xbox, and I can no longer connect to my previously working dedicated server. The only thing I can think of is that the "Xbox Only Online Servers" checkbox option is checked, but the whole field is also greyed out so I can't uncheck it (and hence be able to see PC dedicated servers). Anyone else have this happen to them, or have any ideas on how to fix? Thanks!

[EDIT - IGNORE THIS POST. It turns out -crossplay is enabled by default on ASA, so my issues were something different. I would normally just delete this post but don't see the option.] So I went through some crazy explorations trying to fix this - the answer is simple but insane: Add -crossplay to the very end of your server launch string. I started by using this guide: https://hub.tcno.co/games/asa/dedicated_server/ In it is the (broken) launch command, as I'll list below (used in the launch batch file): start server\ShooterGame\Binaries\Win64\ArkAscendedServer.exe TheIsland_WP?listen?SessionName=<SERVER_NAME>?ServerPassword=<password>?ServerAdminPassword=<ADMIN_PASS>?Port=7777?QueryPort=27015?MaxPlayers=32 -NoBattlEye THE STRING ABOVE WILL NOT WORK. My server would not appear in the Unofficial tab of the server list on my Xbox. Simple adding -crossplay at the end of the string fixed it, ie: start server\ShooterGame\Binaries\Win64\ArkAscendedServer.exe TheIsland_WP?listen?SessionName=<SERVER_NAME>?ServerPassword=<password>?ServerAdminPassword=<ADMIN_PASS>?Port=7777?QueryPort=27015?MaxPlayers=32 -NoBattlEye -crossplay You must add it at the very end (and yes, I know that seems insane). I originally had it in front of the -NoBattlEye and it failed. Moving it to the end immediately caused my server to be available within the Xbox client (though I had to search for the name and refresh a few times). Hope that helps!