Love to queue up twice in 40min queues and get a login timeout, very frustrating.
Getting 3 “login timout” in a row while literally at my screen when it says logging in and ready to select a character to hit another 40ish min que is really annoying.
1 Like
You’re a moron. We can’t even get into the damn game to even test it. If this is just a beta to stress test the servers they don’t need to even have a beta. Just invite only the streamers and give them codes for their friends since that’s the only players able to access this trash.
lol yeah I know right!
I have had it timeout on me 4+ times now. Every time being around a 40 minute wait.
I been in queue like 7 times already, every time I got in, I only play for 10 freaking minutes, the got disconnected…
1 Like
If your game is gray you need to turn off HDR in windows.
I love that I had a login que just for the launcher.
Yeah it is a little ridiculous, but it’s a beta with a TON of people from all over the place trying to get on at the same time. I’m not a programmer or anything, but shouldn’t this kind of load been expected or at least wanted from a sales/ bug test point of view? And if so shouldn’t have more servers or cloud space or whatever is used be allocated for it?
try lagofast to get a stabler connection and boost fps
It’s almost as if this was their first beta ever. Always terribly unprepared.
1 Like
The connection for pretty much every one, aside from some streamers, is just trash at the moment. Wait 30 minutes in queue, play for 5 minutes, get D/C.
Someone removed my comment. So here we go again. I worked in QA for gaming companies for 2 years and I gotta say;
Cut them some slack you guys. After all they are a small indie company xD. All joking aside though and in all fairness, 60 minutes for a que time is actually quite generous for one of the most anticipated games over the last 10 years. HOWEVER, it is also demonstrably gross that after 45,55,65 minute wait times people are being timed out, and disconnected to be then sent to the back of the que line. When I worked in QA, if we wanted to “live” stress test, we’d call it that, or call it a live play test. We would not advertise it as the live beta. The BETA is supposed to come when all the stress testing, and regression testing is done. The last step before finalizing and shipping the game. Additionally, even if it were a stress test: If a large portion of our testers were experiencing time out, and disconnect errors, Our priority would be to ADRESS IT, then FIX it. The fact that this has gone on the ENTIRE first day without so much as an acknowledgment is laughable at best, and woefully pathetic if we’re being honest. If this really is the best representation of the finished game, then rushed is an understatement. Need there be a reminder that diablo 4 started development in 2014? THEY HAVE HAD NEARLY 10 ENTIRE YEARS TO STRESS TEST THIS. It’s not giving. If things don’t change fast, the future of Diablo 4, and Blizzard as a company looks bleak. But what do I know, I’m just some dude behind a screen they don’t want posting this.
3 Likes
Waiting for queue < 1 minute … queued … waiting for queue< 1 minute.
Error exiting … waiting for queue 30 minutes…
3 Likes
I got in this morning instantly… THEN I started rubberbanding really badly so I restarted. Put into a start game pending for an hour until it kicked me out and now says my account is locked. Nice.
I wanted to hate your post, but damn…you are absolutely correct. 30 million is a big number, and if it were not Blizzard handling this situation (or Apple-rofl) I can only imagine what month and year a queue would end.
Played last night with no issue (and was actually grateful the queue was only 30 mins after almost 2 hour queues last weekend). Queue times are at or better than expected, but have to agree with others that while I expect to hit a queue on beta/new games, I do not expect or enjoy getting punted once you get to <1 min then being thrown out of the launcher and to the back of the queue (which gets longer each try). I’m on my 4th attempt now having seen this same error 3 times in a row this morning. While I appreciate this is a beta, you can’t test anything if you can’t make it past the login server.
I wanted to hate you, but you made a good point. Living proof that all messengers should not be beheaded just to send a message back to the past.
Issue seems to be fixed? Knocks on wood
I have started a game half a dozen times with no issues now. Thanks Blizzard, luckily I had some faith in you… no matter how miniscule it was lol
Connection timeout while sitting in a 1hr+ que is soooo irritating. Dont want to have to sit and stare at the screen or hold my controller to spin in a circle for an hour… please fix this.
Also annoying when the crap server crashes, kicks you out, and you have to sit through the whole damn que ordeal again. Can we get a 1 or 2 minute reprieve to have a chance to log back in without getting kicked to que? FFS!