Diablo® III

Blizzard why don't you care?

06/06/2013 11:58 PMPosted by OldThunder
I've been playing D3 since late april, HC exclusively as soon as i could. In AUS on Telstra. stable 180-200 ping, haven't had a single D/C. Lost some chars to graphics lockup shortly after 1.08 but that seems to have been resolved.


OH. WELL. Since you've only been playing for 2 months, I'm SURE that it's definitely the player. Ya know, since the rest of us haven't been having problems with DCing for over a YEAR or anything, right?
What about lag spikes when people join games? I lost my 51 wiz while frozen desecrated in mp5... wtf?
although i haven't been playing very long ( few months), i have yet to experience an sort of DC, barring the one time may cat decided to play with my router, but... yeah..
90 Undead Mage
6905
Posts: 30
I have lost two toons due to your lagg issues in HC and its pissing me off, level up just to die to a sever !@#$ up ?
For 2 days now i've been DC'ing and when it does, the D3 launcher and D3 website won't work for a few minutes after. Something very strange is going on. I've had to switch my DH to a complete paranoia build (calamity/3 turrets/6 spiketraps down at all times) just to make sure i survive lag.
They should just remove the 10 second time delay for leaving a game. If they did that, it would prevent so many DC deaths, and it would show they cared. Yet I doubt it will ever happen. I've lost multiple characters to DC, now I'm about to give up on on D3. I'm tired of being robbed of my characters.
@ spirited

While I share your frustration the 10 second timer serves its purpose but cutting it down to 5 would be nice. What they need to fix is the amount of time it takes the server to recognize the client is DCd. Even if the timer is gone if the server still thinks the client is connected you are going to die.

Fixing the server recognition time is the solution. Even if auto pause was implemented the server stills needs to know the client is DCd.

Getting rid of the timer will just allow people to cheat death.

BTW that is one hell of a stable of characters you have there!
Edited by CyLaNt#1337 on 6/14/2013 2:40 AM PDT
Posts: 10,009
View profile
bump lol, i want this to cap
85 Human Priest
3570
Posts: 132
~300 hours on 1.0.8:

Zero game crashes
Zero rubberbands
Poor latency only once, I turned the game off and did something else.
One D/C, which traced back to my network card. Fortunately my Barb survived it.

I don't have an SSD, or a new fast computer.

I do have the latest drivers, I have stressed tested my PC, and I run Razer GameBooster (which I highly recommend).
~300 hours on 1.0.8:

Zero game crashes
Zero rubberbands
Poor latency only once, I turned the game off and did something else.
One D/C, which traced back to my network card. Fortunately my Barb survived it.

I don't have an SSD, or a new fast computer.

I do have the latest drivers, I have stressed tested my PC, and I run Razer GameBooster (which I highly recommend).


Consider yourself lucky then.

Only 2 DC for me. One was a power outage and the other my ISP went down.
D3 stopped responding last week and lost my Barb

This is since I started playing (about 1000 hours). I can live with those odds!
Posts: 1,620
View profile
06/14/2013 02:37 AMPosted by CyLaNt
Fixing the server recognition time is the solution. Even if auto pause was implemented the server stills needs to know the client is DCd.

Implementing the auto-pause system that StarCraft 2 uses would actually help in this case. But let me back up a bit so that this all makes sense.

Per Bashiok, the in-game latency meter is an actual system.

The latency indicator in-game is not a simple ping like most games, and is actually a full process of the game sending an action to the service, the service processing it, and returning it to the client.

Source: http://us.battle.net/d3/en/forum/topic/5235707848?page=3#46

The above is important because this can be interpreted as meaning this is an actual API that is built into Battle.net 2.0; where it is up to each dev team (SC2, WOW, D3) to implement in their client. The StarCraft 2 team has done just that where the game will auto pause once a certain threshold of latency occurs (I'm not sure if WOW has anything like this since I don't play it). I do play SC2 casually though and have experienced the auto pause a few times. If you are in a multiplayer game, the other party will also receive a popup stating that they are waiting for player XXXX. If after a certain period of time (I believe a minute) has passed, the other players can basically decide to have the lagging player removed. If you are playing a campaign or against the AI in a custom map/arcade game, you'll similarly get this dialog box while the game is paused. It's effective and works well.

For D3, that system would work extremely well for single player. Implementing this in co-op play would be an issue though due to the game pace of Diablo.

As far as using this underlying system for disconnects, that again is something that is theoretically much easier to implement in single player. Since the latency meter is an actual system process that knows when higher latency is occurring and auto pauses the game, that system would also have a better measurement of when an actual disconnect has occurred. If server and client are no longer in communication with each other( as in a disconnect situation), it would show up in this system as very high latency. Thus it would auto-pause and be subjected to the same 30 minute AFK disconnect timer; where the server will unpause the game to begin the 10 second countdown timer. This would help to alleviate the current setup where your character is sitting unpaused in-game and it takes the server up to a minute before it even recognizes that a disconnect has occurred before it begins the 10 second countdown. Characters are normally slain during that period before the server actually registers the disconnect.

This can't be abused because the D3 dev team already took care of the ability to pause and then force a disconnect (where after 30 minutes, the server will unpause that session and start the 10 second countdown to remove the player). If you attempt to login again before that 30 minute idle disconnect period has passed, the same thing will occur; the server will unpause your previous game session on the server and start the countdown timer. How quickly you can re-log back in again will be based on what happens during those 10 seconds (if your character survives, the authentication process will look like it is hung for around 6-7 seconds).

tl;dr - This is why I believe the latency meter and underlying process/system mentioned by Bashiok could be used to implement a similar SC2 style autopause on high latency system in Diablo III (at least in single player mode) which could not be abused because they already have the pause/forced disconnect angle covered. For situations where an actual disconnect occurs, the above system will notice the high latency and auto-pause; the character will therefore only be subjected to the 10 second countdown timer since that session will remain autopaused until either the idle timer expires or you attempt to login again.

Yes, I've read about what Travis Day wrote about not enjoying the possibility of losing his character to a disconnect and Wyatt Cheng basically stating he isn't sure how all of this stuff works server side, and how it is complicated to determine if a disconnect is really server side, result of AT&T's carrier routing systems hiccuping, failover failure (it happens), etc. Seriously, there is no need for them to make that determination in the auto-pause on high latency scenario. Rhetorically speaking, what they need to do is get with the Battle.net folks and/or talk to the SC2 dev team to find out how they are implementing their auto pause on high latency system (I know they have higher priority things on their plate which is why I said rhetorically). 2 decades of IT networking has taught me that yes, the application development folks don't always understand the physical/logical (where it is even more voodoo'ish) network side of things.
So I am done, going to go back to D2 until my pre-ordered PS3 version comes out...I am boycotting this game until something is done...I am doing this for the community, because if more of us boycott this...

-Zero


A boycott is an act of voluntarily abstaining from using, buying, or dealing with a person, organization, or country as an expression of protest.

Basically what I'm saying is that if you are "boycotting" then you should cancel your PS3 preorder.
I've played fairly frequently since release and not once have I experienced a DC. Even lag is rare and I only ever get a small amount playing cm wiz.
I've never had a DC, except for this one time they had to do emergency maintenance and I was stuck in the middle of a mob pack, but after re-logging in, I was surprised to see my toon alive. I occasionally see friends or strangers DC but it's not very often. My condolences for your loss and your spotty ISP. I'm a subscriber to comcast (a decent internet provider but poor customer service IMO). When it's storming out, I don't play.

Side note: I'm aware of the fresh game lag issue so i start at a low mp like mp3 and kill a lot of mobs before going higher.
I have never had a car accident, those guys who claimed they did must be lying or are simply too weak to survive one
This topic has reached its post limit. You may no longer post or reply to posts for this topic.

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)

Reported!

[Close]