vista 64bit + keyclone = input lag and overall keyboard crash

[mkorolev]

Hi,

I run a XP setup with keyclone, maximizer and 2+ wow clients with no problem.

Main monitor is 1920x1200 windowed maximized, second monitor is 1450x960, or something similar using maximizer

The same setup on Vista (separate copy of keyclone and wow) starts off fine after xp sp2 compatibility mode is selected, but after a minute or so the main toon gets stuck in run mode and holding the down arrow or 's' key stops them, but then they continue on when key is released. After a few minutes it seems to crash any input from the keyboard, or any other usb device plugged into the same usb host...running even 1 client with keyclone has issues after a while. Old PS2 keyboard seems to work fine after the crash, as well as the USB mouse. This is now global to the entire system, even if wow and keyclone are closed.

running 2 wow clients alone, without keyclone, doesn't have the same issue....or maybe i just didn't let them run long enough.
I tried setting both wow and keyclone to run in xp sp2 compatibility mode. There was a slight improvement when wow was run in xp compatibility mode (basically you could log in before the lagging started, before even the login screen would lag and seemed to register more than 1 key press? hitting a letter once would fill my login box with * characters)

Has anyone else experienced the same issue? ?(

Here's my setup (nothing's overclocked and system is otherwise stable):
EVGA 790i Motherboard Utimate FTW
AeroCool HorsePower 750W SLI-Certified PSU
Intel Core2 Quad Q9300 2.5GHz
Corsair 4GB DDR3 RAM
2xGigabyte 9800GTX+ 1GB GDDR3 (59 firmware)(Dual Monitor + SLI Enabled on Vista 64Bit 180.x driver)(Dual Monitor + SLI disabled, 177.x driver on XP Pro 32Bit)
XP Pro 32Bit Install on 200GB partition of 500GB Seagate SATA
Vista Ultimate 64Bit Install on 200GB Partition of 1TB WD Caviar Green SATA
2xLG 24" Monitors

[Ogloo]

some sort of connection issue between the 2.. never had this problem humm.. update ur keyboard/ all USB drivers? maybe those are unstable?

[mkorolev]

It seems whenever keyclone is running, regardless whether wow is or not it sends extra key presses -- notepad, firefox, chat, etc

[keyclone]

make sure you do not have more then one keyclone running

[mkorolev]

It's definitely just 1 copy of keyclone running.

[keyclone]

look at the list. do you have 1 entry per client you are routing keys into?

[mkorolev]

Yes. 1 entry, sometimes no entries (no wow clients running) still has issues

[keyclone]

if there is nothing in the list, then keyclone is not sending keys anywhere. watch keyclone. the '...O..' above the connect button moves when keyclone pushes keys around. is it moving even when there is nothing in the list? no? and you're still having issues? i think you have something else going on with your system

send me your email address and i'll check into it further

[mkorolev]

Is it supposed to be pushing the 'O' around when there is only 1 client added in keyclone, or when the key pressed is on the "do not pass" list?

Anyway, the toon seems to be stuck in run mode, almost like auto-run, and it doesn't look like any key is being passed -- 'O' is not moving
only way to stop the toon is to make the window lose focus (either that, or hold the key opposite of the direction she is moving, but then she just resumes on her merry way when the key is released). I tried opening notepad, to see maybe it was stuck in scroll mode somehow, or a 'W' key was "stuck", but that doesn't seem to be the case.

It does sound like an issue with the keyboard/G13 moreso than keyclone, but it only seems to happen when keyclone is running, and only on Vista.
Tried unplugging G13, that didn't help, other than reset my profile :P I guess i can unplugging my wireless keyboard next, but i would so much rather not have to play with an old ps2 one, still a good test.

[keyclone]

ah... now we come to the actual problem.

it's not that keyclone is pushing keys around, its that wow didn't get a key up event.

in your do-not-pass list, do you have 'strict' checked? uncheck it. that will resolve many issues.

(i've described this issue dozens of times over the passed 12-18 months... here goes...)

if you have 'strict' checked and put your movement keys on the DNP list, ie: WASD, then you decide to hit shift+W, this is when you can get into issues. this is how:

shift down
W down << allowed through as it is shift+W
W up << allowed through as it is shift+W
shift up

this will work as expected. but if you are in a firefight and your fingers are flying... sometimes you can do this:

shift down

W down << allowed through as it is shift+W

shift up


W up << NOT allowed through as it is just W

at this point, your alts will not received the W up (really shift+W, but wow will use the W if you have nothing bound to shift+W)... and since they already got shift+W down... they will continue to run in whatever direction you told them.

and yes, the O will push around even if there is only one window in the list