Hello there! First of all, logs View attachment 10-07-2012_12_42 3992 Log.txt This, just before it gave a black screen - Warlock (CC: Zerfall) - Hyjal View attachment 10-07-2012_12_41 2644 Log.txt Mage (CC: Singular) - Uldum View attachment 10-07-2012_12_40 3284 Log.txt Warrior (CC: CLU) - Vashjir The problem is the movement between hotspots, once it reaches one, it stops for a second, then it heads to the next one, making the bot atm not usable because of this obvious bottish behavior. The logs are short, just 10 minute sessions, are in different zones using different CC and classes, all at the same time, so its not a cc problem, please address this issues cause this could generate bans for us, the users of HB. BTW... this keeps happening since the release of 2.0.0.5951 version, made a rollback to 2.0.0.5883 (clean install of course) and oddly, same problems, when it never gave this kind of issue when using prior to .5951... Edit: In case that my logs are not significant, here?s a link to a post of some other user who has this issue: http://www.thebuddyforum.com/releases/58994-release-honorbuddy-2-0-0-5951-a-8.html#post610771
THIS! Its really annoying! Tony, do you really think using another CC will fix that issue? I am using Singular on all my accounts and im experiencing this issue.
Albanuva try delete you Mesh folder located in C:\Users\$$$$\AppData\Local\HonorbuddyMeshes if you have trouble finding it you can look at the Mesh tab on you HB under settings and tools.
I had the same problem, disabled not used Plugins and it was gone! Corga daily plugin was once the problem. Another was Pimpmyguild! After disable this addons it worked great! Strange thing is: I reactivetd Pimpmyguild a day later and it farmed normal (no more stops)...
I tried disabling and fresh reinstall but nothing happened was still same. Its really a movement issue so I decided to delete the Mesh folder and so far no stops in 20mins, also before hand if 2 nodes where in close proximity it would sit there but now farms them both.
Well I've still got this kind of problem, some stopping at points and some moving back and forth between two spots for no reason before carrying on. I tried deleting the Mesh folder as suggested but still no joy. Also no luck with disabling plugins. Anymore suggestions or fixes anyones got I'll give them a try.
Damn this is really frustrating, I've been messing with all of the settings again but just can't get this stopping problem to go away, regardless of plugin settings, mount settings cc etc. The strange thing is that it worked fine before the update and now even when I go back to the previous version the problem remains... Hopefully someone is looking into it and can give us some kind of fix.
Thanks for the suggestion, I did have skype on and quit it. No change in the movement for me yet, same problems. Perhaps it might help someone else with this problem.
black screens are wow issues - so you need to add a blackspot to the node in question - or remove a waypoint or 2
Yup, black screens are wow issues, but how about hb movement? Both answers for staff members address the black screen reference, but NOT the movement. And its not a uncommon issue, there are a lot of people suffering from this, but still, no answer...
I've done this to profiles I've used and it has helped. However... Correct me if i'm wrong, I do not remember blackscreens always being such an issue, in fact in only seems fairly recently this has been brought up. So, surely it's an HB issue? Although, I suppose you could throw back that updates in wow cause this. Nevertheless, I can't recall getting blackscreened in wow if I'm playing...
I am having the same movement glitch. Singular profile used. It moves to a hotspot, waits 1 sec, continues to next, waits 1 sec. Very jerky and botlike. It's broken for me unless I figure out a fix, I'm not using the bot. I made a tiny log and attached. Edited to fix log
Try using this http://www.thebuddyforum.com/archives/21741-plugin-nav-autoprecision-no-more-stop-go.html If that does not fix it then we are at least narrowing down what is causing the issue.
