i played in windowed mode, havent had a disconnect in a week but then suddenly it started happening again so i switched back to full screen and disconnects became more often, now im back to windowed mode which doesnt seem to solve to problem entirely but it lowers the chance of a disconnect happening
only problem is i think this wont be solved soon because it seems quite complicated and we dont even know if Blizzard has found out what exactly is causing it, let alone how to fix it
Might be worthwhile to look at your setup and see if any drivers need to be updated n such. My previous suggestion still is holding strong so Im thankful for that..but its interesting that different suggestions are/aren't working for certain people..which makes me lean toward hardware.
i played in windowed mode, havent had a disconnect in a week but then suddenly it started happening again so i switched back to full screen and disconnects became more often, now im back to windowed mode which doesnt seem to solve to problem entirely but it lowers the chance of a disconnect happening
only problem is i think this wont be solved soon because it seems quite complicated and we dont even know if Blizzard has found out what exactly is causing it, let alone how to fix it
Same thing happened to me, just started dcing again in full screen windowed
In regards to the disconnects, I have noticed it always happens when I am trying to whirlwind at low fury.my guess is that server lag and the rate at which whirlwind consumes fury causes a desync of the client and server. The client thinks you have enough fury to whirlwind because your tornado just crit , but the server thinks you are out, which causes a game crash when the client allows it.
Yes I also always get it when fury is low. Must be some disagreement between client and server about how much fury you have so your client lets you whirl but then the server says you can't. Of course it really should have just made you rubberband, but I guess them trying to fix rubberbanding introduced a new bug that makes you disconnect? Haven't played sprint/ww before 1.0.4 so no idea if the disconnects are 1.0.4-only or if they existed before. In any case rubberbanding and disconnects seem to happen in the same low-fury situations.
Yes I also always get it when fury is low. Must be some disagreement between client and server about how much fury you have so your client lets you whirl but then the server says you can't. Of course it really should have just made you rubberband, but I guess them trying to fix rubberbanding introduced a new bug that makes you disconnect? Haven't played sprint/ww before 1.0.4 so no idea if the disconnects are 1.0.4-only or if they existed before. In any case rubberbanding and disconnects seem to happen in the same low-fury situations.
Its been around since at least 1.03,which is when it started happening to me, and possibly before that.
What this video missing are two things:
1- Show us how godly your gear is. I suspect you have to use mighty weapon with high enough overall DPS to keep fury generation high and survive. With the new changes, the build becomes very gear dependent.
2- Instead of gathering all monsters together where it is easy to maintain WotB, do a regular farm route and show us if you are able to keep your WotB between packs.
This video is no proof for 'do not fear', the real challenge will be keeping WotB up between packs and the refresh rate of WotB. Sure you can still spin around a large group of monsters, but the real power of current WW spec is that you can keep WotB up %100 with mediocre gear.
its KingKongor he's posted his gear before and has also stated its taken him something like $3000 bucks to get it all.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Might be worthwhile to look at your setup and see if any drivers need to be updated n such. My previous suggestion still is holding strong so Im thankful for that..but its interesting that different suggestions are/aren't working for certain people..which makes me lean toward hardware.
Same thing happened to me, just started dcing again in full screen windowed