-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
[Bug Report]: #853
Comments
Use the button tester in the system menu to check which buttons are mapped to what, if any are missing, and what that button combination is actually doing. There is no button combination involving such buttons in the mission control code, so something must be mapping incorrectly, or you have an issue with your hardware. |
here is the mapping parameter that is displayed when I do this combination: 0000 I 04 80 80 80 80 00 00 10 11 00 But also note that a long press of this same combination( approximately 1.5 seconds) in the test application automatically activates the mouse mode of the controller (because it seems that the mocute 53 has two modes: controller mode and mouse mode) look what parameter is displayed 0000 I 03 00 00 10 00 00 And when I do this combination again I automatically exit the mapping test application, which is somewhat normal since the plus key is supposed to exit the application |
I meant the official Nintendo button test in the system menu, to see what the inputs are registering as to the console. Raw data doesn't matter if something in between is modifying it, for example |
Switch Firmware Version
18.1.0 (Latest)
Atmosphère Version
1.7.1 (Latest)
Mission Control Version
0.11.1 (Latest)
Boot Method
Fusée
Issue Description
The issue occurs with the Mocute-053 controller. It seems the combination of these 3 buttons L+L3+A( ON MOCUTE-53
CONTROLLER) automatically got the same use as PLUS button (Start/Pause) and this can be very disturbing mostly while playing games like EA FC where combinations are done in the heat of the action and then the game pauses.
Error Report
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: