GatherBuddy2 not working Correctly

There is no need for a log because its not in my log unless you are looking at the timestamps but it seems like sense the update with Honorbuddy my Gatherbuddy2 stops and wait a second and then places the click to go and looks very bottish. i don't think it is a error. i don't know about anything slowing it down i have no Plugins on while running it but logmeout. if you guys could look into that would be amazing and if you don't understand what i talking about im saying that it isn't a smooth flight its a slow clicking kind of motion. looks like im playing runescape again when running gatherbuddy 2. i don't have any problems like this with using quest bot just gatherbuddy2.

 

let us decide if we need a log or not

please always attach one, as I don't like to guess

 

ok heres the log hope it helps
View attachment 7-14-2012_3_07 AM 4400 Log.txt

 

it's flushing the timed movement a lot

i'll pass it along

 

Pass it along? sorry im tired and i have been trying to get this to work for a while and my brains about to crash and isn't able to really understand.

 

He will give it to a Dev, so they can take a better look at it.

 

Thanks its getting about 4 am here and been up all day so couldn't understand it. Hope i can get this fix haven't had any problems except this which i don't care i just got my 3 characters to 85 so im happy thanks kick for the 1-85 questing profiles

 

I got that problem as well, it was more fluid before the latest update I think.

 

I don't know how i got it to work but it seems like its only on some parts of Northern and other parts. i will give another log and what profile im using when it happens again.

-Edit- its happening again uploading the Logs

 

Also getting the same problem after I updated, lots of "[20:28:16:243] Flushing timed movement. Direction: AllAllowed" like the other guy.

 

Just figured I'd post here so as to not start another thread with the same basic topic. I used GB today for first time since last update and noticed the same pausing at hot spots as others have mentioned. I was on my druid earlier herbing/mining and noticed it on all profiles I used. I actually re-installed HB so I could check if that was it just to make sure but nothing changed. I also used three different cc's, JungleBook/CLU/Singular, and nothing helped.

The log below is from my DK tonight as I decided to set him up to do some fishing with AutoAngler2. The profile I was using was a private one of mine and it was really bad on it so I just decided to call it a night. As you will notice I stopped the bot several times as I was trying to change the mount settings so please ignore that part of it.

Thanks for your time.

 

Same problem here with the Flush thing. Can't get to log right now.

 

I have this problem too and gatherbuddy is black-screening wow for me. Already made a post here - http://www.thebuddyforum.com/releases/58994-release-honorbuddy-2-0-0-5951-a-11.html#post630037

 

same issues here ... bot works fine but at some time just stands in the air doing nothing , randomly, it also blacklisting 20% of the nodes , nothing in the logs, only saying moving to next hotspot. and yes i got also black screens , all this happens in both zones i farm Deepholm and hyjal. (using singular and shamwow cc's and pottz profiles). thx

edit: btw this started to happen since "facing node" has come to GB ... which i never understood, my bot is falling off some edges even more often , i keep it unchecked... maybe this helps.

 

Had the same issue, and there didn't seem to be a fix to it despite many posted about it other then using the old version of hb which Tony linked in another thread.

Love your work otherwise guys!

 

Which thread, I would love a workaround. My bot keeps pausing while moving as well. I linked my log on another thread but I'll link it here as well. It's short, but the bot still paused each time it was clicking to a new spot.
View attachment 7-17-2012_1_53 PM 1284 Log.txt

 

This is almost definitely a latency issue. It looks like it slow to load paths due to lag as your bot syncs with our auth server. That should only matter for first couple of circuits of your profile but your profile is HUGE and takes at least an hour to do a circuit. Run a smaller profile and the problem will go away.