Homebrew RELEASE MissionControl: Use controllers from other consoles natively via Bluetooth

ndeadly · Sep 3, 2020

Ratatattat said:
I used to play Mario Kart 8 on the wiiU with the Wii steering wheel. I purchased Mario Kart 8 for the Switch but hate those tiny steering wheels. And NO i am not worth a crap trying to use joystick control. My question is... is there now a way to hook MISSION CONTROL up and use that to use the wii controllers with the wii wheel on Mario Kart 8 on the Switch?

Once motion controls are implemented this might be doable. Do you know if MK8D supports motion controls natively? I've only ever played using the analog sticks.

Ratatattat · Sep 3, 2020

ndeadly said:
Once motion controls are implemented this might be doable. Do you know if MK8D supports motion controls natively? I've only ever played using the analog sticks.

I know the small Switch steering wheel works the same as the wii controller with the wii steering wheel. So that should mean it has native motion control. The real question becomes can the wii remotes motion control be read by the switch then?

ndeadly · Sep 3, 2020

Ratatattat said:
I know the small Switch steering wheel works the same as the wii controller with the wii steering wheel. So that should mean it has native motion control. The real question becomes can the wii remotes motion control be read by the switch then?

Sounds like it's supported then. All non-switch controllers are mapped to look like a Switch Pro Controller, and any controller that supports motion will be converted to this format when I get around to adding the feature.

Bachato · Sep 3, 2020

*Deleted*

KamelColtd · Sep 4, 2020

Thank you very very very much
want to ask when the 2nd release .
For DS3

m3anmug · Sep 4, 2020

This is awesome. Just wanted to say thanks.

ndeadly · Sep 4, 2020

KamelColtd said:
Thank you very very very much
want to ask when the 2nd release .
For DS3

I'll make a bugfix release soon to fix the crashes people have been seeing due to a bug in DS4 battery level handling. No ETA on DS3 support though. It's not as straightforward as just adding another controller mapping.

Shoruk3n · Sep 4, 2020

Is the modified boot2 included in the git release download?

ndeadly · Sep 4, 2020

Shoruk3n said:
Is the modified boot2 included in the git release download?

Yeah, it's present in the zip. Just got to make sure you say yes to overwriting existing files when you extract to your SD

KamelColtd · Sep 4, 2020

ndeadly said:
I'll make a bugfix release soon to fix the crashes people have been seeing due to a bug in DS4 battery level handling. No ETA on DS3 support though. It's not as straightforward as just adding another controller mapping.

awesome work thank you veryyy much i just register to say thanks.
anyway i just boughed DS4 and want to say thankx everyday
Good job

Shoruk3n · Sep 5, 2020

I had it working earlier today, but suddenly when I turn on my ps4 controller my switch crashes. I did charge my controller, so I'm guessing this is the battery level issue. Eagerly waiting for a fix!

MUDD_BR · Sep 5, 2020

This is an awesome work. I apply it to a pro controller from wiiu and you just need to sync once, it works like a charm, thanks again!!!

ndeadly · Sep 5, 2020

Shoruk3n said:
I had it working earlier today, but suddenly when I turn on my ps4 controller my switch crashes. I did charge my controller, so I'm guessing this is the battery level issue. Eagerly waiting for a fix!

I've posted a build that fixes the issue on several of the GitHub issues regarding DS4 crashes if you want the fix before the next release.

Giosandoval · Sep 5, 2020

I'm a sx os user and I love it because I can use my hdd and xci files.

My suggestion to anyone using sx os and want to use mission control and does not want to completely change to Atmosphere is to have a multi boot manager, that's what I did and it's working great, mission control is awesome.

Here is the link with the great retro reloaded boot manager I'm using.

https://github.com/RetroGamer74/RR_RetroReloaded/blob/master/README_EN.md

Or you can wait for team xecuter or some dev to port it.

Shoruk3n · Sep 5, 2020

ndeadly said:
I've posted a build that fixes the issue on several of the GitHub issues regarding DS4 crashes if you want the fix before the next release.

Thanks for that! I'm only somewhat familiar with github, not quite sure how to download anything that's not release though.

Deleted User · Sep 6, 2020

ndeadly said:
MissionControl

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

Features

Supports all firmware versions

Pair Bluetooth controllers natively via Change Grip/Order screen

Native button remapping (firmware 10.0.0+)

btdrv-mitm sysmodule adds extension IPC commands that can be used to interact with the bluetooth process without interfering with the state of the system.

Supported Controllers

Currently, the following controllers are supported. If you have a third-party variant of one of the below, or a Bluetooth controller that isn't listed, consider submitting an issue with the controller details, including vid/pid, to request support.

Nintendo Wii Remote + extensions (Nunchuck, Classic Controller, Classic Controller Pro, SNES Mini)

Nintendo WiiU Pro Controller

Sony DualShock4 Controller

Microsoft Xbox One S Controller*

*Not all Xbox One wireless controllers support Bluetooth. Older variants use a proprietary 2.4Ghz protocol and cannot be used with the Switch.

Requirements

Hackable Nintendo Switch running the latest Atmosphère CFW

Compatible Bluetooth controller

Installation

Download the latest release .zip and extract to the root of your SD card. A console reboot is required in order for MissionControl to become active.

Note: Currently a modified boot2 is required to launch btdrv-mitm early enough to intercept Bluetooth initialisation. This will get overwritten any time Atmosphère is updated on SD, and will need to be replaced.

Usage

Install MissionControl to your SD card, reboot the console and then pair controllers as you normally would via the Controllers->Change Grip/Order screen. Once paired, controllers will reconnect automatically when woken up.

Most native features should just work (with the exception of things like firmware update). If you find something that's broken please create an issue.

Pairing controllers

The supported controllers each have their own methods to enter pairing/sync mode. Below are instructions on entering this mode for each supported type

Wii(U) Controllers
Press the red sync button on the back of the controller. The controller LEDs will blink rapidly

Dualshock4 Controllers
Press and hold the PS + share buttons simultaneously until the lightbar starts blinking. When done correctly the blink pattern will resemble a heartbeat, otherwise it will blink periodically.

Xbox One Controllers
Press and hold the guide(X) button until the LED starts blinking. Then press and hold the small sync button on the back near the charging port until the LED starts blinking more rapidly.
You should also ensure your controller firmware is up to date, as old firmwares were known to have flakey bluetooth.

Planned Features

Controller management application

Rumble support

Motion support

Keyboard and mouse support

Frequently Asked Questions

Does this support USB controllers?
No. MissionControl is Bluetooth-only for now.

Does this work with sys-con installed?
Yes, I have had several reports from users that the two can be used together without issue.

Why have my official Joycon/Switch Pro Controllers stopped working over Bluetooth after installing MissionControl?
It is possible to pair these controllers via the Joycon rails or a USB connection. In these cases a garbage hardware ID gets stored to the pairing database and the controller fails to be identified. This issue can be resolved by using the Disconnect Controllers option in System Settings with the controller disconnected from the system, and then re-pairing via bluetooth in the Change Grip/Order screen.

Why doesn't my 3rd-party knockoff controller work?
Many 3rd-party controllers also use garbage hardware IDs, making them difficult to identify reliably. If a controller can't be identified, I ignore it, since I have no idea how to process the incoming data. I am currently trying to find an alternate way to identifying them without creating problems elsewhere.

Can you add support for PS3 controllers?
It's on my list of things to look into. The pairing process is non-standard and may require modifications to the bluetooth driver. If it can be done non-destructively I will add support eventually.

Can you add support for Xbox 360 controllers?
No. These don't use Bluetooth. Try sys-con with a wireless USB adapter.

Can you add bluetooth audio support?
No. The bluetooth module on the switch only implements a small set of services required to make hid controllers work. Of this small set of services, only a handful of high-level functions are exposed to the rest of the system. Adding audio support would require implementing the services neccessary for audio transport, for which any sane person would require an open-source re-implementation of the bluetooth module in order to have access the low-level functions required to pull it off.

Known Issues and limitations

Non-Switch controllers cannot be used to wake the system from sleep.

Controllers that haven't had their hardware ID whitelisted for identification will not be recognised as connected. This can include some official Switch controllers. They will however still pair with the console and store their details to the database. If you encounter such a controller, please create an issue requesting support.

Wii(U) controllers can take a while to pair with the console. For some reason they are only detected at the end of a device discovery cycle. Be patient and re-press the sync button on the controller if neccessary.

Xbox One button layout was changed at some point in a firmware update. Please ensure your controller firmware is up to date if you have issues with incorrect button mappings.

Games with motion controls experience a drift on non-switch controllers when motion controls are enabled. I will fix this in a future release. For now most games should allow you to disable motion controls as a workaround.

Link: https://github.com/ndeadly/MissionControl

The system cant seem to find/pair with DS4 controllers while a game is running. Once I closed out of slay the spire(in case it makes a difference) my system found my controller right away

ndeadly · Sep 6, 2020

Shoruk3n said:
Thanks for that! I'm only somewhat familiar with github, not quite sure how to download anything that's not release though.

Check out this issue. Scroll down for the download link.

Sasori said:
The system cant seem to find/pair with DS4 controllers while a game is running. Once I closed out of slay the spire(in case it makes a difference) my system found my controller right away

It's better to file this as an issue on github so I can follow it up more easily. Not familiar with that game, but it might cause the switch to send commands to the controller than I don't currently handle. Does this happen with any other non-switch controllers?

Alvsar · Sep 6, 2020

Giosandoval said:
I'm a sx os user and I love it because I can use my hdd and xci files.

My suggestion to anyone using sx os and want to use mission control and does not want to completely change to Atmosphere is to have a multi boot manager, that's what I did and it's working great, mission control is awesome.

Here is the link with the great retro reloaded boot manager I'm using.

https://github.com/RetroGamer74/RR_RetroReloaded/blob/master/README_EN.md

Or you can wait for team xecuter or some dev to port it.

Cannot you do exactly the same from the boot in SXOS and call Atmosphere from there?
I hope Sxos is updated to allow the use of this tool for the same features you mentioned in your post at the beginning.

ShadowOne333 · Sep 6, 2020

I have copied over the MissionControl files and all, but for some reason now sys-clk is no longer working?
Is it known if this app clashes with sys-clk in any way?

ndeadly · Sep 6, 2020

ShadowOne333 said:
I have copied over the MissionControl files and all, but for some reason now sys-clk is no longer working?
Is it known if this app clashes with sys-clk in any way?

If it does, this is the first I've heard of it. I don't run sys-clk so maybe someone else can chime in with their experiences. I wouldn't expect them to clash though, I don't access much besides the bluetooth service.

Homebrew RELEASE MissionControl: Use controllers from other consoles natively via Bluetooth

Well-Known Member

Well-Known Member

Well-Known Member

Member

Active Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Deleted User

Guest

Well-Known Member

Member

QVID PRO QVO

Well-Known Member

Similar threads

Popular threads in this forum