When SetInputMode_GameOnly is applied on a PlayerController and the application runs in windowed mode on a multi-monitor setup, the Windows OS shortcut Win+Arrow (window snapping) stops functioning once the window is moved across a monitor boundary.
This appears to be an interaction between UE's input capture (FInputModeGameOnly → CapturePermanently mouse capture) and the Windows shell snap handling. While the window holds input capture and crosses a display boundary, the shell no longer receives the snap key input correctly.
Workaround (confirmed behavior):
After the issue occurs, clicking the window, or pressing Win alone to open the Start menu and then refocusing the app, restores normal behavior (capture/focus re-syncs).
Note: This is a Windows standard OS feature, so this may be a Windows-side constraint rather than a strict UE bug. Filing to confirm whether the capture behavior of FInputModeGameOnly should be adjusted, or whether this should be classified as By Design.
Expected Result:
Win+Arrow window snapping continues to function normally after the window crosses a monitor boundary.
Actual Result:
Win+Arrow snapping stops responding once the window crosses a monitor boundary until focus/capture is manually re-synced.
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-386734 in the post.
| 0 |
| Component | UE - Editor - UI Systems - Slate |
|---|---|
| Affects Versions | 5.8 |
| Created | Jul 15, 2026 |
|---|---|
| Updated | Jul 15, 2026 |