I've been getting random DC's the past couple days, always while doing WW. Is there any fix. It caused a party member of mine to get booted twice last night too. thanks
If you are in software developpment,it should be easy to grasp DC or dc'ing= disconnecting from the server in this context in others on the general internet, it means i dont care as well.
I did experience some lag while using WW. It causes some extensive rubber banding. You get desynchronised from the server and come back to an earlier position(=rubber banding). Is there anyway to stop the animation on female barbs " i got hurt" thats annoying as hell. Losing 1/4 of a second everytime. That kind of problem with tornadoes is to be expected... From a programmer point of view, the collision are harder to determine, and as it happens fast, the tornadoes might trigger the minimum response time from player based action to prevent game inconsistency= thats why you are getting booted.
This happens to me usually at the same areas, the long bridge before siegebreaker and the keep levels, i cant remember this happening after the siegebreaker all the way to azmodan.
I usually pick the kill siegebreaker quest, start at stone fort and do both areas on the roof, take WP to kill the siegebreaker, go all the way to azmodan, then backtrack from the WP before siegebreaker until the end of bridge, port, do the keep levels, most of the time i don't DC, but if i do, it usually happens in the areas i go to after doing azmodan.
The best farm route for me is stonefort and siegebreaker till end of act anyways, so if i DC after that its not biggy.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I did experience some lag while using WW. It causes some extensive rubber banding. You get desynchronised from the server and come back to an earlier position(=rubber banding). Is there anyway to stop the animation on female barbs " i got hurt" thats annoying as hell. Losing 1/4 of a second everytime. That kind of problem with tornadoes is to be expected... From a programmer point of view, the collision are harder to determine, and as it happens fast, the tornadoes might trigger the minimum response time from player based action to prevent game inconsistency= thats why you are getting booted.
I usually pick the kill siegebreaker quest, start at stone fort and do both areas on the roof, take WP to kill the siegebreaker, go all the way to azmodan, then backtrack from the WP before siegebreaker until the end of bridge, port, do the keep levels, most of the time i don't DC, but if i do, it usually happens in the areas i go to after doing azmodan.
The best farm route for me is stonefort and siegebreaker till end of act anyways, so if i DC after that its not biggy.