
Originally Posted by
'keyclone',index.php?page=Thread&postID=61033#post 61033
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. :|
Connect With Us