Printable View
I have this problem aswell, quite alot of the time. It's EXTREMELY frustrating in instances. :(Quote:
Originally Posted by 'Fursphere',index.php?page=Thread&postID=22950#pos t22950
It also happends when my slaves are following my main and i start casting a spell.
It only seems to happen to me when I hit my formation key while im moving. If I stop and then hit the formation key they dont seem to run away.
kinda an old thread?
well since I've made a change on ahk switch to alts using a key I can consistently get a run away when I'm switching while holding a movement button down or hitting a movement button before the switch happens.
I've seen it a few times.
Macbook Pro OS X 10.5.4
ClonedKeys
ControllerMate
G15 and Logitech 610 mouseI have to agree to this 100%. I have thing setup so it is a keyQuote:
Originally Posted by '''''', but that was usually because I had the run key held down when I moused off one PC and onto another one.[/quote
click to switch characters so I have all of the windows overlap (I get
better FPS at the same time). Since I started overlapping the windows,
I have NEVER had a character just run off.
Thread necromancey for the win. Seriously though, I do know one reason why this happens and it most likely isn't the only reason it happens but as a programmer I can validate why and how this happens when using keyclone/octopus on two computers with kvm enabled.
In this example I'm running my main main paladin on one computer and my 4 shamans on a second computer. The keyboard and mouse are cross linked to the two computers and wasd only go to the client that has focus. If I hold down for example the w key and move my mouse over to the second computer the w key basically gets locked in a pressed down state on the paladin client and will not release without first going back to the paladin client and hitting the w key again.
Now as to why this happens it is very simple. What is happening is Octopus is sending the WM_Keydown windows message directly to the paladin client. Keys stay pressed until the corresponding WM_KeyUp message has been sent to the window. Because the W key is pressed down while the paladin screen has focus and not released until another client has focus the WM_Keyup message is never receieved and the Paladin continues happily running off into the sunset. Going back to the client and pressing the back button does no good because to this client the W key is still being held down. Pressing the W Key again works simply because it causes the WM_KeyUp message to be sent after you release the W key with the proper client having focus. I hope I explained this so people can understand it.
my post from [Keyclone] 4 box shamans running off, more common in instance runs help :
From what i read it seems that a couple people (at least, me included) had this problem with the clone that needs to STRAFE RIGHT.Quote:
i've been having this problem as well, and it seems it's always when i use my formation (which i often use just to break /follow)
Basically with my 3 toons, the formation key is '\' (backslash)
This is bound to DOWN on my main, STRAFELEFT on clone1 and STRAFERIGHT on clone2.
Seems sometimes clone2 decides to run forward instead. looks like it receives AUTORUN instead of STRAFERIGHT basically.
From memory it's always the same clone that runs like a fool.
Pressing the follow key (backspace in my case) usually bring him back if i'm quick enough.
i had the one time when he would turn and run back, but continue to run past my other toons until i pressed follow again, then turn again and run past us again etc.
Can anyone confirm? could it be that this keystroke is passing badly or something?