[Wii U] No controller rumble
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
Wii U controller rumble is either not supported or broken. Attempting to map a memory address to rumble the GamePad or other controllers performs no action.
Expected behavior
I configure a cheat file which conditions specific memory addresses to vibrate the controllers under certain circumstances. The controller(s) should vibrate under these conditions.
Actual behavior
The controller(s) do not vibrate when the conditions are met. I have tested this on both the Wii U GamePad and Wii U Pro Controllers, and it happens on every game and cheat config I use. I've tested it in the Snes9x and mGBA cores.
Steps to reproduce the bug
- Start RetroArch on Wii U through Homebrew Launcher and start a game
- Load a cheat file with rumble support
- Attempt to trigger the rumble
Bisect Results
I am unsure as to whether or not rumble was ever supported with RetroArch for Wii U.
Version/Commit
You can find this information under Information/System Information
- RetroArch: 1.10.3/dc2f6da
Environment information
- OS: WiiU
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
Begin by tracing Wii U controller rumble handling and the cheat-trigger path in RetroArch, comparing behavior with the Snes9x and mGBA cores. No source file or test is identified in the issue; done means a Wii U GamePad and Pro Controller vibrate when the configured cheat conditions are met.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100