Hi, Not entirely sure if this is the correct place to post, but here goes: I noticed this started with the Beta (HonorbuddyBETA 2.5.8438.404) and has now creeped into the latest live (2.5.8461.698). I did not have this problem in 2.5.8179.697. I can recreate this problem ad nauseum with Live 2.5.8461.698 as I could with Beta 2.5.8438.404. The setup: GatherBuddy2, mining only, Druid (Tauren, 90), Swift Flight Form. Happens on multiple profiles across different zones including Jade Forest, Valley of the Four Winds and the Dread Wastes. The problem: Often GB2 will 'overfly' the node. Ok, the bot flies back. Ok, a third time. Maybe a fourth. Move on to next node. Looking at WoW and it's saying "Can't do that while moving." Looking at the HonorBuddy window and it's telling me that the node will be blacklisted and the bot moves on to the next node. This can happen a lot, and I could almost guarantee a repeat if using the Beta version above and the now live version. I've attached a log --skip to [23:12:02.003 D] --I paused the bot to kill a rare at the start, my apologies! I let the bot run a little just to show it happening short and sweet, but this happens across other profiles and at length. Sometimes, actually most of the times, GB2 functions fine and will hit the nodes OK but I'm seeing this creep more and more now. As this problem did not exist in 2.5.8179.697 (for me) I am hoping there is a fix or it is a bug that can be addressed. Thanks in advance You need to register and have one post to see spoilers! View attachment [GB2] Cant do that while moving #2013-10-27-0011.txt
TuanHA. Hi, I think it is an issue with HB's implementation of Frame Lock -which makes sense as it was introduced to the main window in Beta 2.5.8438.404 and subsequently Live 2.5.8461.698. With Frame Lock enabled the problem arises and disappears respectively when enabled and disabled... so my thinking goes. This user james7360 posted similar situation here... it could be unrelated but I think it's the cause. I can't test at the moment to confirmbut will report back tomorrow. NB: I test with Singular, Hazz and PureRotation -all suffer the same.
I was actually asking the creator of this thread, not you. Anyway, I'll let the devs know about this, as this would be a pretty big problem. Your updates would be appreciated.
well you didnt state who your question was directed at, As we are both suffering from the same problem wouldnt gathering infomation from as many people who are getting the same problem be the smartest idea? No need for the rudeness in your reply. Looking forward to a Fix, Thanks for your Help
ideally no one should be bumping a support thread except moderators and the person who took the time to make it. so yea, we're checking it out.
Try to decrease your tick rate from hb settings to allow gb2/pb to start gathering. WoW MS: 40-50 CPU: Intel I5 2550k 3.80gHz Tick: 7 Bot: ProfessionalBuddy Profile: Private (Pandaria mining) EDIT: Added bot base and profile info. Works perfectly.
Hi CodenameG, Thanks for your time and keeping the thread on point. My CPU, if it's of interest is an Intel i5-3570K clocked at 4.4Ghz with 16GB DDR3 1833 RAM. Should also be noted I am using Mist Piercing Goggles. Speedtest: 30Mb/s. WoW home and world: 31ms. Logs with and without Frame Lock (FL): View attachment [GB2] FM and TPS Logs.zip FL=Ticked @ 100TPS = Fail FL=Ticked @ 60TPS = Fail FL=Ticked @ 30TPS = Fail FL=Ticked @ 20TPS = Fail FL=Ticked @ 5TPS = Success FL=Unticked @ 100TPS = Fail FL=Unticked @ 30TPS = Fail FL=Unticked @ 25TPS = Fail *mostly success FL=Unticked @ 20TPS = Success FL=Unticked @ 15TPS = Success FL=Unticked @ 5 TPS = Success NB: It's also interesting to note that the symptoms change depending on TPS. At a very high TPS (with and without FL) the bot can overfly a node but without appearing bot like -smooth, if you will; lower the TPS between 20 and 60 presents very prominent *bobbing* when attempting to correct itself after an 'overflown' node. At the lower TPS it works perfectly, particularly 5TPS -with and without FL. Thanks again for your time.
