• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Diablo 3 Retail Client Download Links; Predownload the Installer, Retail and Digital

Page 6 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Status
Not open for further replies.
Its not that you cant play, if you get in you can play. My brother is in just fine. Its just the login box they use probably getting slammed. When thousands of people try to access a machine at the same time, yeah, that could cause problems. 😛
 
Had a couple cool error messages when logging in... besides the normal error 37...

"Player has been disconnected, Error 3005"
and
"Unable to connect to the service or the connection was interrupted, Error 3003"
 
I am now getting an error message saying I dont have Diablo3 in my battle.net account and I just bought it like an hour ago.
 
It's shocking how badly this launch was botched. It's not like it should be a shock to them that they'd have high demand, they know their sales numbers 😛
 
It's shocking how badly this launch was botched. It's not like it should be a shock to them that they'd have high demand, they know their sales numbers 😛

Agreed. What is blizzards defense? "We didn't think everyone who bought a copy of the game would actually want to play it"? They had sales figures, it shouldn't be any mystery as to how many people would be trying to log in at once.

And then they made it worse by allowing all of US in at the same time, spitting on the east coast.
 
It's shocking how badly this launch was botched. It's not like it should be a shock to them that they'd have high demand, they know their sales numbers 😛

* Nods * (without sarcasm, agreed)

They totally didn't have "some time" to prepare for it, nope. They didn't have years, or at least months to prepare for that kind of demand, nah. They didn't have a closed beta AND an open-beta to give them "an idea". They also probably didn't ran "simulations" or had any types of numbers on papers coming out of their brilliant imagination.

I did my part, I paid, I waited. I launched the game, they said AND advertised that it would be live at 00:01 PDT (or 3:01 EST for me). I logged in, it didn't worked. It's that simple. It's a failed launch. It reminds me of ME2's launch on Steam with the Cerberus Network and people having dozens of issues even though BioWare said "we're ready!".

Anyway, I'll keep trying to get in for another ten minutes, if it doesn't work I'll go to sleep. I think I need just that right now.
 
Why do I have the feeling I might as well go to bed now as I am not playing tonight. 😛

I'm about there with you. I'm disappointed, but not really angry. I'm sure it will be plenty of fun when it gets up and running. It's just wild to me that they couldn't figure out how to get the right number of servers up to match their sales numbers.

On a funny note, #error37 is the #1 twitter tag in the world at the moment, and a million variations of the error37 meme are cropping up everywhere. This makes 'took an arrow to the knee' look totally obscure in comparison.

I stayed up late to kind of have a funny moment to share 20 years later when my son is playing World of Diablo 9 or whatever, but I'm sure everyone will remember what I'm talking about when I tell them about ERROR 37!
 
* Nods * (without sarcasm, agreed)

They totally didn't have "some time" to prepare for it, nope. They didn't have years, or at least months to prepare for that kind of demand, nah. They didn't have a closed beta AND an open-beta to give them "an idea". They also probably didn't ran "simulations" or had any types of numbers on papers coming out of their brilliant imagination.

I did my part, I paid, I waited. I launched the game, they said AND advertised that it would be live at 00:01 PDT (or 3:01 EST for me). I logged in, it didn't worked. It's that simple. It's a failed launch. It reminds me of ME2's launch on Steam with the Cerberus Network and people having dozens of issues even though BioWare said "we're ready!".

Anyway, I'll keep trying to get in for another ten minutes, if it doesn't work I'll go to sleep. I think I need just that right now.

Yeap.
 
I get the feeling they decided it wasn't worth dealing with the temporary spike in activity and went with not allowing a larger number of people to connect as their solution.
 
I'm on justin.tv and every single stream is just people sitting at the login/character creation screen hating life, it's hilarious.
 
Played tf2 for an hour, come back, same login probs 😛 - Darmit I wannt play! Blizz must have known there was going to be insane traffic at this time, wonder if they could have prepared better.
 
Quite enjoying it, I can see it sucking up a lot of time.

Shame I'm in the middle of a busy stretch of night shifts so I dont have much time to play. 🙁
 
I broke down and ordered teh digital version from Blizzard, its installing right now. Cuda#1366, I have no idea what I'm doing so add me and lets kill some shit!
 
It's shocking how badly this launch was botched. It's not like it should be a shock to them that they'd have high demand, they know their sales numbers 😛

They don't have enough revenue and didn't have enough time to plan for the launch.

I mean, come on, they only have like a trillion dollars and 10 years.
 
Launches are like a battle. As soon as the first shot is fired, the plans go to the wayside.
 
Sucks there's so many having problems but I have to laugh at my 2 buddies that were "teasing" me because I bought a physical copy from Amazon instead of digitally from Blizzard. I'm going to go out on a limb and say they didn't play at all last night / this morning. 😀
 
Actually, found out part of my initial problem. Some how something from my original beta install didn't get removed when I did the uninstall. So was causing the client to crash constantly. I never even got to the point where I attempted to "log in" to the game. After hours on the phone, I had got to find out how to clean everything out manually from their corrupted beta files.

Then I had to uninstall everything and wait more hours to install again. I got to the 30% point of the install where I could "play" as is. So I launched the client and it started right up finally. Then it was only 20 minutes of trying to log in to the server before it finally let me in about 6am CST. Too bad I had to leave for work.
 
Blizzard could spend a lot of $$$ and massively overshoot the infrastructure needs to meet demand @ launch day, but they never will. They don't need to; they already have your money. People want to play and they'll just wait and keep trying to login. If the problem is indeed just a case of too many people not enough resources it will likely self-correct once the surge dissipates.

It's possible they could undershoot the infrastructure mark so drastically that the queue really becomes unmanageable and can't correct itself, but I don't think they'd do that. I think they know exactly what they're doing. The "line outside the club" may even be partially intended.
 
Status
Not open for further replies.
Back
Top