[Test Release] Second Nav Test with a lot of combat and other bug fixes

[stevelulwow]

Left the house for about an hour or so, to see what I would come back to.... GUESS WHAT!?










Still running!!!! yeeeeeey

 

[Epics]

Running very nicely here. Fastest so far

 

[Liferose]

The bot is removing and re-adding things from my stash to my inventory with the default item rules in a loop, or it's taking an absurd amount of time so I stopped it.

 

[magusq]

Have a couple of system null exceptions in my log.
And noticed that in core, sometimes it will open a chest, run to a spot, run back to the opened chest and run away.

 

[temhoahreji]

Finally able to use it, 4 days later, but im happy and no lag. thanks!

 

[sparks]

gave this a try and it sure fixed a LOT of my problems.

thanks guys


oh wait its a Hawker thread
ITS ABOUT TIME ROFL

 

[GilesSmith]

Frequently get "Not able to attach... is Diablo 3 running?" error if I've already attached DB once, but closed it then re-opened it (without closing and re-opening Diablo). Didn't do this in past official release (I didn't try the first nav-test release).

 

[BakedGrease]

Here's my latest log. Ran 34 Core runs and it crashed D3 and locked up DB while I went AFK for a bit....


View attachment 2012-06-16 18.50.zip

 

[rizarjay]

So weird. Seems like it's picking up some blues, but not others, leaving 1000+ stacks of gold on the ground randomly..

 

[chronos147]

Frequently get "Not able to attach... is Diablo 3 running?" error if I've already attached DB once, but closed it then re-opened it (without closing and re-opening Diablo). Didn't do this in past official release (I didn't try the first nav-test release).

Same. If you open up your Task Manager you can find all of your DB processes there. I had around 4 when I tried to open up another version. Just kill them all and it should run fine.

 

[Tjann]

Is the GPH in 'Diagnostic" mode bugged by anychance? It says 660k GPH which would be like a 200-250k GPH improvement just sound too good to be true. Will report back later. Will messure it manually and double check.

 

[Toney001]

Frequently get "Not able to attach... is Diablo 3 running?" error if I've already attached DB once, but closed it then re-opened it (without closing and re-opening Diablo). Didn't do this in past official release (I didn't try the first nav-test release).

^ This. Previous version (.103) did it too.
It's pretty annoying... gotta restart D3 half the times I change something within DB that requires me to restart it (like CC or plugin modifications).

 

[Lipie]

Since this version , on the sarkoth profile, when sarkoth spits out loot, he allready ran back to his waypoint and skips a lot of loot, he even lets rares lay down on the floor and just ports back ...

 

[gamingjunkie]

This is not just on Sarkoth, I have ran numerous profiles testing this new build and on everyone they seem to skip loot. I'm not talking about one piece here or there, it's huge stacks of gold and a lot of items. I have tried using various loot rules but they all seem to be doing the same thing.

 

[B3AST]

Make sure you re-chose your loot rules btw, This is working flawlessy bumped my GPH by 200k!

 

[protossop]

Tried this, my guy just runs up to Sarkoth and doesn't attack and dies.

Had to switch back to v.95. Something's wrong with this build.

 

[krangmang]

Aww I had the old Nav Test version doing queen runs on my DH's.... And I'm not home to change!


Will report back.

 

[nucleotides]

So this worked really good for 26 runs it seems.

gph 431903 which is a huge increase from what I had before.

However, during run 27 I got stuck in infinite loot loop.

[00:05:12.007 D] Generated path to <711.1545, 523.5415, 0.6515045> (loot container) with 1 hops.
[00:05:13.471 V] Opening loot container a3Battlefield_Props_Demonic_Container_A-392
[00:05:17.861 V] [Item Rules] Matched Gold with rule: NAME_MATCH_ONLYickUp
[00:05:17.863 V] Blacklisting 7922002C for 00:10:00
[00:05:17.880 V] Opening loot container a3Battlefield_Props_Demonic_Container_A-392
[00:05:18.528 V] [Item Rules] Matched Gold with rule: NAME_MATCH_ONLYickUp
[00:05:18.556 V] Opening loot container a3Battlefield_Props_Demonic_Container_A-392
[00:05:19.202 V] [Item Rules] Matched Gold with rule: NAME_MATCH_ONLYickUp
[00:05:19.222 V] Opening loot container a3Battlefield_Props_Demonic_Container_A-392
[00:05:19.873 V] [Item Rules] Matched Gold with rule: NAME_MATCH_ONLYickUp
[00:05:19.908 V] Opening loot container a3Battlefield_Props_Demonic_Container_A-392
[00:05:20.576 V] [Item Rules] Matched Gold with rule: NAME_MATCH_ONLYickUp
[00:05:20.854 V] Opening loot container a3Battlefield_Props_Demonic_Container_A-392
[00:05:21.500 V] [Item Rules] Matched Gold with rule: NAME_MATCH_ONLYickUp
[00:05:21.520 V] Opening loot container a3Battlefield_Props_Demonic_Container_A-392

Prior to this everything else was running smooth from what I can tell. I had unstucker 2.0 on but I guess it bugged out on me. I'll try to edit my log to be slightly smaller and post it in the morning. I'm beat.

 

[johnd]

So this worked really good for 26 runs it seems.

gph 431903 which is a huge increase from what I had before.

What profile are you using? Im guessing not public?

 

[Toney001]

^ This. Previous version (.103) did it too.
It's pretty annoying... gotta restart D3 half the times I change something within DB that requires me to restart it (like CC or plugin modifications).

I ended up figuring this one out.
It seems like DB doesn't always kill the process on exit, so when you try to open it again, the old process will still be attached.
Until the devs fix this, you can manually kill DB from the task manager to get around it.