Diablo® III

WhirlWind Disconnections.

(Locked)

http://pastebin.com/6a6vkY1a
I had this problem, I think the disconnections happened when I would whirl by clicking a mob right next to me causing me to whirl on the spot.
http://pastebin.com/JyxEJevJ

Please help.
Having the same issue.
Alright, I am posting again here since people just ignore the temporary fix.

Use Winowed mode. I have not had a single disconnect since I switched from fullscreen to windowed mode.
^ same
After switching to windowed mode (fullscreen), no more disconnections.
I know this might not help everyone, but worth giving it a try
90 Human Priest
16825
http://pastebin.com/jiaWAJia
just happened to me 10 minutes ago.

Thanks
http://pastebin.com/MbxdQjMG
disconnect :/

Thanks
Ok so I posted 6 days ago that I set my game to windowed full screen and haven't had any disconnects since....until just 2 minutes ago. My first DC since changing the setting. It seems while this helps it doesn't solve the problem 100%. Unless I DC'd for some other reason but I will keep an eye on this. Dang, was headed to Azmodan with 5 stacks...oh well.
really tired of this happening..................
WW is bound to the "D" key on my keboard, which I hold down. I don't click it. Today's disconnect started with rubberbanding, but then it led to a straight disconnect.

Log paste:
http://pastebin.com/TeBY99KV
I think I have a fix for this problem .

1. Click -> Start
2. Click -> All Programs
3. Click -> Diablo III
4. Click -> Diablo III - Uninstall

This should solve all your problems until Blizzard one day decide to actually fix the real problem.
90 Human Priest
16825
I hope they are looking into this issue. Its hard for me to do whirlwind if my cursor is not locked to my game monitor since I use 2 monitors lol. I have a habit of clicking on the other monitor and having my Barb stop and die lol.
First, to those claiming it's a setting... I obviously am not with Blizzard, but I can say with confidence that it has nothing to do with settings, video lag, or anything like that... This is a Client/Server De-Synchronization that's happening. Something doesn't quite line up when the Server and your game client are communicating. Whether it's an expected number, network packet, a skill readiness flag, or something else... SOMETHING isn't matching on one side or the other and the two disagree and viola, you're disconnected. Most of the time it's because of an "anti-cheat" type thing in place that prevents modification of things, such as life numbers, mana count, stat numbers, etc.

Now, to it being related to a specific skill, I don't think that's true either, I don't think it's specifically related to Whirlwind, but more the Generation or Client/Server Synchronization of the amount of Fury available and the process of spending of it.

The reason I say this is because if I watch my fury close enough and be a little more careful about using skills when I don't have enough Fury to do so, I don't get disconnected. (This is very hard to do, mind you, but not at all impossible)

Now, if I run around purposefully holding down WW (and even using it to generate Fury) whenever possible and mashing on Sprint, (More than normal) I get disconnected before I get to 5 stacks of NV, guaranteed. Basically, purposefully spending Fury, AS MUCH as possible and as often as possible, can cause this to happen on a regular basis.

The reason, I believe it's happening more specifically with WW, is because WW is a "constant" drain on Fury, and the server and client both expect it to drain at a certain rate.

I'm going to give an example... you're using Sprint and WW... Now, we know that Sprint takes 20 Fury, we also know that WW takes 16... so between the two, it's 36 Fury... Now, your game client thinks you have 35 Fury, the Server thinks you have 36... the WW will continue because you're in the middle of it, it then happens to come down to Sprint... your game client says "no" to Sprint, but the Server says "yes" to it and adjusts your speed accordingly, now you're out of sync, and your movements are no longer registering as expected... Or vice versa... your client thinks 36 and the server thinks 35 Fury is available... your client says "yes" to Sprint, server says "No" and again you've moving at an "unexpected" rate...

This is just one example... There's MANY possibilities here... I'm not saying this is what's happening, but it definitely seems like a Fury Generation/Spending/Synchronization problem.

If there were another skill that used Fury in the same manner, we'd probably have the same issue here. But none of the other Barbarian skills use the same "drain" type of Fury spending, so there's no way to fully test the theory from a "normal" client...

I suggest to the developers to look at the following algorithms and checks/balances: Fury Generation, Fury Client/Server Synchronization, and the Anti-Cheat/Hack code you have in place for it.

My personal guess is that it's some form of Anti-Cheat/Hack thing in place that is SUPPOSED to disconnect the client when it's detected. (For example, trying any of the packet related hacks in Diablo 2 will immediately disconnect you from the game) And somehow we're tripping it by like trying to spend "too much" fury, and the client succeeds in spending it while the server fails. (or vice versa) Thus de-synchronizing and ultimately disconnecting said client.
Edited by Migs#1845 on 9/11/2012 5:07 PM PDT
@Migs

A lot of what you say makes sense and I agree with it. I only speak from experience when I said that going to full screen windowed mode helped me immensely. I didn't DC for 6 full days where as before I would DC every day 1-2 times losing NV in the process.

I'm guessing this isn't an easy bug to catch or to replicate but I know they must be taking the feedback here and providing it to the developers for review. So everyone who keeps getting DC'd continue to post your pastebin links!
85 Orc Mage
0
having the same problem for about 2 weeks. it makes me want to kill myself.
90 Human Death Knight
16375
This is getting absolutely ridiculous. This bug has been reported and logged and tons of info has been given. We need a fix for this. Sooner, rather than later. This thread is a month old. This is game breaking. Why should I keep playing? I'd rather eat glass at this point.
Yes, what Migs wrote is spot on.

Blizzard should read it.
Started playing again with 1.0.4

Started playing ww barb and started having this issue daily.

Found this thread today.

http://pastebin.com/gRsNfhxA
the same here same issue.
I won't post this data because there are too many ppl doing it already, just came here because its happening to my WW Barbarian. Looks like Blizzard found a way to nerf this spec :P just kidding
This topic is locked.

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)
Submit Cancel

Reported!

[Close]