RELEASE MissionControl: Use controllers from other consoles natively via Bluetooth

Just installed the latest Retroarch on my switch (HOS 11.0.1, AMS 0.17.0, MC 0.4.1) and can confirm my DS4 works without issue. It must be some problem with your setup.

 

Not quite sure exactly what you mean there. Are you asking about a means to return to the retroarch menu from within retroarch? A global shortcut to bring up retroarch?
While it might be possible to monitor button presses from MissionControl to perform certain actions like launching an applet, I think this kind of thing is a bit out of scope for the project.

 

I don't see why it should be any different for any other controller, assuming it has something mapped to + and -. I just launched retroarch now and tried it with my xbox controller. Pressing the view and menu buttons together brings up the quick menu, which I assume is what you're talking about.

 

Full joycons meaning left/right pairs (16 joycons in total)? If so, then no. The switch only supports a total of 8 controllers connected simultaneously, regardless of whether the joycons are linked together as a single controller or not.

 

Yep, latest version works with 0.18.0

 

Please stop asking about this. I have already explained the situation, and I am not investing any time into it. If anything changes you will hear about it. DS3 support will likely come via USB long before Bluetooth (if at all).

Sure, no problem! I already have support for some Razer controllers, so it's quite possible whitelisting the hardware ID of the controller is all that's needed. Your description of the issue does sound a little odd though. I would not expect the controller to appear as a Pro Controller in the database shown by btdb, since it has not been designed for Switch at all. Are you sure you weren't mistaking an entry from an actual Pro Controller for this one? If the controller successfully pairs but isn't matched against a whitelisted entry, it should appear in the controller applet as a pro controller with red buttons. You should also be able to see the data it sends in HID Report Viewer. If you are not seeing this it sounds like the controller isn't completing the pairing. The manual seems to suggest there are multiple Bluetooth modes. Have you messed around with these?

I don't have any official format for controller requests (I should really get around to creating a template on github one of these days...) Just go ahead and open an issue. The fact that you're even asking about it here shows you're already giving it more thought than most

The most important thing I need is a hardware ID (vid/pid) for whitelisting the controller. A screenshot of the btdb output is enough. If the controller doesn't use a known report format then I'll also need a transcription of the packets seen via HID Report Viewer. Additional info such as whether the controller has support for rumble or motion controls, player leds etc can also be useful, though not required for adding basic support. You could also include information about any special button combo or mode you had to use to get the controller to pair for the sake of other users with the same controller.

Let's continue this exchange on github.

 

I've had it working for major console controllers for some months now. Other controllers will depend on whether people can provide me with information about their output report format. There is definitely some room for improvement, which is why I haven't released anything yet. I know it's a highly anticipated feature, but with the core of it out of the way it's just not a very interesting problem to work on from a dev point of view. I recently implemented reading settings from a config ini though, so I may release something soon now that users who aren't happy with the current state can just disable it.