It seems that the follower is running a little bit slower than the other and eventually getting too far away. I can ofc just stop every few seconds but that is just too annoying.
I think it might be because im running 2 programs at once.
Printable View
It seems that the follower is running a little bit slower than the other and eventually getting too far away. I can ofc just stop every few seconds but that is just too annoying.
I think it might be because im running 2 programs at once.
What are the specs of the machine you're running on?
Could network latency have an effect like this.
I am on Hughesnet Satellite and I have the same issue with Auto Hot Key in a x2 config.
I have a /target/follow/focus/assist macro but it sure would be nice to get w,s,d,a working.
Would it be better to run it all windowed?
Also why is it so difficult to get AHK to accept w,a,s,d?
(I get the little jerk movements but my toon does not move,kinda like a jumpy action.
This here is that bit of code. I use q,w,e,f, on my keyboard.
~e::
KeyWait e, D
WinGet, Active_Window, ID, A
IfWinActive, World of Warcraft
{
If(%killbroadcast% = 0)
{
Loop, %wowid%
{
target_window := wowid%A_index%
If (Active_Window <> target_window)
{
ControlSend,, e, ahk_id %target_window%
}
}
}
}
Return
Without knowing a great deal about how Blizz implemented their follow code, I can well imagine that latency of that magnitude could cause this sort of problem.Quote:
Could network latency have an effect like this.
I am on Hughesnet Satellite and I have the same issue with Auto Hot Key in a x2 config.
500-1000ms latency on the first hop makes for a very long round-trip time :(
I'll defer to others for the AHK question, but you might also consider a new thread for it in the Software Tools forum.