I’m experiencing an issue that happens only when launching my macOS build from Steam (by clicking the green Play button).

If the player moves the mouse during the initial loading phase, the game window later requires double-clicks to interact with UI elements (as if the first click only focuses the window). Disabling the Steam Overlay does not prevent this.

I believe this behavior is specific to being launched from Steam, and I’m saying this based on the following tests:

1.Steam SDK removed, launched directly from the Desktop (outside Steam):
Works normally — single-click input works even if the mouse is moved during loading.

2.Steam SDK removed, added as a “Non-Steam Game” and launched from Steam:
Works normally — no issue regardless of mouse movement.

3.Steam SDK included, launched from Steam (green Play button):
If the player does not move the mouse for the first few seconds (while the Steam overlay toast appears), the game works normally.
If the player moves the mouse during that period, the game then requires double-clicks to interact with the UI.

4.Steam SDK removed but the build is uploaded to Steam and launched via the Play button:
Same outcome as (3): moving the mouse during startup causes the game to require double-clicks afterward.

Environment: macOS (Mac mini M2, 2023). I can upload the exact builds used for testing to my Steam pipe (“Creator Chronicles”) if that would help.

I also tried adjusting macOS entitlements and changing activation order, but the issue persists.

Is there anything additional I need to do for macOS builds when launching via Steam?
Any recommended flags, entitlements, or initialization steps to ensure the game window becomes the key window and accepts single-click input immediately would be greatly appreciated.

Thank you very much for your help!