Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

The Boundary Condition

A 3D/2D/1D puzzle-platformer exploring the physics of cross sections. · By thesquaregroot

System bug on Windows 10

A topic by kilgorezer created 21 days ago Views: 242 Replies: 4
Viewing posts 1 to 5
(3 edits)

OS: Windows 10 IoT LTSC 2021
Version: 0.2.8
Required Inputs: Keyboard/Mouse, Gamepad

Steps to reproduce:
1. Open the game.
2. Use the controller.
3. Switch to another window.

Expected behavior:
The mouse is released

Actual Behavior:
The mouse becomes locked where the client area of the game should be, even on alt+tab, unless security options is opened or the game switches back to keyboard and mouse input.

The issue appears to be a regression related to the hotfix for mouse capturing in version 0.2.8. While the original issue with keyboard/mouse input may be fixed, a new bug occurs when a gamepad is also connected. Steps 2 and 3 can be done in any order and the bug still occurs.

Developer

Thanks for this report! I’m wrapping up some other changes and am hoping to get another update out soon, so this is good timing. I’ll let you know when I’ve had a chance to take a look at this.

Developer

At least on Windows 10 Home, I wasn’t able to exactly re-create this. However, I did notice some similar issues whenever interacting with the game window, especially when in windowed mode. For example, it was difficult to move/resize the window since the mouse would get captured as soon as you started interacting with it.

I was able to avoid those issues by explicitly detecting when the window is unfocused and changing the mouse capture behavior until the game is focused again. I think it’s pretty likely this will address what you’re seeing as well.

This fix will be included in the next update, which should be coming soon, once I finish up testing.

Here is a video where I reproduce the bug. As it seems to be related to the window being unfocused, that should fix it.
Developer

Just (finally) posted an update that I believe should address this. When you can, please try it out and let me know if it’s fixed.