Printable View
I was able to reproduce the "run away" behavior as follows.
I have w set as "do not pass", which is also run forward.
If I do hold shift and hit 'w', shift-w will get sent to my alts, and they -will- run forward.
So here's how I did the run away bug.
Hold shift
Press W
Let go of shift
Let go of W
And they are off! Until i click on those windows and hit 'w', they keep running fwd as if w is stuck down.
Works with asd, as well.
This is with keyclone version r. Did s fix this?
hmmm... that would probably produce the behavior since the clones would never get the W key up, with it on the black list.
shift-W will also run them forward.
i'm not sure how the up command would ever get through, since releasing the W would be blocked, even with the shift down.
my recommendation would be to add shift-WASD to the black list.... or just use the mouse to drive/steer and not have WASD on the black list (i've never hit this since i don't have much on the black list.. just NUMLOCK currently)
nice catch
I added shift-WASD to my blacklist, fixed that up. When I first saw that, I chalked it up as a feature rather than a defect.
Aye, the autorun thing on my clone was ridiculously frustrating.
Yeah this is annoying little bug. But just blacklist the shiftw
lol it is annoying and yet very entertaining sometimes.
i usually find this happens when say im running in for a pull, so im holding W, then im hitting something like power word shield which is like ALT+2 on my g15 bind pad, and thats when its triggered.
And if whitelist worked a little better with the g15 keys i would use it, but it doesn't understand them all that well :(
*HINT*HINT* make a sexy g15 binding section for keyclone ;) ;) ;)