Keyclone 1.8 buggy ?

Hallo,

the first thing "sorry for my bad english", i hope i can explain the problem right.

I use Keyclone 1.8 one a single computer, i control 5 Chars on 2 monitors like some other people.

For every WoW-session in have a differnt installpoint (c:\wow1, c:\wow2, c:\wow3 .......)

On the start from Keyclone and the 5 WoW sessions, all works perfect :D

BUT after a time of play, i become trouble with the change from my mousecurser frome one WoW-window to another.

I can not longer enter with the mouscurser into one of the WoW-Windows, if i try that, the curser jumps out of this window and the toon of that windos make a little turn.

This problem comes an different time of play and it comes an differnt WoW-sesissions. 8|

At the moment the problem starts, the whole computer runs fine (max. 45% CPU use, swap 1,20 GB)

please help me

Something I'm experiencing as well and I believe it's due to a small amount of lag moving between screens.

Are you using both mouse buttons to move around in those windows? If so, as you move your mouse out of one screen, it's not telling the window that you've released both mouse buttons hence all you can do when you move it back is look around.

The only way I've found to get it sorted is to move your mouse into the affected window and quickly use the left mouse button to look around at any other angle to reset the camera.

It's a pain, I've not found a better way around it yet. I can't find the thread now but this was discussed recently - assuming you ARE having the same problem as me.

Hi Stormweasel,

thx for the quick answhere :)

I think this will help me the i use the mouse to move around my mainchar, like you request it.

i try your tip, and give a feedback if it fix my problem or not.

I have a similar issue as well and i think it's related... sometimes my slaves after on follow will suddenly just keep running in a particular direction. And even if i press the toggle auto run it will continue on. Only way to stop it is to click on the bugged slave one, then on the master window then back again onto the slave.

Any ideas whats causing this?