Emulator

What's the problem? Describe what went wrong.

I'm having an issue where Dolphin's keyboard hotkeys don't work, and the hotkey settings (Options > Hotkey settings) also show some weird behaviour. From the first build with issues up to the most recent build, there were differences in behaviour that I tracked down by testing more builds, showcased below.

Build 9865 is the last properly working build from my tests, with no weird behaviour.

Starting at build 9869 (nice):

• with a controller connected: the keys stop working, both in-game and in the hotkey settings
• if my controller isn't connected: hotkey settings work fine until I hit the reset button from there, but opening the settings borks it in-game. If go in-game without opening settings, it works until I close and reopen the game without closing Dolphin. Opening the hotkey settings at this point borks both.

Starting at build 9876, it stops working at all, even with no connected controller.

Starting at build 10123, a PR was made where Dolphin doesn't refresh devices when opening the mapping UI. As a result, I can actually change the keys in the hotkey settings, until I hit the Refresh button there. The keys don't ever work while in-game. Whether my controller is connected or not doesn't change these behaviours.

This is the same behaviour up to the most recent build tested (11050).

Game Name / Game ID / MD5 Hash? Not applicable

What steps will reproduce the problem? Open a game on Dolphin. Hotkeys won't work.

Is the issue present in the latest development version? Yes; 11050

Is the issue present in the latest stable version? No (5.0)

If the issue isn't present in the latest stable version, which is the first broken version? 9869

If your issue is a graphical issue [..] Not applicable

What are your PC specifications?

Intel i5-6600, GTX 1070, Windows 10 1903 (18362.418), 8GB RAM.
Using a generic 'Wired backlighting gaming keyboard' (no proper name is put anywhere)
Dualshock 4 controller with DS4Windows/HIDGuardian

Is there anything else that can help developers narrow down the issue?

This might have some relation with issue 11702. I think my issue used to be more like that (I even commented so there), but I might have just used a older build and I can't confirm whether that is the case anymore.