Original Post — Direct link
over 4 years ago - /u/ChrisGansler - Direct link

Hey guys. We are aware of the issue and our team is working on a fix. We have seen some players saying that restarting the game will fix this. I know this is a bit painful for PC players that might receive an ECHO when trying to login again.

Can a console player maybe confirm if restarting the game or logout / login will help?

over 4 years ago - /u/ChrisGansler - Direct link

Originally posted by AndrewJacksonsGat

I signed out/in did not not work

Thanks!

over 4 years ago - /u/ChrisGansler - Direct link

Originally posted by QQboby

Relog did not work for me, fast travel to another place then back to the safehouse fixed it for me however.

Thanks for that. I'll add that as another workaround.

over 4 years ago - /u/ChrisGansler - Direct link

Originally posted by jm2054

Are we safe to play on console? It won't be taken down due to early release will it?

You're good to go.

over 4 years ago - /u/ChrisGansler - Direct link

Originally posted by [deleted]

[deleted]

Because it requires a new server build I'm afraid. The fix also is not as simple as it might seem. The team here is working on it.

over 4 years ago - /u/ChrisGansler - Direct link

Originally posted by alfiesred47

It wouldn’t work for me, I went off to do something else, died and respawned - then it worked. Maybe the reload was the trigger. I didn’t quit/restart at all

It basically needs you to find a server instance that is not borked. How you get there is pretty much not important, re-logging and fast travelling should just do server instance transfers.

over 4 years ago - /u/ChrisGansler - Direct link

Originally posted by [deleted]

[deleted]

I see a lot of confusion around this and we'll see if we can get more clarification on the intent. Keep in mind that we sometimes make changes that not everybody will like but that are part of a bigger revamp.