Call of Duty: WW2 has been having one of the roughest launches in recent memory, and today’s patch was supposed to smooth things over.
Unfortunately, this did not happen. The patch, released earlier today for Call of Duty: WW2 players on PS4, and Xbox One, contained connectivity fixes and a few balance changes.
After downloading the patch, players started running into all kinds of problems. Some have been getting disconnected from matches with the listen server error, while others were unable to connect at all after getting a different variant of the ol’ 103295 error.
The majority of reports on Reddit, however, are of players unable to start a match. Our very own Matt Martin has been sitting in the lobby screen for a while.
Developer Sledgehammer Games has yet to officially acknowledge the problems, but the official Twitter for Activision Support confirmed that work is underway to find a fix. This was over seven hours ago, though. The most recent update reiterated that the work continues.
We're working to resolve the issues from earlier this morning, stay tuned for updates
— Activision Support (@ATVIAssist) November 10, 2017
Hopefully these problems will be resolved before the weekend, otherwise it would be the second weekend in a row for Call of Duty: WW2 to have severe server problems.
Update: Sledgehammer continues to work on the issues and have released the following updates:
#CODWWII MP connectivity improved from earlier, but dedicated servers are currently off-line. Expect normal P2P performance including host migrations. We'll be sharing updates throughout the day on current status.
If you have a support request, please reach out to @ATVIAssist.
— Sledgehammer Games (@SHGames) November 10, 2017
#CODWWII Game Update: While we restore dedicated server support, we’re taking Gamebattles integration offline until functionality is restored.
Look for another server status update soon.
— Sledgehammer Games (@SHGames) November 10, 2017
Today’s Call of Duty: WW2 patch screwed things up big time [Update] posted first on http://ift.tt/2k0LiGW
No comments:
Post a Comment