[Feature Request] Add Windows.Gaming.Input API support
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
First and foremost consider this:
- Only RetroArch bugs should be filed here. Not core bugs or game bugs
- This is not a forum or a help section, this is strictly developer oriented
Description
Request to add support for the Windows.Gaming.Input API.
Benefits include Xbox One and Series controller trigger rumble motors to be utilized.
Also, support for the Share button on Xbox Series controller to be detectable and mappable, as well as possibly better battery level detection, though currently all xbox controllers under retroarch on windows doesn’t detect at all.
Possibly the newest input standard for Windows builds, with possible benefit of utilizing dynamic latency input.
Environment information
Windows 11
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
No files, tests, or entry points are named in the issue. Start by locating RetroArch's Windows controller-input path and determine where Windows.Gaming.Input support would fit; done would include the requested trigger rumble, Share-button mapping, and improved battery detection where supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100