Cant do this while moving

Annoying bug is there since christmas.
There are like ten other reports over course of last three months regarding this tho, no clear answer what to do.
Any OS/HB version/CC/Class/Spec.

Also got another movement issue under certain condidtions that is not realted to gb2 that is result of same bug i guess.
Setup is heavy, vmwares, vpns. But point where to work would be good. Custom lag tolerance that helped to reduce this effect to some other guy in other thread doesnt really seem to affetc me at all.

Hopefully i will not get suggestion to reinstall HB since i was even reinstalling OS trying fix this even.

Guess it will be hard to fix this, but at least some directions where i have to work.

 

It's not a GB/HB issue.
It happens when GB/HB tries to interact with something whilst the WoW client thinks it's moving.
The only way to handle this is to decrease your lag. But seeing as you're on a VM, through a VPN there is a high likelihood that you won't be able to do that.

Having said that; it's not a big issue. GB/HB will usually try again after a second or so and then it will succeed and move on.

Your choice: Paranoia with VM/VPN and a slower gather or faster gathering without the VMs and VPNs.

 

If its not GB2/HB issue than:
Why GB1 is working just fine?
Why i never have to force interactdelay with npcs?
Why there are no delays or bugs with anything but only with the process of initial interact with node?
Why other people had this problem without vmwares/vpns?

Makes no sense at all.

Despite its vpns and vmwares there are no huge delays or something you might think of.
And despite it may be not relevant at all - i never have in-game latency over 150-160.

 

i have the same problem
[17:03:14:815] Activity: Interacting with node
[17:03:14:815] InteractDebug:450784392
[17:03:14:816] Interact Done:450784392
[17:03:14:883] Flushing timed movement. Direction: AllAllowed
like he interact before finishing movement

 

its my log
this bug dont occur everytime , sometimes i got 10 nodes in row without this bug , but this bug occur ~ 70/100 nodes

 

any idea why this bug occur ?

 

I have the same problem and i dont think that this depend on my 80-90 ms ping in world of warcraft.