Octopus has me totally confused....

[Dr4g0n3]

first off there needs to be a guide for dummy's :)

ok back story.

Two computers

one vista,server (1680x1050 screen res)

one xp x64, Client (1024x768 screen res)

they are not anywhere near each other so I cannot see the second screen



I can get the client to connect to the server, no problem, I set up the toggles to 1 2 3 on the numpad,

whenever I hit the mouse toggle it shoots all the way right on the client computer and I must move the servers mouse off my screen to the left to see it on the other.



I need help setting it so they are in the same spot at the same time ( if changing my server res to match the client that is no problem)

how would I achieve that?

and I just need it to broadcast 1-9, tab, wasd, and mouseclicks/Movement.

any other tips?

ill throw on the flame suit just in case.

[skarlot]

it goes like
a) if you toggle the cursor whilst on the server (within a game window), the client cursor should reposition in the same relative location, in the game window designated to 'receive cursor'...
b) if you toggle whilst on the client, server should reposition according to the client.

then from there they should track together, regardless of res/aspect ratio.

this is a function (the cursor part) that im reviewing next, but in my testing it does work ok, it just locks the current KVM screen.

i'm not sure why the mouse is shooting here or there, other than, the mouse is hidden in the bottom right whilst not in use.

[Dr4g0n3]

im sorry, did you answer my questions on how to get it running correctly?

if you did I cannot see it.



if I turn off the KVM the mouse does go to the bottom right of the client screen

if kvm is on i have to move it all the way left to see it on the client (but then i cant see if on the server)

[skarlot]

did you see the link to the guide octo.sourceforge.net ?

the KVM seems to work ok, but the cursor broadcast is independent, and should work with or without...

you have a window marked [m] on the server, and one marked [m] on the client, toggle cursor broadcast, and it should broadcast ok, thats all there is to it...

here is another thought, dont use the 64 bit version in conjunction with the newer 1.3.3 always use same version.

[Dr4g0n3]

oh yes, I have read it several times and gone through the "set up" multiple times,



the guide needs to be re-written, better wording and exact meaning and showings of what does what.

and im using the same version.

wish I could get help

[Ughmahedhurtz]

It sounds like maybe you have some cursor acceleration matching issues. In the 1.3.2 version I'm using, this works very well. Note that I use the KVM feature 24/7. Here are a few things you'll need to verify:
Control Panel --> Mouse --> Pointer Options tab --> make sure the slider for pointer speed is the same on both PCs and the "Enhance Pointer Precision" setting is unchecked UI Scale slider in WOW is exactly the same on all clients (you can do this more easily by editing the config.wtf and making sure the value for SET uiScale "x.xx" matches) Make sure all of your windows have focus. This is most readily ensured by enabling your server sounds for "enable key broadcasting" and "disable key broadcasting" and checking the box for "pause broadcasting when alt+tabbed"
Once the above are done, I just roll the mouse across all 4 machines so it "stabilizes"(*) the mouse accel on them and verify that the sound for "broadcasting is paused" dings on any of the clients, then I'm good to go.

Hope this helps.

* I say "stabilizes" because it appears that if you're on the desktop, octopus somehow uses a different pointer speed than if you have WoW open and in focus. Sorry I can't describe it better but I don't much care because it Just Works(tm). :P

[skarlot]

ok then, reality is I'm not going to rewrite the guide, it's already my 2nd go, and people constantly go yeah i need a manual, i need a guide for newbies, i dont have the answer - it would be better if somebody else wrote it all.

anyway,
"whenever I hit the mouse toggle it shoots all the way right on the client computer and I must move the servers mouse off my screen to the left to see it on the other."

all this shit was changed in 1.3.3, I'm sure 1.3.2 wouldn't behave like this. Which is why i need to go over it next. Just playing with it now, it's not quite right it seems. I do not have a testing team and shit theres just so much testing i can do. so sorry.

in reality it's using absolute positions while not mouselooking (any button down), i cant see acceleration etc affecting it.

give 1.3.2 a go or shock beta's multibox is another free thing that does the mouse broadcasting...

[Dr4g0n3]

i must be reading your guide wrong

because it is still not broadcasting the mouse keyboard and clicks to the second computer. and i have to run over there with my server mouse to click on any icons rather then them tracking together like you said.



instead of one guide maybe you should write multiple guides.

guess i wont be able to use this for AoC

[skarlot]

I will see if it works with AoC, out of curiosity

[Dr4g0n3]

on a side note I would really apprecaite some help, my wife doesnt have alot of time to play games so I would be leveling characters for her and such

i just need it to broadcast mouse movements, clicks, and some keyboard commands but it doesnt do it.



first queston about your "guide"

it doesnt state if I have to to run the same setting on my client computer

so do I have to have all the settings, names, and anything else set to the same?

another question

do I HAVE TO be running a game for this to work? all my testing has been just in the windows OS. if so your guide needs to state this

[skarlot]

Yes all the broadcasting is to the game windows in the client window list. No windows, no broadcast. The cursor part is even more fickle - it broadcasts to the window area not the desktop. using cmd.exe is a good place to test the key broadcasting.. not notepad. AoC, which won't patch right now, is linked with DirectInput which reads the mouse events pre mouse hooks (the normal way it's done). hence is why there is a mouse filter driver to further complicate things. But that doesn't mean Conan is actually using the DirectInput mouse, but theres a fair chance I'd say. I supose it's the same for keyboard, too.

[Dr4g0n3]

ok so I need to set it up to open cmd.exe instead of aoc right now, correct?
if so, how?


I can get the server to open a progam, but it will not open or do anything on the client computer.

do I need to load it by hand?



also my settings never saved, is this a bug in 1.3.2?

[Dr4g0n3]

ok here is a screen shot of all the windows I made changes too on the server computer (name as main)

do these need to all match on the client computer? (named as kassie)
http://img382.imageshack.us/img382/3610/octopusscreenoe7.jpg

[Ughmahedhurtz]

On your keys page, if you don't check the "Whitelist" box, adding keys in there effectively blacklists those keys.

Does look like your client is connected, though, which means it should start working assuming AoC doesn't have something screwy going on with the way it does clicks/keys.

[Dr4g0n3]

I have the keys button checked now, it was before but it isnt saving any of my settings

[Ughmahedhurtz]

I assume you're running the octopus as administrator? Not doing that would cause settings not to write to disk.

[Dr4g0n3]

this last instance (screen shot one) i started it as admin because it was giving the " no cursor broadcasting window found" not sure what this means,

[Dr4g0n3]

do I have to start the games by hand then enable octopus?

[Ughmahedhurtz]

I start mine manually with octopus already running, then it just picks up the windows and off I go. I don't know if octopus can start them for you.

[skarlot]

AoC works ok, the only issue is the cursor doesn't link off the right side of the screen, and probably the bottom too. you add to the windwo list via running an instance, or via auto add by title/process.