Keyclone acting funny?

[ahnubis]

I was playing and noticed that keyclone was still running but it was not passing any of my commands to the other 4 windows. All this is on 1 PC dual core 3.4ghz 4 gigs of ram dual 8800gtx.

I had to close keyclone and relaunch it add each window and it would work again. About 20-30 min later it would stop working again.

(note)the little circle in keyclone to let you know its getting commands was still working each time I hit a key that circle would move to a new dot but the command was not hitting the other 4 windows.

I noticed this with G and H versions.

[keyclone]

a new version is out today, v1.8i.

please send me your system-id and i'll check it out

[Otlecs]

please send me your system-id and i'll check it out

Out of curiosity, what can you do to diagnose problems once you have a system ID?

[Niveous]

Having the same problem; ever since I patched WoW my keyclones aren't responding to my commands.

[Niveous]

I restarted my wow's and it started working, then about 15 minutes later it stopped like the OP suggested. I'll PM you my key.

[Gurblash]

I've been a long time KC supporter and had that same issue creep up on me last night. This is my first bug ever experienced with KC.

Found out that it was only passing a handful of keys. And unfortunately not the ones I wanted ;)

Tried everything, deleted my DNP list, redefined my regions. Reset computer, KC, WoW's nothing.

Finally I uninstalled *deleted* Keyclone. Downloaded the LATEST version v1.8i, re did my regions, DNP list, commands and bam in 5 minutes I was back up and running like nothing was wrong.

So if all above fails you give the delete and recreate method a try :) Worked for me

[Niveous]

I deleted my old Keyclone and re-did my DNP list, it seems a few of them might stay connected for a while.. while the other (all on one PC) will not connect. Restart WoW, with-in 10-15 minutes it will die completely and no keys will be sent.

[keyclone]

are you using ANY other software? are you using the latest version, v1.8i ? did you download it directly from solidice.com?

i've had keyclone connecting my xp and vista box all day... still running.. almost 9 hours

i'd really like to know what you guys are doing to get this effect

@Niveous
i have no idea what you are talking about. few of what might stay connected? other keyclones? are you talking about wow clients? keyclone does not 'connect' to them... just sends them messages.

[Niveous]

Yes I got it directly from your sig. I'm not running anything else and I'm using Vista. I use 4 accounts to play WoW, and three characters might connect while the 4th won't receive any key commands. I restarted that 4th that wasn't working and then they worked for maybe another 10 minutes before none of them were receiving the keypresses besides the active client. Not sure what the patch did to it :cursing:

[Niveous]

Ok well apparently my problem was a DNP problem. I used all the settings from last time but added a few more including: shift+q shift +e ctrl+q ctrl+e (since I use q and e for attack and follow)... and it was blocking even the normal pushes of the buttons for q and e without the shift and ctrl functions. I'm not sure if this is intended or not, but it just seems strange when I dont have q or e blacklisted, it will blacklist those two for inputting the above functions (shift+ctrl, etc.).

I'll post back if it acts up again.

[keyclone]

ahhhh

ok... to prevent the 'run aways'... i implemented the option 'strict' on the dnp list. by default, 'strict' is UNCHECKED. as such, if you put 'e' in the dnp list, then ALL forms of 'e' will be blocked. this is an intended.. but is different from the way it was before.

here is the problem... noobies will download keyclone and start using it... at some point, they will hit the 'run aways' if they are using the dnp. this is frustrating and many groups have been wiped because of it.

by implementing 'strict'.. the noobie will not have to face the 'run ways'... and the more advanced player can CHECK the strict option... getting the old dnp list functionality

i hope that makes sense. i realize its a bit confusing, as your behavior changed on updating... so, i would recommend just CHECKing strict to get back to the original way of doing things... and only UNCHECK it if you experience the run-aways