I tried this and it doesnt work. Also tried pressing the reset button on the controller and holding the home.and share buttons
I tried this and it doesnt work. Also tried pressing the reset button on the controller and holding the home.and share buttons
That's what I figured. The more important would it be to have a companion homebrew app to create new controller profiles.
To launch and use the app we use a controller already recognized (or just the Joy-Cons).
The app itself just goes through all the buttons and let us map them with a 5 second time window each resulting in a key to be unassigned if we don't press it within the 5 seconds (this way we could use SNES gamepads for example that don't have analog sticks and ZL+ZR).
I have a 8bitdo sega genesis controller, but it's 2.4ghz. I know it wont connect to this directly (because it isnt bluetooth), but would it work if I connected a genesis USB adapter to the Switch with the 2.4ghz dongle that comes with the controller if I used this?
edit: ah, nevermind, its bluetooth-only right now.. I wonder if sys-con would work then..
edit: ah, nevermind, its bluetooth-only right now.. I wonder if sys-con would work then..
Yeah it might work with syscon, I don't know if it needs to have it's hardware ID registered or anything first though.
Eventually I'll look into intercepting USB comms with MissionControl after I've implemented all the other features I intend for Bluetooth.
Honestly speaking I think the DS3 will be supported via USB well before any possibility of Bluetooth support. It's literally my lowest priority right now due to the large amount of work involved to even see whether it might be possible without breaking anything else.
Could you add something like a "priority list" to your planned feature list in your opening post?
So people know where to look for answers and won't question the same things over and over again like myself. xD
Are you planning to add xbox series controller support?
also thanks for all your effort and replies, it's really appreciated
Last edited by B-alpha,
@ndeadly
First of all, thank you for the effort. It's great and I use it with PS4 controllers. Works like a charm!
I commented back on your first release, that I had a knockoff WiiU Pro controller, that I wanted to use, but it wouldn't sync.
It still doesn't. It works flawlessly on WiiU of course, so it isn't broken.
You told me back then to get some more info on the controller, ID and so on. Could you elaborate on how to obtain this information and I'll get it.
Thanks!!
First of all, thank you for the effort. It's great and I use it with PS4 controllers. Works like a charm!
I commented back on your first release, that I had a knockoff WiiU Pro controller, that I wanted to use, but it wouldn't sync.
It still doesn't. It works flawlessly on WiiU of course, so it isn't broken.
You told me back then to get some more info on the controller, ID and so on. Could you elaborate on how to obtain this information and I'll get it.
Thanks!!
The Wii U equivalent to MissionControl is https://gbatemp.net/threads/hid-to-vpad.424127/ and there we had a companion homebrew app, where we could connect any controller, press each button and it would give us a value (I think it was a bit code or something like that). With that information we were able to create a "controller_xy.ini" on our PC, assign all noted values to the actual buttons, place the .ini on the SD card in a directory and the controller was recognized by HID to VPAD.
Could you think of something like that @ndeadly or is that not possible since Bluetooth controllers won't even be recognized by the Switch at all before you implement their unique hardware ID(?) or something like that?
Could you think of something like that @ndeadly or is that not possible since Bluetooth controllers won't even be recognized by the Switch at all before you implement their unique hardware ID(?) or something like that?
I consider the project readme on github to be the primary source of up to date information/documentation for the project. I've recently updated it to expand upon the planned features and rough priorities here.
Yes, see this github issue. The reason support hasn't been added already is that it's using Bluetooth LE, which I currently haven't figured out. I'm in the process of looking into it.
Since then I've had several users ask for support of knockoff WiiU controllers, and so far none have been able to even be discovered by the console. I think they're probably all using some incompatible Bluetooth chipset. I wouldn't be surprised if yours is the same. Are you able to connect it to a PC or phone?
This is essentially what I do already for users asking for controller support on github, I just haven't got around to packaging it all up into a nice app that I distribute with MissionControl yet.
I have considered the .ini file approach in the past, but it adds additional layers of complexity that I'm not sure I want to deal with. Such a format allows you to describe a straight report layout, but some controllers require additional logic to be applied, especially with outgoing reports. I can map a new controller fast enough that I'm not sure that it's worth the overhead. I've said before that doing it in code allows me to maximise speed and keep memory usage low. If someone doesn't like my hardcoded mappings they can use the button remapping on 10.0.0+
Last edited by ndeadly,
Hi, I'm not too up to speed with controllers and specs and was wondering if you could help. I want to get this for my son so he can use it on my One and the Switch. Should it work using this homebrew? Thanks.
Xbox Wireless Controller - Robot White
https://www.ebgames.co.nz/product/xbox-one/267807-xbox-wireless-controller-robot-white
Xbox Wireless Controller - Robot White
https://www.ebgames.co.nz/product/xbox-one/267807-xbox-wireless-controller-robot-white
I hope to be able to support the Xbox series X/S controller in the future, but currently it won't work due to lack of Bluetooth LE support in MissionControl. It's something I'm working on but can't give any ETA on when it might be done. A regular Xbox One controller will work though (maybe this is what you intended since you mentioned Xbox One, the controllers look very similar).
Ok, no worries. Cheers mate, thanks for the confirmation. Yeah I have a One controller and that works awesome. Thing is they're all out of stock in NZ and this new one is a direct replacement as it works on both of the Xbox's apparently.
Last edited by phonemonkey,
Hey man, sorry to hassle you, but would this one be ok? Cheers.
https://www.ebgames.co.nz/product/xbox-one/225592-xbox-one-s-controller-grey-green
Yeah, it's a bit strange to me that they made the two controllers otherwise compatible with either console but switched to Bluetooth LE for everything else. I guess they've prioritised battery life over performance.
No problems. Yep, that one should be fine. Just keep in mind you may need to update the controller firmware before the buttons will map correctly on the Switch.
Just a heads up to anyone who might have already downloaded 0.4.0. There was a copy/paste error that broke handling of dualshock4 analog sticks. I made a shadow release since I didn't think it warranted a new version. If you're affected by this bug simply redownload the 0.4.0 release from github and all should be good.
Similar threads
-
-
@
Psionic Roshambo:
Ken I have that sort of set up on Drastic on Pi for games that don't require touch -
-
-
@ HiradeGirl:
Any TV with your PC connected with Citra and any smartphone to use as a screen using a free play store app.+1 -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
