Crossplay Problems

yehalio

New member
On PS5. Can’t join friends server on PC from console. We made sure crossplay was enabled, max player size was 8, world size was 8196, EAC was enabled, and every bit of advice found online. Searched by both the server name and gamer tag and still no luck. Made sure it wasn’t a dedicated server. Any suggestions?

 
Hi there yehalio, we are having the same issue.  From what we are finding tho, is that crossplay from console to PC from a dedicated server isn't supported yet.  That they are working on it and hopefully it will be ready by Q1 of this year.  We've tried everything on the server side, making sure it's a Pregen 8k, the Navezgane map, crossplay enabled, server is public etc.  The only success we've had, is have the console person fire up a save game on their side and us PC user join them.  (peer to peer) only.

Sorry.

https://7daystodie.com/winter-patch/

posted on 12/7/2024 v1.2

 
Since version 1.3 release I have been having issues connecting to a friends server because of EAC authentication issues. Most of the time get kicked with error code eacauth_known_Invalid - Authentication timed out. I've never had the issue before and nothing has changed, just started after the new update and haven't been able to play since, happens across multiple world and new games no matter the game size.

Anyone encountered this and found a way to fix it?

Tried uninstalling and reinstalling on both ends
Resetting router/modem both ends
Verifying files and licences
Loading old saves/starting new games

 
My friends were able to play on my world(I’m on pc, they are on xbox) until one day they couldn’t. They just get kicked before loading in every time now. This is so frustrating

 
There has been a common issue that creates this problem on all platforms for the past several months.

Multiplayer connections require authentication with EoS. If the clock of your system does not match the clock on the EoS server you are authenticating with, then your return authentication token will not sync.  Basically EoS asks your client for the auth credentials and your client has a limited amount of time to respond. If the timestamp on your response does not match the timestamp of their request then authentication fails and you get kicked for invalid auth.

The fix is to ensure that the clock on your device is 100% synced with internet time. In some cases (Especially with Microsoft products) this requires taking the device offline and doing it manually.

 
Back
Top