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

[swabbo]

Seeing how I just got an Xbox Sex controller, this thread is highly interesting to me.

A WHAT?!? lmao

 

[RealYoti]

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

DS3 support wen?)

 

[ndeadly]

DS3 support wen?)

Via Bluetooth? Not for a long time, if ever. Other platforms that support DS3 controllers require modifications to the Bluetooth driver or separate drivers altogether to support the DS3's non-standards-compliant ways. Without the ability to compile our own Bluetooth driver, we just don't have that level of flexibility with the switch. Even if it could be done via binary patching or similar, I think the effort to reward ratio is just too high to make it worth my time.

Eventually, when mission control supports USB, you can expect the DS3 to be supported that way

 

[shiraho]

Via Bluetooth? Not for a long time, if ever. Other platforms that support DS3 controllers require modifications to the Bluetooth driver or separate drivers altogether to support the DS3's non-standards-compliant ways. Without the ability to compile our own Bluetooth driver, we just don't have that level of flexibility with the switch. Even if it could be done via binary patching or similar, I think the effort to reward ratio is just too high to make it worth my time.

Eventually, when mission control supports USB, you can expect the DS3 to be supported that way

Any chance you could add macro support to it? :d

 

[ndeadly]

Any chance you could add macro support to it? :d

Maybe, but it's low priority. Mission control is actually pretty simple in design and essentially just intercepts real packets, and translates them to the switch packet format and passes them on. The problem with adding macro support on-console (especially when we're not the driver) is that you've got real inputs coming in from physical controllers at the same time you're trying to generate an uninterrupted sequence of artificial inputs. To add this kind of thing would require separate threads, timers, locks, extra buffers etc. greatly increasing the complexity of the input processing and opening the door for synchronisation issues and instability. Then there's also the need to provide some sort of framework for actually specifying macros. It's not impossible, but it's a non-trivial amount of work to do it right for something I personally don't have much interest in. I won't be considering it until the rest of my roadmap has been cleared at least. If someone else were to prove it could be implemented cleanly within the constraints mission control is under I would consider accepting a PR though.

 

[silvershadow]

hey @ndeadly thank you for this awesome sysmodule!

Is there anything we can do to help you with getting motions controls to work? i was doing a bit of testing with one of my devices (Titan Two) and i notice that it does interpret every single motion input (wired and wireless), so i don't know if there is some data I (or any of us) can extract to help you towards getting it working?

Or is it just waiting on you to move it up the priority list to start working on it?

Thank you again!

 

[ndeadly]

hey @ndeadly thank you for this awesome sysmodule!

Is there anything we can do to help you with getting motions controls to work? i was doing a bit of testing with one of my devices (Titan Two) and i notice that it does interpret every single motion input (wired and wireless), so i don't know if there is some data I (or any of us) can extract to help you towards getting it working?

Or is it just waiting on you to move it up the priority list to start working on it?

Thank you again!

Adding basic motion control support itself is pretty trivial, the calibration is the part that needs work in order to make it usable. We need to be able to read the calibration data from each of the different controllers and convert it to something that resembles the format used by the switch. I started working on this a while ago but got a bit hung up on trying to relate the reverse engineering notes of the switch format to the info found in data sheets and how to convert between various units, coordinate systems etc. and haven't really had time to revisit it.

If someone were interested in trying to figure this stuff before I get back to it, I don't see the actual implementation in code being anything too crazy (except for maybe the wii motionplus. That thing has a whacky protocol for actually sending the data). It's more about getting the maths right.

Or is it just waiting on you to move it up the priority list to start working on it?

It's more this than anything though. I've been preoccupied until recently with fixing the controller pairing that 12.0.0 broke.

 

[fatmeegz]

@ndeadly Have you fixed the connecting issue with Wii U Pro Controller on firmware 12.1.0 yet?

 

[Aheago]

@ndeadly Have you fixed the connecting issue with Wii U Pro Controller on firmware 12.1.0 yet?

Did you even read the patch notes...

 

[fatmeegz]

@Aheago Nope.

--------------------- MERGED ---------------------------

@ndeadly Just read the latest release notes. Thank you so much! Man, ive been waiting for this since 12.0.0. Keep up the great work mate...!

 

[Asia81]

I wonder if we can play Skyward Sword HD with the original wiimote motion plus and a nunchuck, is it even possible?

 

[ndeadly]

I wonder if we can play Skyward Sword HD with the original wiimote motion plus and a nunchuck, is it even possible?

Motion controls are not currently supported, but even if they were I don't know if it would be possible as the console would be expecting to see two different bluetooth devices for left and right joycon and I'm not sure how easily we could fake that.

 

[Clapmastr]

I would still love rumble for PS and Xbox controllers. Great job on this project. Works well.

 

[ndeadly]

I would still love rumble for PS and Xbox controllers. Great job on this project. Works well.

Rumble is supported for both of these controller types on the latest version

 

[ian0]

works flawlessly on a DS4 controller thank you very much ndeadly,
a dimming or turn off DS4 light bar feature would be godly if possible
thank you very much again ndeadly

 

[r5xscn]

works flawlessly on a DS4 controller thank you very much ndeadly,
a dimming or turn off DS4 light bar feature would be godly if possible
thank you very much again ndeadly

Try the newest version. https://github.com/ndeadly/MissionControl/releases/tag/v0.5.0

• Added a configuration option to disable the LED lightbar on Sony Dualshock4 and Dualsense controllers.

 

[ian0]

couldnt make it work
1 opened missioncontrol.ini.template with txt
2 set true to both lines under [misc]
light is still on help

 

[ndeadly]

couldnt make it work
1 opened missioncontrol.ini.template with txt
2 set true to both lines under [misc]
light is still on help

You need to copy the template as missioncontrol.ini and a reboot is required for it to take effect. Did you do this?

Also make sure you've uncommented those lines you modified by removing the ; at the start

 

[ian0]

uncommented those modified lines by removing the ; at the start

worked
its godly godsent thanks

 

[tabnk]

It will nice to add native USB support.