Project

General

Profile

Actions

Emulator Issues #12504

closed

Whether or not hotkeys work at all during gameplay in dev builds of Dolphin QT on Windows 10 x64 is seemingly completely random. Restarting the emulator an arbitrary number of times appears to be the only solution.

Added by Akira13645 almost 3 years ago. Updated about 1 month ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

What's the problem? Describe what went wrong.

The title says it all, really. This is a persistent, extremely annoying problem. My usual "fix" is to just immediately press the screenshot key when launching a game, and if it doesn't do anything, continually close and re-open the emulator while repeating the process until it works, at which point I know hotkey presses are being detected and I can go ahead and play.

What steps will reproduce the problem?

Simply attempting to use hotkeys in master branch builds of Dolphin QT on Windows 10 x64.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

It has been present for months and months in master branch builds.

Is the issue present in the latest stable version?

I don't think this is very relevant as stable Dolphin is IMO woefully outdated in numerous unrelated ways, but for the sake of completeness I went ahead and checked, and yes, actually, it is present, in the same way.

What are your PC specifications? (CPU, GPU, Operating System, more)

  • i7-4771
  • 16GB DDR3-2400 CL10
  • GTX 1660 Ti
  • Windows 10 Pro x64

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

I don't think so. This pretty clearly is some kind of weird DInput / XInput / etc issue within the code of Dolphin itself.

Actions #1

Updated by JMC4789 over 1 year ago

  • Status changed from New to Questionable

Is this issue still present in the latest development builds? I believe it was addressed at some point. Please test to reconfirm.

Actions #2

Updated by Billiard26 about 1 month ago

  • Status changed from Questionable to Fixed

No response from OP. Will re-open upon request.

Actions

Also available in: Atom PDF