void lynx
As an old qa i want to say something. maybe they don't realize how the game is not working at all. I am also a developer, and i know these situations but I don't understand why. Haven't they tested? Why that rush for go online. You can wait until the game ready for big changes and try in that.
jolly ibex
yea, I am having the same problem. I do not see a lot of people with this problem though, makes me wonder if @atomic cobalt even knows about it.
void lynx
yea, I am having the same problem. I do not see a lot of people with this proble...
yeah. because of this i sent this ss'. In the game, chat was working and other users game works fine. I hope they are going to fix these issues.
keen root
As an old qa i want to say something. maybe they don't realize how the game is n...
There are multiple platforms and multiple machine types. It’s no excuse, but they probably did not thoroughly test it on the machines/platforms that are producing this issue. As for this specific issue, I have the exact same problem, and have exchanged a few PMs with @atomic cobalt about it already. They think that it is likely a client update that is needed to fix this, and it is lower priority than fixing cloud/server issues such as matchmaking. Honestly, I think the match making could potentially be at least partially a client-side issue, and I hope they are looking at this stuff from every angle.
As for why it wasn’t tested adequately, then migrated in regimented portions of users for validation of production readiness, who knows. My best guess (and purely a guess) is that they thought there would be no issues (aside from data transfer) with simply swapping out the backend connections… then simply failed to plan… then ran out of time, as they are no longer with their old provider. Sounds like there was little to know overlap between new provider and old provider.