Having trouble with movement functions sticking across 5 boxes with KC

[Con7ent]

Hey everyone, I'm new to the community as well as using keyclone. I'm not new to multiboxing though, I've been doing that ever since I got a hold of more than one account pretty much and had multiple class synergies to tinker with. :P As of late I'm just really starting to see the potential of automation with this software and I am currently working on clearing heroics with my 5 man team of resto shaman, two fire mages, a warrior and shadow priest. Since they are all diff classes it takes a lot of specific and relative function macros including of course, some basic movement functions. What I have now is basically a macro for everyone to follow the warrior, or follow the resto shaman if I want to put them into different camps, and I have bound move backward(default w) to ALT-C in order to break all following the warrior and placing the heal/caster camp however I want. Here's the issue, though- often times when I press alt-c to break follow, often times it's like the same affect as your W key sticking, and the toons will not stop moving backward even when I release alt c, move forward strafe or do whatever. I can even hold down move forward when they get "stuck", and they'll stand still, but as soon as I release it they start backpeddling again... anyone else have this or know a remedy to this anomaly? Help would be awesome :thumbsup:

P.S. Also it's any movement that causes this to happen, not just backpeddle, it happens with strafe also.

[JD50]

Sounds like an issue with your DNP list. What is in your DNP?

[Con7ent]

Sounds like an issue with your DNP list. What is in your DNP?Could be, but I have C on my DNP list and alt isn't could this be causing a prob somehow? (Alt-C being the backpeddle command across clones.)

[Con7ent]

Also I just removed C from my DNP list, kept the binding as ALT-C and retried it, its still sticking.

[Reprisal]

Yeah, i've wiped many a time because of that. It's quite annoying, I'll hit the backwards key on my alts and they will just keep backing up until i exit out of keyclone on that computer. No idea what is causing it.

[aNiMaL]

To me it seems like modifier keys are linked to this problem.

I was trying to create a 2-key spread sequence and ran into sticky keys aswell.

I'm using a G15 keyboard and mapped my G2 and G3 to "ctrl + num 8" and "ctrl + num 9"
I keymapped these to "." and "," on the clones.(which are linked to the movement again)
When I pressed both keys at the same time my clones just started running and wouldn't stop.

I've been using my mains "." and "," (whitelisted) to spread them out ever since and it works like a charm.

When I used a 1-button spread on the G3 button this issue never came up.

[Bena]

From some tests I did it seems to be related to the order in which you
release the modifier keys. If you let go of Alt before C then
sometimes it will get stuck with C pressed. If you release C and
then let go of Alt it seems to be ok.

[KvdM]

In the past I only noticed the sticky keys when switching focus, now I've also seen it happen a couple of times without switching focus. Going to check tonight if my sticky key issues are also caused by the modifiers.

[Ken]

I have the same problem when all characters are standing still and i press [ctrl]+[alt]+[arrow right] to switch to my other virtual desktop. Sometimes, when I do this, the client that lost focus starts running automatically, until I go back to that client and interrupt the running. It looks like running gets activated (which is bound to num-lock for toggle or mouse button for regular running).

I also have problems when just running around with my main and the movement keys E/S/D/F(instead of W/S/A/D). These movement keys are in the do-not-pass list. I seem to be able to cancel the running most of the time (but not always!) by passing a "/follow main" on the running characters or by first forcing them to walk forward (manually) and then doing a "/follow".

It's really weird.

[Ughmahedhurtz]

From some tests I did it seems to be related to the order in which you
release the modifier keys. If you let go of Alt before C then
sometimes it will get stuck with C pressed. If you release C and
then let go of Alt it seems to be ok.Now this is good feedback. Maybe Rob can do some investigation with that data in hand. ;) (assuming he hasn't already)

[keyclone]

your DNP contains: WASD

and you press:

shift down
W down
shift up
W up

what passes to your clones is:

shift down
W down (since this is really shift+W)
shift up

note... no W up, since W is not shift+W... and W is on your DNP

and since wow works off of movement vectors (the down and the up.. in between doesn't matter)... you end up with a 'run away'

solution? add shift+WASD, ctrl+WASD, and alt+WASD to your DNP

now... i could modify the way the DNP works... and block ANY version of W, modified or not.. but i don't think people would like that

[keyclone]

Now this is good feedback. Maybe Rob can do some investigation with that data in hand. ;) (assuming he hasn't already)yea.. this is a known 'problem' as i mentioned above (simul-post :D )

but then again, its not a problem. it's an understanding of what is going on

[KvdM]

Is there a list or sticky of these known issues or can a sticky/wiki entry of these issues be created? This sounds like something that a lot of new multi-boxers will run into.

[keyclone]

i might be able to do something about it when i get home tonight...

[Bena]

yeah... funnily this has actually surfaced at work.. a new version of a
software package had issues with tools getting stuck in their state in
the viewport.. multiboxing saves the day again :thumbsup:







Now
this is good feedback. Maybe Rob can do some investigation with that
data in hand. ;) (assuming he hasn't already)yea.. this is a
known 'problem' as i mentioned above (simul-post :D )

but then again, its not a problem. it's an understanding of what is going on

[Con7ent]

your DNP contains: WASD

and you press:

shift down
W down
shift up
W up

what passes to your clones is:

shift down
W down (since this is really shift+W)
shift up

note... no W up, since W is not shift+W... and W is on your DNP

and since wow works off of movement vectors (the down and the up.. in between doesn't matter)... you end up with a 'run away'

solution? add shift+WASD, ctrl+WASD, and alt+WASD to your DNP

now... i could modify the way the DNP works... and block ANY version of W, modified or not.. but i don't think people would like that"

Thanks for all the feedback guys, seems like a really productive community tbh. I see what you mean about the DNP not letting the game send the "release movement" command on account of the key being released on the DNP list. However I did some more tests, and found out some interesting things. Remember my move backward bind was to ALT-C across clones, and I had only had C on the DNP list when the movements started sticking-well, I disabled C from the DNP and still got the same result with the ALT-C binding.... BUT when I rebound the command to move backward, or any other movement command for that matter to SHIFT-4th mouse button, I tried to get it to stick and it wouldn't;everything was working just fine. It sounds like it has something to do with using the ALT key as a modifier in any form. Whenever I saw that a few posters above me also were using alt as modifiers and the same problem occurred, I was pretty assured of that. :P I am actually running out of keys AND modifier keys I can comfortably use to bind commands as well... which I'm sure a lot of players here are also, so kind of sux. :|