I have it working for all major console controllers in some form, it's just not great. Some work is needed to figure out how to effectively map HD rumble to each controller type so that it resembles what was intended by the game devs. Not yet sure how to go about adding it for generic controllers as there is little to no information available for most of them, and I don't own any for testing.
Nope. I can tell you it's probably my lowest priority right now. I'm fairly convinced it can't be done without considerable effort, if it's possible at all within the constraints of HOS. There are so many other things to work on right now with a much better risk/reward ratio.
The main thing people could help with would be figuring out how to send rumble commands to controllers I don't have access to. I'm just not sure the best way to go about this. Finding the HID report descriptors might be a good start.
Not possible currently, but will be added in a future update.
It's certainly doable, the main problem is that as far as I can tell most modern Bluetooth keyboards use Bluetooth LE and I don't currently know how to make LE connections. The latest release of MissionControl already has the keyboard device type whitelisted though, so if you were to come across a keyboard that uses legacy Bluetooth it should connect like any other controller. It would just need to have the keys mapped.
Thanks, had to find the info on what BT standard the keyboard supports. To pair it is same process as a controller? After pairing do I see a keyboard or a controller on the screen? How do I go about mapping the keys?
Yeah, you would just go through the Change Grip/Order screen as usual. If it connected successfully it would appear as a Switch Pro Controller with red buttons, indicating there is no handler found to map the controls. I don't think the switch itself has any concept of a Bluetooth keyboard.
Mapping the keys would require me to define a new handler in the code based on observing the packets sent by the device. Normally information about the reporting format would be sent in an HID descriptor, but this isn't exposed by Nintendo's Bluetooth service since they don't need to accept arbitrary devices. Unfortunately this means that each unique device likely needs to be mapped manually like this.
I have firmware 10.0.1 and AMS 0.14.2 and my Switch crashes on boot. I had too remove the sd and put it in my pc to delete the files to get it to work properly. Any ideas why this happens? Should I also be on the latest oficial FW?
Could be any number of things... outdated MissionControl version, corrupted AMS install, too many sysmodules running etc. Can't really comment further without seeing a crash report.
In most cases a fresh install of Atmosphere followed by a fresh install of MissionControl usually resolves this kind of issue. You can use whichever firmware version you like.
How is working 8bitido adapter to support rumble? I have it and work great with xbox one controller with no issues.
Is not possible use the same metod in Mission Control?
Regards.
No idea, all the USB adapters are closed source. I have the rumble working, I just have to spend the time to make it feel decent for each controller. Been working on other things.
Thank you
I have a ko-fi donation link and a bitcoin address on the main project page. You can also DM me for my paypal
Similar threads
