[Beta] Demonbuddy daily beta builds

nesox do you consider the current state of the dungeon explorer to be working or even usable?

i just spent the last hour testing icefall caves and caverns of frost in fields of slaughter, and it still fails to find the exit to level 2 on occasion, despite having a boxsize and tolerance that allows a path there. if youre not familiar with them, these 2 dungeons are quite small and linear.

ive just completely given up on things like keep depths, in addition to experiencing the same issue as above (not finding the exit), even if you do use some kind of workaround (like tp if you dont find the exit) it always spends at least half the time in there backtracking over already discovered areas.

ive spent so many hours testing (all kinds of sizes and tolerances in addition to viewing them in the map viewer) across every release/beta build that involves anything to do with the dungeon explorer, but the same issues i experienced when i first started testing still exist today.

if you do read this and reply, thanks in advance.

 

game freeze with the latest beta

 

Demonbuddy freezes when Starting from .64 and .66 betas :S

 

it doesnt explore enough. when writing the post up i was going to compile a screenshot of the map in game, and the map in the mapviewer as well as the settings i had used but the mapviewer decided to not respond. ill start up a bot and run it until it fucks up again and get back to you with that and ill pm you the profile.

 

Did you give it a blanket?

 

Can you solve disconnect when identifying items issue?? I really hate it. Disconnects every second or third town run!

 

If you want "stable", you should use the ordinary build. For me, currently the latest beta is running all trough the night flawlessly so theres not a case for the post-54 being unstable, its just you and some others. Ill bet alot have no trouble like me. And thats the problem with guys like you. How can Nesox get good feedback on latest build when you keep going back to whatever you believe to be the most stable? Look, its fine if you just run to run as stable as possible, we are here to make money afterall. I just wish you didnt treat this beta thread as a release thread. You dont betatest when you keep old versions cause their more fucking stable.

You suck honestly as a beta tester and shouldnt be in here. Perhaps neither should i, though im on Win 8 so kinda have to at the moment.

 

It sounds to me like he's having the same issue I mentioned previously in the thread where MiniMapMarkers don't show up on occasion. http://www.thebuddyforum.com/demonb...monbuddy-daily-beta-builds-44.html#post817807

'Dump MiniMapMarkers' does nothing, or perhaps misses only the exit, and the dungeon explorer can't find the nameHash either.

I've even gone as far as making a plugin to dump Zeta.ZetaDia.Minimap.CurrentWorldMarkers, which is empty (no elements) when this happens. There are no errors in the logs, and restarting DB doesn't fix it. Only leaving the current game and resuming (usually) works.

Right now, I'm on Halls of Agony Level 3 (Act 1), literally standing at the portal to the butcher, and this just happened. Just made a video of this with the latest beta: 2012-10-31_2213 - rrrix's library

 

Another issue with ExploreArea is the 15 mins wasted on walking back and forth re"discovering" the map once its explored it all.

 

Beta.66 is crushing on identifying items.

Code:

[09:28:13.318 N] [GilesTrinity] No more space to pickup a 2-slot item, now running town-run routine.
[09:28:29.508 N] ========== Grid segmentation resetting!!! ============
[09:28:58.774 N] Closing error dialog
[09:29:00.864 D] System.NullReferenceException: Object reference not set to an instance of an object.
   at Zeta.Internals.Actors.DiaActivePlayer.get_LoopingAnimationEndTime()
   at Zeta.CommonBot.Logic.BrainBehavior.„(Object )
   at Zeta.TreeSharp.WaitContinue.
.
()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Sequence.
.
()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.
.
()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.Common.HookExecutor.Run(Object context)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action.
.
()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.
.
()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.
.
()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Decorator.
.
()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.
.
()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.Common.HookExecutor.Run(Object context)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action.
.
()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.
.
()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.CommonBot.BotMain.
()
[09:29:00.934 N] Waiting 10.1 seconds before next game...

Let me know if you need full log.

 

Don't feel like replying to a woman who think she and her mates are right while other men keep telling it's not.

 

Taking the high road I see. Guess i won

 

Been getting a crash randomly from 10-50 minutes of running. Not sure what is causing it; Fresh install of DB, updated plugins to most recent, Even switched from profile using RadsAtom to one that uses only Trinity xml commands. Seems to crash when starting a new game. Log attached

View attachment 1400 2012-10-31 22.24.txt

 

What is that new Ticks/s: under Games/hour: ???