DB 220 Freezing on [Stuck Handler]

[MewB5V37]

Every time the [Stuck Handler] gets called, I get a 1-2 second freeze in the game. Immediately following DB CPU usage falls to 0 and D3 usage drops by at least half and sometimes to 1. Following is an exerpt from the log at the moment it is frozen:

[22:43:09.982 N] Debug1: Combat repeater part 9
[22:43:09.982 D] [Stuck Handler] We're stuck at <644.931, 831.4777, 20.1>
[22:43:09.990 D] Navigator.Clear

Full logs attached. Some of these were with diagnostic runs by Giles to see if the problem was with his plugin as I was seeing it a lot during combat. It was happening every 3 seconds in combat when my CMWW was spamming spells but not moving. The game would also freeze when the stuck handler was called outside of combat.

 

[Tony]

remove the plugins from your installation and give it a try

 

[MewB5V37]

Hi Tony. I did as you asked, even though I knew what the result would be.

Still FREEZES every time [Stuck Handler] is called. In the attached log, there were 2 calls of the stuck handler and the game and DB froze both times.

Please have this fixed.

I will now reenable my plugins that actually make DB usable (lags like hell in combat without them).

One other thing you may notice in the log. When booting it calls my system an AMD64...uhm..I have an I7

 

[GilesSmith]

Hi Tony/MewB

At the moment, EVERY time DB's built in unstucker decides you are stuck, it does this;

1: Loop through a 360 degree radius around your character.
2: For every XX degrees (5-10 or so), raytrace a line away from your character.
3: Once a line is found that it might be possible to move along, load up every single unit in Diablo 3 memory, and see if any of them intersect your path (with no check on direction - so if it's a large tree/large monster at point blank range, it will be considered as "Blocking your path" in every single direction - even if you can move away from it directly).
4: If it finds a line that is raytracable and not blocked, it does something (returns a location found to some routine in DB?)

Beyond that, DB may then try and find a new path using path-finding to a next waypoint (I couldn't work out where it goes from there).

Unfortunately, at the moment, the built-in unstucker is not editable, not changable, and no way to interface with it - so if you are stood still in combat for a length of time (particularly with my combat replacer which "holds onto" DB's attention while spamming rapid fight attacks), then the moment combat with a current target ends, unstucker decides to try and unstuck you and causes a large freeze - even if there may be other targets to move onto.

I've made a request to edit this behavior on the developer forums here;
[url]http://www.thebuddyforum.com/demonbuddy-forum/developers/66371-request-built-db-unstucker-can-we-replace-disable-interface.html[/url]

Since built in behavior in DB that can over-ride and interfere with the activities of plugins with no way to disable or alter it is "A Bad Thing" (in my opinion), and in this case is doing something bad anyway.

 

[Tony]

Hi Tony/MewB

At the moment, EVERY time DB's built in unstucker decides you are stuck, it does this;

1: Loop through a 360 degree radius around your character.
2: For every XX degrees (5-10 or so), raytrace a line away from your character.
3: Once a line is found that it might be possible to move along, load up every single unit in Diablo 3 memory, and see if any of them intersect your path (with no check on direction - so if it's a large tree/large monster at point blank range, it will be considered as "Blocking your path" in every single direction - even if you can move away from it directly).
4: If it finds a line that is raytracable and not blocked, it does something (returns a location found to some routine in DB?)

Beyond that, DB may then try and find a new path using path-finding to a next waypoint (I couldn't work out where it goes from there).

Unfortunately, at the moment, the built-in unstucker is not editable, not changable, and no way to interface with it - so if you are stood still in combat for a length of time (particularly with my combat replacer which "holds onto" DB's attention while spamming rapid fight attacks), then the moment combat with a current target ends, unstucker decides to try and unstuck you and causes a large freeze - even if there may be other targets to move onto.

I've made a request to edit this behavior on the developer forums here;
http://www.thebuddyforum.com/demonb...stucker-can-we-replace-disable-interface.html

Since built in behavior in DB that can over-ride and interfere with the activities of plugins with no way to disable or alter it is "A Bad Thing" (in my opinion), and in this case is doing something bad anyway.

ok,we will check that

 

[MonsterMMORPG]

stuck handler also causing me problem

[03:17:13.688 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[03:17:13.698 D] Raycast path generated.
[03:17:13.698 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[03:17:15.748 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[03:17:15.778 D] Navigator.Clear
[03:17:17.328 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[03:17:17.338 D] Raycast path generated.
[03:17:17.338 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[03:17:19.368 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[03:17:19.398 D] Navigator.Clear
[03:17:20.938 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[03:17:20.958 D] Raycast path generated.
[03:17:20.958 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[03:17:22.988 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[03:17:23.018 D] Navigator.Clear
[03:17:24.558 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[03:17:24.578 D] Raycast path generated.
[03:17:24.578 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[03:17:26.558 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[03:17:26.578 D] Navigator.Clear
[03:17:28.118 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[03:17:28.138 D] Raycast path generated.
[03:17:28.138 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.
[03:17:30.118 D] [Stuck Handler] We're stuck at <2971.25, 2861.25, 23.94533>
[03:17:30.168 D] Navigator.Clear
[03:17:31.718 D] Generating path to Moving to use waypoint - <2981.259, 2836.146, 24.89399>
[03:17:31.728 D] Raycast path generated.
[03:17:31.728 D] Generated path to <2981.259, 2836.146, 24.89399> (Moving to use waypoint) with 1 hops.