Capture mouse cursor in client? Tweet

[AddisonHigham]

According to the API docs (http://aws.otoy.com/docs/OTOYClientAPI.pdf), CURSORS=1 is supposed to capture the mouse cursor.

Here is the full command:
http://aws.otoy.com/?connect=//<IP>:8090/?START=D%3A%5CPrograms%5C<Command>.exe;CURSORS=1;NOCRYPTO=1;STATUS=1;AUTOLOCK=0;FULLSCREEN=1;WAN=45;GUID=<GUID>

Upon connecting, it doesn't seem to capture the cursor (nor go fullscreen). This results in mouse movements in a game to not work at all.

Any hints? Am I doing something wrong?

[Goldorak]

Not all ORBX parameters work in all browsers at the moment - note that this list is for native ORBX, of which ORBX.js implements about 90% at the moment. Pointer lock and full screen are not uniformally implemented in all browsers, but we're working around this in an update due next month for ORBX.js.

[ronjart]

On the same note, I've tried to change the resolution via WIDTH= and HEIGHT= but had no effect - same when I try BORDERLESS=.

I've tried in Firefox and Chrome.

When I change the resolution on the cloud-desktop, the connection freezes.

I'm just looking for a way to run full-screen (which I can getting to work by running my browser full-screen) at my host PC's resolution. Any pointers?


Thanks.