[Windows] [Input] Raw input driver not detecting any mouse movement
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
As indicated in the title, if the input driver is set to "raw" on Windows 10 x64 no input will be detected from the mouse. This is valid both for the Menu navigation (if Mouse Support is active) and for any content/core that supports mouse use.
Setting the input driver to "dinput" will restore mouse functionality as normal.
Expected behavior
Mouse should work normally with the "raw" input driver just like with "dinput".
Actual behavior
Mouse movements are not being detected.
Steps to reproduce the bug
- Set input driver to "raw"
- Save configuration and restart RA
- Mouse movement is non-functional
Version/Commit
You can find this information under Information/System Information
- RetroArch: 1.9.0 / 59f90dd
Environment information
- OS: Windows 10 x64
- Compiler: Mingw64
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue on Windows 10 x64 with the input driver set to "raw," following the listed restart steps, then inspect the Windows raw input driver entry point and compare its mouse handling with "dinput." Done means mouse movement works in menu navigation and mouse-enabled cores while using the "raw" driver.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100