FPS camera and windowed mode

Acki · Post by **Acki** » Tue Dec 16, 2008 11:47 pm

Hi,
I'm not sure if this is intended to be like it is, though...
I tested this with the special fx demo (#08 )...

when you create an app in windowed mode and using a fps camera, then if you move the mouse fastly sideways (look around) so the mouse gets out of the window the movement (rotation of the cam) stops and the mouse curser stays outside the window until you move it back over the app's window...

I think this is a bug, because you can't play a game in windowed mode where you have to turn around fast...
let's say an enemy stands behind you and you want to turn around to shoot him, then you can't do this fast, because the mouse gets out of the window and you don't rotate anymore until you move the mouse back over the window...

Dorth · Post by **Dorth** » Wed Dec 17, 2008 12:19 am

Actually, I think it's better for a developer to code a "net" for the cursor than having it by default

hybrid · Post by **hybrid** » Wed Dec 17, 2008 12:42 am

Why would you use windowed mode then

Also, might be a problem with your Desktop setup, maybe your window manager grabs the focus?

Acki · Post by **Acki** » Wed Dec 17, 2008 1:55 am

hybrid wrote:Why would you use windowed mode then

what a question is this ?!?!?

why should I not use windowed mode, or at least let the user decide to use fullscreen or windowed ???

hybrid wrote:Also, might be a problem with your Desktop setup, maybe your window manager grabs the focus?

no, the focus always stays on the app's window and I also don't press any mouse buttons to change the focus...

maybe someone can test this with the examples from the sdk where a fps camera is used (02.Quake3Map, 07.Collision, 08.SpecialFX, ...) ???
start them (they are in windowed mode by default) and move the mouse fast sideways...
I think it's easiest to see with 08.SpecialFX with realtime shadows, because it's more hardware challenging and the mouse updates not as often as (e.g.) with the 02.Quake3Map example...

sudi · Post by **sudi** » Wed Dec 17, 2008 3:58 am

Acki is right.
Same here.

rogerborg · Post by **rogerborg** » Wed Dec 17, 2008 11:47 am

Yup, that looks like a bug. It's escaping completely on Windows, and on Ubuntu 8.10 (in VmWare) it temporarily escapes but then gets recaptured again. I'll look into it... wait for it... waaaait... now.

Hah, got it. A very quick movement can take the cursor out of the window in a single tick. We then don't get any more mouse events for it, but we still think that it's at the window centre, and so never set it back there.

I've made the position setting unconditional in CSceneNodeAnimatorCameraFPS::animateNode(), so that we always grab the pointer back again.

This does mean that if you do smgr->drawAll() without checking device->isWindowActive() then the cursor will always be moved back even when you switch windows (e.g. to a debugger). However, it's the most robust solution. I tried registering for WM_MOUSELEAVE messages on Windows, which did help, but was still able to escape the logic and lose the pointer with very frenetic movements. If anyone can get that working robustly, knock yourself out.

1.5 branch : SVN 1965
Trunk : SVN 1966.