ndeadly / MissionControl

Use controllers from other consoles natively on your Nintendo Switch via Bluetooth. No dongles or other external hardware neccessary.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[Bug Report]: Mission Control not running?

tomtom-H opened this issue · comments

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

I have similar issues on

  • Horizon 16.0.3
  • Atmosphere 1.6.2
  • Mission Control 0.10.0

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

  • low battery
  • corruption in /config/MissionControl/controllers
  • the controller isn't an authentic one from sony

Hi ndeadly,

  • battery of the controller is fully charged
  • i deleted and freshly installed mission control, which should eliminate the chance of having a corrupted config
  • ps4 DualShock is an authentic Sony one

is there any other possible error source im not seeing? Would love to use Mission Control again.

Try the archive bit fix in hekate