Yep! Currently they still have an edge since as far as I'm aware they can handle both rumble and motion controls. When I get around to implementing those though, there won't be much reason to own a dongle.
the dongles still are useful for everyone on stock FW but yea with this CFW systems won’t need them at all.
The main thing will be how well this stacks up to using a dongle including latency and supported features.
Can I still use Sys-con and this? I want to use a Wii U Pro Controller via Bluetooth and my wired Xbox 360 controller via USB that I already use with Sys-con, can I use both at the same time? Can you add USB controllers to it?
I'm not 100% sure as I don't use sys-con. Though I've not heard a single person complain of problems with it yet, so I assume it's probably fine. Why don't you try it?
--------------------- MERGED ---------------------------
This is how it's mapped currently. Please make sure you're running the latest firmware on your xbox controller, as the button layouts were changed at some point.
Tried it with a few controllers:
(official) Switch Pro Pad doesn't pair anymore. Still wakes the console and shows "paired" when sync is held, buit doesn't actually do anything but flash the leds like it's still searching
Wiiu Pro Pad works fine, gets recognized as switch pro pad
Dualshock 4 doesn't pair
Reseting paired devices doesn't help.
(official) Switch Pro Pad doesn't pair anymore. Still wakes the console and shows "paired" when sync is held, buit doesn't actually do anything but flash the leds like it's still searching
Wiiu Pro Pad works fine, gets recognized as switch pro pad
Dualshock 4 doesn't pair
Reseting paired devices doesn't help.
Just got hit with an error code 2162-0002 (0x4a2) as I held the + button to search for my DS4 from within the Change grip screen. I'm on the latest Atmosphere booted using fusee-primary.bin if that makes a difference..
Edit: tried to pair it again and got the same crash but I also managed to notice the title id : 010000000000002A which from a quick google search seems to be the btm-sysmodule which im assuming has something to do with bluetooth.
Edit: tried to pair it again and got the same crash but I also managed to notice the title id : 010000000000002A which from a quick google search seems to be the btm-sysmodule which im assuming has something to do with bluetooth.
Last edited by phatweeb,
I'm going to try it out later then, thank you for this, it really is a useful tool, if they don't work having both installed at the same time, would you consider working with the sys-con guy on making them not interfere with each other or something? Thank you regardless
Could you open a github issue detailing the issue and your setup? Please include your system firmware version, atmosphere version, any other homebrew you might be running and whether the controllers are official or 3rd party. Did you reset paired devices via "Disconnect Controllers" in the Controllers and Sensors menu?
Had a couple of other users report similar issues. One said deleting and reinstalling Atmosphere fixed it for him. If you still have issues, please open a github issue and attach the atmosphere fatal error report.
I suspect they can already coexist, but if not, sure.
Will this app work with retroarch with Wii U pro controller without getting disconnected??
What do you mean? Is this some kind of known issue? MissionControl aims to impersonate a Switch Pro controller, so a controller should have more or less the same behaviour
Yep that did it worked like a charm and my DS4 popped up immediately. Your'e doing god's work with this mate now I don't have to buy a pro controller just for my switch!
It is a bit odd tho how it didn't work the first time around. The only Homebrew I had installed was retroarch and sys-clk
Yes, deleting the files should make your console go back to how it was before. Simply reinstalling atmosphere should be enough to disable it though, as it won't run on boot without the custom boot2 provided.
Possible, yes. However it's unlikely to happen anytime soon if at all as it will likely require a full reverse engineering and reimplementation of the bluetooth module. Either way, it's not a feature that I plan to add to MissionControl. This is strictly for hid devices.This is a great HB thank you
Would connecting other bluetooth devices be possible? Bluetooth Headsets for example or is this HB strictly for game controllers only?
Do you have a link to any further info? Try and pair it and then dump your bluetooth database with btdb.nro provided with the release.
Good to hear that fixed the issue for you too. I'm also a bit stumped as to why this might fix it though, assuming everything was up to date prior. Maybe just coincidence
Similar threads
