Octopus - oddities with Clicks

[Maricksville]

First off this is my first time trying to set up dual boxing so Im a bit of a noob. Have tried using Octopus and love it, my one gripe being that Clicks are really annoying to the point that I cant use them.

Im running 2 WoW clients off the one machine, a priest and druid. My main aim is to powerlevel them both. When I enable broadcasting Clicks in Octopus one of these random things will happen:

Client 1: Click Spell > Client 2: Nothing

Client 1: Click Spell > What looks like a really quick alt-tab, the screens go funny then Client 2: Spell fires

Client 1: Click Spell but nothing happens > Client 2: Spell fires

Right now Ive got Broadcast Clicks off cause I cant actually move in the game. If I Click anywhere on the terrain the screns alt-tab really fast and the camera angle that I come back to in Client 1 is completely random, sometimes facing straight up in the air.



Anyone know how I can fix this cause Id really like to have Clicks broadcasting. Cheers

[jefflo]

im having the same problem, is thier any settings that would fix this or some where missing im also new at this trying out 2 locks

here's one example that i can reproduce all the time, ive set up maximze to split the windows in 2, at log on screen in wow i click username tab its good it set to have the login name already for the two account, then i move on to password, i click on it is ok i enter password both of them are the same, then when i press loging only the 2nd display will be successful in the click i have, its like its very hard to click on the main window, i see 2nd window grabing the cursor its like its grabing it to fast or something i have to keep on clicking on the loging screen so it can click it, same thing when im ingame, try to click buttons for spells foods and other stuff is very hard, what you guys think is the fix for this

btw i love this software and its free =)

[skarlot]

The lower timings (event wait/foreground wait) the more chance the camera is gonna go whacko or miss a click.

In the case of the foreground window missing the click before it switches to and back from instance 2... try increase Event Wait.

Foreground wait is just an additional delay one can add to the mix if click down's are being missed...

But generally event wait is for any click or movement... to give time for WoW to process it before getting confused....

Cameras going whacky, my best guess, is its moving to the next window too fast for WoW with the default values, so it receives a relative movement whilst WoW *thinks* the mouse is down. Of course even with 0 ms event wait Octopus will have said release the click prior to moving, but I expect Blizzard dev's were not too concerned about making it respond to clicks for a <100 ms session.. who knows what they are doing, probably processing movement before clicks. One can only speculate. But since they can't even write follow code, do you expect them to write it for <100 ms clicks turbo alt tab style???

The original post didn't even mention the timings, I should probably write in bold text WoW only accepts clicks in the foreground. Alt tabbing is not random, its necessary, its the timings that are critical.

if you increase the timings to 500ms say, you'll see the problem is probably not with my code, but how WoW responds under pressure :P

[jefflo]

ic i tryd the timing its working now
so altab is normal fo clicks to work right?

if i go the 2 pc route with dual box will this prevent the tabbing part coz i have 2 separate computer with two separate mouse cursor?

or is thier a way software side that would let say give a 1 cursor per wow window running? so it doesnt go the tab route and swicthes windows and use the same cursor? like the key stroke thing

[skarlot]

yea with 'cursor broadcasting' its live on 2 PC's... as is MultiBox.

no is the short answer for doing it with software unless your really keen and skilled... then maybe, maybe.