ZDoom

Graf Zahl wrote:What I cannot say is if RawInput provides any advantage for mouse handling.

IIRC it works a lot better with high polling rate mice (DInput would skip mouse clicks, delay them, etc), as well as providing a bit more accurate acceleration.

I'm moving this to on hold because this was reported at DRD Team years ago and it was pretty much stated there that this may be unfixable - but nevertheless this wasn't closed there nor here but it shouldn't help clutter up the newer reports.

Nevertheless, the issue is acknowledged, and I am sure there is every intention to fix it - it's just a question of finding the best fix.

This is a perfect case where some feedback from Randi would be appreciated. I'm simply not sure what the initial motivation for the cursor locking was.

I think for me this happens only then GZDoom doesn't get the focus on startup.

Unfixable? Capturing mouse/hiding cursor when the window gains focus (or every second/frame) is impossible?

It is put on hold because nobody here understands the motivation behind this code.