-
-
Notifications
You must be signed in to change notification settings - Fork 137
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]: Mission Control not running? #784
Comments
I have similar issues on
Trying to pair two different dualshock 4's, when i try to pair one i get a pop-up of pairing on the Switch, but nothing shown in the controller slots, and the controller shuts off immediately and no input, pressing the PS button to turn it back on results in it just turning off again. The second controller is practically the same, except i don't get the pop-up. Is this the same behaviour you observe? |
The main reasons for a controller being disconnected after pairing are
|
Hi ndeadly,
is there any other possible error source im not seeing? Would love to use Mission Control again. |
Try the archive bit fix in hekate |
Switch Firmware Version
17.0.0 (Latest)
Atmosphère Version
1.6.0 (Latest)
Mission Control Version
0.10.0 (Latest)
Boot Method
Hekate
Issue Description
Hi there,
yesterday I updated my V1 switch to
Hekate 6.1.0
Atmosphere 1.6.2
Firmware 17.0.1
MissionControl 0.10.0
Unfortunately it seems like Mission Control is not running at all... cannot connect either my ps4 DualShock or Wii controllers... wich have been working on previous versions.
I tried updating Mission Control but also did a uninstall and fresh install.
Error Report
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: