Win + g prevents from using hotkeys
See original GitHub issueDescribe the bug:
If using Windows
+ g
to open the Xbox Game Bar while in the game, keys (such as Escape
to go back, Space
to go forwards… will not work)
Note: key tapping still works during songs, but hitting the Space
key to skip will not work.
Switching windows and back (Alt
+ Tab
ing or clicking another app and clicking back on Osu!) fixes the problem.
Screenshots or videos showing encountered issue: Video
osu!lazer version: osu 2021.109.0.0 (issue since late 2019/early 2020 might have been since longer though)
Logs: logs.zip
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
Fix problems with Xbox Game Bar on Windows
If Xbox Game Bar doesn't appear for a full-screen game, try keyboard shortcuts: Press the Windows logo key + Alt + R to...
Read more >Disable Press Win + G to open Game Bar - voidtools forum
In the Task Manager, click the Services tab. Right click and click Stop Service. Open Windows Explorer. If prompted with a Access Denied...
Read more >4 Ways to Fix Keyboard Shortcuts Not Working in Windows ...
7 Ways to Fix Keyboard Shortcuts Not Working in Windows 10 · 1. Check Yiour Keyboard Hardware · 2. Turn Off the Keyboard's...
Read more >How to disable Windows Gamebar mapping? [duplicate]
I have been a happy Gridmove user for years, and I use the combination Win + G to change into the "send window...
Read more >Xbox Game Bar is not working. 3 ways to fix it in Windows
The Windows + G keyboard shortcut is not working? You can't enable the Xbox Game Bar? Here are three things you can do...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This should already be fixed in the latest version.
I see, that helps heaps. Means the key is getting stuck in a depressed state, according to SDL2. I’m guessing it’s also timing dependent, since I can’t reproduce by progammatically sending the keystrokes.