search

ndeadly / MissionControl

Use controllers from other consoles natively on your Nintendo Switch via Bluetooth. No dongles or other external hardware neccessary.
GNU General Public License v2.0
2.56k stars 141 forks source link

[Bug Report]: unstable while using missioncontrol.ini #566

Closed Abraham79 closed 1 year ago

Abraham79 commented 1 year ago

Switch Firmware Version

14.1.2

Atmosphère Version

1.4.0 (Latest)

Mission Control Version

0.8.0 (Latest)

Boot Method

Fusée

Issue Description

If missioncontrol.ini is present (and edited) pairing up to 2 original joycons is OK, pairing a third one resets them all. Sometimes it works after a few tries, most times it resets again after choosing order and pressing A to confirm, showing none or one single joycon connected. Works as expected with two cotrollers but no more than two while missioncontrol.ini is present.

Error Report

No response

Additional Context

I have edited host name and mac while I was -unsusccessfully- trying to use the same controller on different devices whithout the need for re pairing to each device anytime.

I have deleted missioncontrol.ini and everything is working again as expected

ndeadly commented 1 year ago

You'll have to explain your setup in more detail. I suspect this problem may just be due to the nature of what you're attempting to do.

If you change the MAC address of your console, then controllers that were already paired with it will now store invalid pairing data for the console. Joycons can do Bluetooth pairing when connected via the console rails, and sometimes refuse to update their pairing information when this is the case. Wiping the pairing database may be required, before re-pairing each device wirelessly.

Another possibility is that you're spoofing the address of another device that is still in range with Bluetooth active. Two simultaneous devices broadcasting with the same address will likely confuse the controllers and cause weird things to happen. This feature assumes that either the secondary device is switched off or has Bluetooth disabled, or is located in a different physical location where it is out of range of the controller.

Lastly, this feature is aimed at more of a "power user". In order to work, it requires dumping of the pairing information from the last device the controller was paired with (or the controller itself), and injecting this information into the pairing database of the second device. I provide no tools to automate this since there are many possible configurations. You will need to do this manually for the feature to work.