Looking for help with performance issues since swapping from Octopus to Keyclone

I've been boxing for a month or so, using Octopus (because it's free to try). A couple of threads here coupled with my aim to start a mage group soon have convinced me to buy Keyclone for it's round robin feature. I have however run into a couple of issues with maximiser as implemented by Keyclone.

Initially, one that I am sure will be easy to fix is the aspect ratio of my display areas. I've created regions in the maximiser at 16:10 ratio (same as my primary monitor). Region 1, monitor 1, 1680x1050. Region 2, monitor 2, 1120x700 and Regions 3&4, monitor 2, 800x500. This is the same setup I use under Octopus on my 22" widescreen and 20" 4:3 (1600x1200) displays. Unfortunately the wow sessions are running in a horizontally stretched 4:3 ratio making everything look short and fat.

My second problem is performance related. I am unable to take control of any session while another is on a loading screen and mousing into a session causes a noticable pause and jump in the mouse movement. Again, this is not apparent under Octopus.

I'm running a 3Ghz Core2 Duo, 3.2Gb ram under Vista with my WoW sessions all symlinked to a single install. I run Octopus and Keyclone from the same WoW installs.

Anyone have an idea how to fix this? I really want round robin and hotstrings (I want the mages setup to be leaderless).

I'm still very new at this, having just started yesterday, but I noticed a sizable performance improvement by turning off "Focus follows mouse". It's a big enough difference that the additional click into the window to make it active is much faster.

That being said, I'm running all five clients on one machine, so I'm sure that's going to be part of it. But with that feature turned off, I'm getting pretty decent performance.

sounds like you didn't set your game resolution in your maximizer for each region.
i generally recommend setting it to the size of your main area for all regions.
then make sure your small regions have the same aspect ratio as the main

as for performance duriong loading screens... i'm fairly certain no one has ever mentioned that they cared.

Well yes, the performance during loading is a minor problem other than I have to wait for each session to load up fully before I can select a character. I must then wait before I can click "enter world" on the next window because the previous one is still loading. Not something I can't live with as it just takes a little longer to get going than clicking on each "enter world" button in turn.

The problem is the delay when mousing between sessions with focus follows mouse. The mouse pointer actually vanishes as I land in the new window and then re-appears a second later. It breaks the flow of the pointer movement and my eye must then relocate the cursor in order to click on anything, it's far from the "seamless" enviroment I have become accustomed to.

Don't get me wrong, Keyclone is WAY easier to setup than Octopus. If there's nothing I'm doing wrong and it is some "oddity" of my system is it possible to use the more advanced features of Keyclone (Roundrobin, hotstrings) while using the mouseover and maximiser from Octopus (with it's keysender disabled)?

<EDIT> Ignore the Octopus maximiser question, I've tried it and it works. It does however exhibit exactly the same mouseover focus delay and "loading screen lockup" behaviour.

<EDIT ... AGAIN> Using Octopus as maximiser with IT's focus follows mouse on and Keyclones equivalent disabled I get the smooth mousing between windows I had before. RR works nicely, just need to try hotstrings... But I need to learn how to do that first..

OK, I realise I am making many edits and now answering my own post but I have narrowed the issue to Keyclones "focus on mouseover" function. If I run Octopus with auto add windows set and use it's focus on mouseover everything is smooth and lovely even when starting the clients with the Commands and Maximiser from Keyclone.

Since I have started everything from Keyclone I should have full functionality (I think?), running a mostly disabled Octopus in the background for mouseover functionality is an acceptable workaround.