The mouse is hard to catch in `for-0.55.0/sync`

[illwieckz]

It usually happen after some alt-tab, for some time the engine freezes, then after that the engine fails to really capture the mouse:

20240513-062759-000.unvanquished.webm

[illwieckz]

We see in the video that sometime the mouse is captured but not centered, and sometime centered but not captured.

[illwieckz]

This was recorded after #1134 is merged but was first experienced before:

• https://github.com/DaemonEngine/Daemon/pull/1134

So, this is another input bug unrelated to the one fixed in #1134.

[illwieckz]

A vid_restart fixes the bug.

[illwieckz]

I got a variant: after pressing [Escape] to open main menu, I got a huge lag, then the main menu appeared.

I can then cycle the opening and closing of the main menu with [Escape], but my mouse can't move the player view anymore once the menu is closed. After some alt-tab the mouse moves the player view again but is not centered again.

[illwieckz]

I tried to go fullscreen with Alt-Enter but game freezes and the log went full of:

Com_QueueEvent: overflow 
Com_QueueEvent: overflow 
Com_QueueEvent: overflow 
Com_QueueEvent: overflow 
Com_QueueEvent: overflow 
Com_QueueEvent: overflow 

And the game got minimized to return to Desktop (probably a window manager decision).

[slipher]

How about some repro info. Window manager? X vs Wayland? SDL version?

[VReaperV]

I've had this with the current for-0.55.0 branch on win10 I think. It was either this or the keyboard input not being captured after tabbing out to a different program and back. I'll see if I can reproduce the issue later.