4 ms·
Diablo 3 was pretty horrible at first too for the same reason. I don't know if you will call that a success or failure though.
by cnlwsu 14y ago
Diablo 3 was pretty horrible at first too for the same reason. I don't know if you will call that a success or failure though.
- Bockit 14y agoAnecdotally, I still have people dismiss Diablo 3 over the connectivity issues at launch, and make error 37 comments. Even from people who played through the issues and stuck around for a bit, it's the thing that stands out most for them. Success or failure depends on your definition of success here. Successful game, sure. Successful sequel to Diablo 2, it doesn't seem to have the same popularity, and I think the connection issues at launch framed a lot of people's opinions about the game.
- gambiting 14y agoI've had Diablo 3 since day one and played successfully to level 60 with two characters, never had any problems with connection. And SimCity doesn't work sometimes - it just doesn't work at all.
- scarlson 14y agoYou weren't playing Diablo 3 at release then. Give EA time and Sim City will stabilize as well as D3 has, either because they've expanded hardware, or shrunk their user base.
- gambiting 14y agoWell I was. But my point is that it was a hit-or-miss. I managed to play without problems but I had friends who could not connect. SimCity is not like that. SimCity just does not work at all.
- degenerate 14y agoOn the flip side, I've had friends playing simcity just fine. So, yeah.
- eswangren 14y agoBS. I was on at midnight release night. No one could play reliably. It was hit or miss for a week after that. Besides, the game itself was ruined by the AH and the RMAH, regardless of whether or not the servers were holding up.
- jpalacios 14y agoHaha thanks for reminding me about the error 37 video by francis. Classic! I remember that error lasting for several days after launch.