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

[ndeadly]

No, it's a not a drifting issue, just normal game behavior I'd say. You are constantly recentering it since it uses the camera movement to do so. I guess it is not a good example for the poor Wii Remote Plus. I have to try Captain Toad.

I just watched your video properly and that certainly doesn't look normal for the wiimote when the others work so well (Unless you were having to hit R3 a lot with the other controllers and I just couldn't see in the video?). I wouldn't expect you to have to rotate the controller to such wild positions so quickly just to center your view.

Firstly, don't know if you're aware that you don't need to go through the controller menu every time you want to connect a controller (maybe you just did this for the sake of your youtube viewers?). Once paired you can just wake them up with a button press and they will reconnect by themselves at any time.

I saw you had some trouble with initialising the MotionPlus at first. As i mentioned in the above comments with @Takokeshi , the initialisation can be a little finicky and doesn't currently work every time. I didn't want to hold up the release trying to make it perfect. I think by trying to support any possible combination of MotionPlus and extensions we're trying to use the controller differently to how it was intended to be used with Wii games. Anyway, you did the right thing by just reconnecting it. You may have also been able to get away with simply pulling the nunchuck and reconnecting that to trigger a status update.

As for the the motion controls, it looks to me like either the MotonPlus still hasn't been initialised correctly and you are possibly only getting accelerometer data, or there is something off with the calibration. Maybe this game is configuring the motion controls in a way that I don't currently handle. If you're interested in doing some testing to try and improve things, feel free to reach out to me on discord @ ndeadly#5317

 

[Deleted member 323844]

I just watched your video properly and that certainly doesn't look normal for the wiimote when the others work so well (Unless you were having to hit R3 a lot with the other controllers and I just couldn't see in the video?). I wouldn't expect you to have to rotate the controller to such wild positions so quickly just to center your view.

Firstly, don't know if you're aware that you don't need to go through the controller menu every time you want to connect a controller (maybe you just did this for the sake of your youtube viewers?). Once paired you can just wake them up with a button press and they will reconnect by themselves at any time.

I saw you had some trouble with initialising the MotionPlus at first. As i mentioned in the above comments with @Takokeshi , the initialisation can be a little finicky and doesn't currently work every time. I didn't want to hold up the release trying to make it perfect. I think by trying to support any possible combination of MotionPlus and extensions we're trying to use the controller differently to how it was intended to be used with Wii games. Anyway, you did the right thing by just reconnecting it. You may have also been able to get away with simply pulling the nunchuck and reconnecting that to trigger a status update.

As for the the motion controls, it looks to me like either the MotonPlus still hasn't been initialised correctly and you are possibly only getting accelerometer data, or there is something off with the calibration. Maybe this game is configuring the motion controls in a way that I don't currently handle. If you're interested in doing some testing to try and improve things, feel free to reach out to me on discord @ ndeadly#5317

I didn't push R3 even once, gyros reset when you move the camera, so the reference point is not a problem. Maybe Wii Remote Plus sensitivity is a bit high, but I don't think it would matter with lower sensitivity.

Yes, I woke them with the home button on Sony devices, but sometimes Wii Remote syncs as a Wiimote instead of a Pro Controller, that's why I always sync it. You can see that in the video. The first time I sync it, it is configured sideways and gyro doesn't work. The second time it gets synced properly. Edit: As you say in the third paragraph xD

I will join the Discord later. Than you ndeadly

 

[ndeadly]

I didn't push R3 even once, gyros reset when you move the camera, so the reference point is not a problem. Maybe Wii Remote Plus sensitivity is a bit high, but I don't think it would matter with lower sensitivity.

Yes, I woke them with the home button on Sony devices, but sometimes Wii Remote syncs as a Wiimote instead of a Pro Controller, that's why I always sync it. You can see that in the video. The first time I sync it, it is configured sideways and gyro doesn't work. The second time it gets synced properly. Edit: As you say in the third paragraph xD

I will join the Discord later. Than you ndeadly

Oh, so the issue is more that you don't have the right stick at all to control the camera? That might be trickier to solve.

 

[Deleted member 323844]

Oh, so the issue is more that you don't have the right stick at all to control the camera? That might be trickier to solve.

That's certainly the main issue, but I don't know if gyro sensitivity can be improved. It lost it's position very quick, as you can see the first time I use it. If you do the same gestures with the DS4/DS they hold the position for longer time without resetting it. If the Wii Remote can behave the same as those, I think that remapping one of the directions of the right analog to another button (d-pad, for example) would be enough to play decently.

I have only tried with Quake. I'm not sure if that would be an issue for non-FPS games with gyro gestures.

 

[LiborNX]

Hi, I'm new to this tool so might be missing the obvious.

- Controllers > Change Grip/Order - it shows 4 empty controller slots
- DS4 controller: hold PS + Share
- A few seconds later "Paired" pops up on the screen

...Then what? I mean I am still on the Change Grip/Order screen at this point and I still see the 4 empty controller slots. It says "press L + R on the controller"; I tried but it does nothing. I am basically stuck on that screen although the "Paired" pop-up was very promising.

Any idea how to take it from here?

Thanks

 

[Deleted member 323844]

Hi, I'm new to this tool so might be missing the obvious.

- Controllers > Change Grip/Order - it shows 4 empty controller slots
- DS4 controller: hold PS + Share
- A few seconds later "Paired" pops up on the screen

Try the reset button, near the left trigger, in the gamepad. That's the procedure, no other steps required.

 

[franklinyyz]

I am very excited to pair my DualSense using Mission Control.
That said, I would love to be able to not having to re-pair every time I'm switching between the Switch and the PS5.
Based on what I read, the [bluetooth] setting would allow me to not having to re-pair. However, that's where I need help explaining to me how I should configure the host_name and host_address. Is it a matter of me inputting the host name and address of the PS5 in here? If so, how do I do that? If not, please educate me!

 

[LiborNX]

Try the reset button, near the left trigger, in the gamepad. That's the procedure, no other steps required.

Thanks Stranno. That helped. For the record DS4 hard reset wasn't enough (it did change something... After hard resetting, pairing would trigger a fatal error program ID 010000000000bd00 which forced me to reboot to stock). I had to:

- Properly remove MissionControl (steps here: https://github.com/ndeadly/MissionControl/#removal)
- Reinstall (https://github.com/ndeadly/MissionControl/releases/latest)
- Hard reset the Dualshock 4 controller
- Then it was OK to pair

Thanks!

 

[ndeadly]

I am very excited to pair my DualSense using Mission Control.
That said, I would love to be able to not having to re-pair every time I'm switching between the Switch and the PS5.
Based on what I read, the [bluetooth] setting would allow me to not having to re-pair. However, that's where I need help explaining to me how I should configure the host_name and host_address. Is it a matter of me inputting the host name and address of the PS5 in here? If so, how do I do that? If not, please educate me!

That's the basic idea, but it's a bit more complicated than that. When you pair a controller with another device, the two devices negotiate a link key and store that alongside each others bluetooth mac address. Most controllers will only store the key and address of the most recent device they were paired to, so anything you want to pair with needs to advertise with that address and know the key. To make this work you would need to find the bluetooth address of your host, and spoof that on the switch using the missioncontrol.ini setting. The second and more complicated thing you need to do is extract the link key used in the connection and inject that into the entry for that controller in the Switch's bluetooth pairing database. How to do this is largely dependent on the device you want to pair with. A linux PC for example would be relatively simple to extract the key for the file that stores the bluetooth pairings. For something like the PS5, you would either need to console to be hacked in order to access this info from within the filesystem, or you would need to be able to request this info from the controller directly. I know on Switch you can read the pairing information directly from controller memory via a bluetooth command. I'm not sure if this is possible for Sony controllers. In the event that you could obtain the key, you would then need to write that into the pairing database on the Switch. I currently don't provide a mechanism for the end user to do this, so you would need a simple homebrew program with the ability to write the save file for you.

If you can do all of that, then you should have a pairing that works simultaneously between both devices. It's definitely more of a power user feature, but the option is there if you are capable enough.

Thanks Stranno. That helped. For the record DS4 hard reset wasn't enough (it did change something... After hard resetting, pairing would trigger a fatal error program ID 010000000000bd00 which forced me to reboot to stock). I had to:

- Properly remove MissionControl (steps here: https://github.com/ndeadly/MissionControl/#removal)
- Reinstall (https://github.com/ndeadly/MissionControl/releases/latest)
- Hard reset the Dualshock 4 controller
- Then it was OK to pair

Thanks!

Sounds to me like something was messed up with your initial install. If you don't mind, I'd be interested in seeing the error report that that fatal error generated.

 

[Allen-R]

https://github.com/ndeadly/MissionControl/releases/tag/v0.7.0

FINALLY MOTION CONTROLS!!!!
LET'S FUCKING GOOOOOOOOOOOOOOO!!!!!!!!!!!!!!!

 

[franklinyyz]

That's the basic idea, but it's a bit more complicated than that. When you pair a controller with another device, the two devices negotiate a link key and store that alongside each others bluetooth mac address. Most controllers will only store the key and address of the most recent device they were paired to, so anything you want to pair with needs to advertise with that address and know the key. To make this work you would need to find the bluetooth address of your host, and spoof that on the switch using the missioncontrol.ini setting. The second and more complicated thing you need to do is extract the link key used in the connection and inject that into the entry for that controller in the Switch's bluetooth pairing database. How to do this is largely dependent on the device you want to pair with. A linux PC for example would be relatively simple to extract the key for the file that stores the bluetooth pairings. For something like the PS5, you would either need to console to be hacked in order to access this info from within the filesystem, or you would need to be able to request this info from the controller directly. I know on Switch you can read the pairing information directly from controller memory via a bluetooth command. I'm not sure if this is possible for Sony controllers. In the event that you could obtain the key, you would then need to write that into the pairing database on the Switch. I currently don't provide a mechanism for the end user to do this, so you would need a simple homebrew program with the ability to write the save file for you.

If you can do all of that, then you should have a pairing that works simultaneously between both devices. It's definitely more of a power user feature, but the option is there if you are capable enough.

Thanks for the detailed explanation! Since I am not a power user, I'll just put up with re-pairing.
Looking forward to the day BLE being supported, then I can use the series X controller and using the native remapping function to remap the X Y A B buttons. Using the Dualsense means I have to memorize the button mentally, and my brain capacity is limited. HA

 

[franklinyyz]

Has this ever happened to anyone since updating to 0.7?
Prior to 0.7, I've only added the Wii U Pro controller and there was never an issue. With 0.7.0, I added the Dualsense controller. Now when I am in handheld mode, several games would not detect that I am in handheld mode, prompting me to take out the joycons and play in tabletop mode.
Weird huh?

 

[Deleted member 323844]

I have been talking to ndeadly and the Wii Remote Plus behavior seen in my video can be vastly improved synchronizing the gamepad from an stable place. Now it behaves pretty much the same as the Dual Shock 4 or DualSense. The game also features a very weird HD vibration pattern, which does not translate very well into the good old ERM vibration of the Wii Remote.

 

[FanNintendo]

anyone tried with Wiimote on The House of the Dead Remake??

Never Mind I tried with wiimote as lighgun dam it not working but it work as controller and I read that The House of the Dead Remake dont support Lightgun like I say WTF? Hope to see The House of the Dead Remake update support with one of joycon as Lightgun

 

[LiborNX]

I know on Switch you can read the pairing information directly from controller memory via a bluetooth command.

Interesting... You can read that only from a hacked switch, right? Reason I'm asking: I've been trying to simultaneously pair a Swtich controller pro with a hacked Switch and a non-hacked one.

 

[ndeadly]

Interesting... You can read that only from a hacked switch, right? Reason I'm asking: I've been trying to simultaneously pair a Swtich controller pro with a hacked Switch and a non-hacked one.

To do it from the console you would need a hacked switch, yeah. In that case it's easiest just to dump the pairing database. But you can also read directly from the controller, so it's possible to do it from a PC too. Joycon Toolkit is capable of dumping the entire controller memory and you could read it out of that. Refer here for info on the contents of the flash memory. You're interested in the host bluetooth address and the long-term key.

In this scenario I would pair the controller on the hacked switch to create an entry for it in the database, then pair with the non-hacked Switch, dump the controller memory on PC, and then inject the host address and key into the database of the hacked one. This should work fine, but I'm not sure what kind of weirdness you might see if you try to wake the console from the controller when within range of both, for example.

 

[LiborNX]

To do it from the console you would need a hacked switch, yeah. In that case it's easiest just to dump the pairing database. But you can also read directly from the controller, so it's possible to do it from a PC too. Joycon Toolkit is capable of dumping the entire controller memory and you could read it out of that. Refer here for info on the contents of the flash memory. You're interested in the host bluetooth address and the long-term key.

In this scenario I would pair the controller on the hacked switch to create an entry for it in the database, then pair with the non-hacked Switch, dump the controller memory on PC, and then inject the host address and key into the database of the hacked one. This should work fine, but I'm not sure what kind of weirdness you might see if you try to wake the console from the controller when within range of both, for example.

Will try, thanks! And yeah, I will make sure to avoid having both within range!

 

[buchu300]

Hey there! I have a small problem with pairing my dualsense pad with missioncontrol.
I bought the pad yesterday, connected it to the switch with no problems. Today, trying to connect again - after entering "Change Grip/Order" and pressing the playstation button, the message Paired was displayed, but the pad was not detected, nor could I control it.
I've removed and reinstalled MissionControl, reset the pad, and nothing.

What else can I do?

AMS 1.3.0

Thanks for the work you put into this

//edit: I updated the pad software (you can now do it on PC instead of connecting to PS5!) and everything works as it should great job thanks again!

 

[ndeadly]

Hey there! I have a small problem with pairing my dualsense pad with missioncontrol.
I bought the pad yesterday, connected it to the switch with no problems. Today, trying to connect again - after entering "Change Grip/Order" and pressing the playstation button, the message Paired was displayed, but the pad was not detected, nor could I control it.
I've removed and reinstalled MissionControl, reset the pad, and nothing.

What else can I do?

AMS 1.3.0

Thanks for the work you put into this

//edit: I updated the pad software (you can now do it on PC instead of connecting to PS5!) and everything works as it should great job thanks again!

Haven't heard of the controller firmware causing problems before. Your problem sounds similar to what people have been reporting for DS4 controllers when the battery is almost dead. Could it be that you connected the controller via cable to PC for the update which allowed it to charge a little?

 

[franklinyyz]

Any recommendations of wireless fighter/rocker/arcade sticks that work with Mission Control?