New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Wii U] Erratic input management on most cores #14935
Comments
It might be interesting to note that FB Alpha and Mame work fine, and those setup initially Wii U Gamepad to "port #0". It also seems to me that there is something fishy about a +1 translation, since I have the impression that port #2 controls the menu in other cores. I've just found out that if I switch port 2 from, say, Wii U Pro Controller, which could control the menu just before that, then it can't anymore. |
Good temporary fix : use core settings to remap Port 2 to Player 1 (and Port 3 to Player 2 etc). This works flawlessly. But the problem is that then one cannot use hotkeys anymore... |
Hello. Did anyone find a solution to this ? |
Yes. What I've written just above your post works perfectly (and is the ONLY solution that works). Except for hotkeys... Home button works. Do this procedure core by core and use "save core remap" (or something like that) so that it remembers it next time. |
Cool I have to try. |
Sorry to disturb, but I really can't find where to remap ports for each core |
Thanks so much man. |
Description
On most cores (everyone I've tried besides FB Alpha and Mame), input management is very erratic on Wii U.
Expected behavior
Actual behavior
See description.
Steps to reproduce the bug
Bisect Results
Happened since as long as I can remember, even though I haven't been testing intermediate builds since around a year ago and until now.
Version/Commit
Latest nightlies.
Environment information
Wii U.
The text was updated successfully, but these errors were encountered: