(Bug) the button orientation in xbox one is wrong, you can add some way to reorder it as in .ini file

When the DS4 battery reach 100% while plugged in the nintendo switch dock with micro-usb cable, atmosphere crashes and it retrurns an Error Code: 2011-0301 (0x25a0b).
Firmware: 10.1.0 (Atmosphère 0.14.1-master-ee5a095c).
Controller: Dualshock 4 - CUH-ZCT2U

I have an Ipega control, model 9062S that was detected and connected to the Change / Grip Order function.
In the Control the LED indicates that it is connected but the "Pro Controller" does not appear on the screen and no button on the control works.

I looked in the app btdb.nro, before 6 devices appeared and after I connected the Ipega control, 7 devices appeared.

I managed to make the connection as I do on Smartphones, holding the Home + (X) button to turn on bluetooth, I tried to turn on bluetooth using other combinations with the Home key to see if it would be identified as well but was not identified.

Below is a photo of the app btdb.nro, if I'm not mistaken the ipega control is the following MAC that appeared (00: 90: e1: e2: 3f: 89 - 1949: 0402)

Hi,
Is there a way to make it work on sxos ?
Thanks,

hi , ive done this but it doesnt do anything , im in atmos 14.1 dont recognize my ps4 controller and my wii controller , help
ive tried to pair with the buttons but doesnt work

I have got a gamestick and a ouya it would be nice to use these controller on the switch I now the gamestick controller is lacking some buttons but couldn't u use a combination of buttons to emulate missing buttons

Hello when i try to pair the first generation DS4, atmosphere instantly crashes (On the pair controller screen)

It works great with the last generation DS4, it's only failing on first generation

Using a DS4. When running classic Doom, the camera spins very fast and cannot move.

Only weird thing I've done is remapped Cross to A and Circle to B in the Nintendo remapper.

Both these controllers have a Switch mode and work in the Switch, the problem is that 8bitdo's drivers for the Switch specifically are trash: it has a bug where the Switch detects the analog as 100% tilted to a direction even tho physically they're tilted around 60%, this results in the analogs being extremely sensitive. Here's a image of the problem and here's how it should be

That's where Xinput comes to the rescue: when using both these controllers on Xinput in a PC, this sensitivity issue doesn't happen, as the Xinput drive was actually written correctly. I have both these controllers here and I can test beta builds and provide information about them if you end up picking the issue up.

Edit: out of curiosity I tried pairing the SN30pro+ to the Switch in Xinput mode and to my surprise it paired fine, the bottom layout is all over the place tho.

Hello, thank you for the great tool, my DS4 v1 was working perfectly until it somehow crashed the switch. It was connected through bluetooth while charging through usb (through wall charger). Suddenly, it crashed the switch and now every time I tried to reconnect the controller through bluetooth it crashed Atmosphere. (maybe this is related to 100% charge issue in another issue #18 (comment)).

It would be great if you can add an unpair button to your app so that we can unpair the controller. Right now, unpair through settings is impossible because it needs the controller connected and x button pressed. Simply connecting the controller will crash the switch.

Thanks!

The steam controller is quite an impressive and comfortable controller, and while it's sadly EOL, IMO it would be a lot more useful (to me at least) if it was supported by a project like this. I'm willing to do the necessary tests, research etc to help implement this, if requested.

The controller only supports a proprietary protocol and requires a dongle by default, but it gains BLE support with a software update that can be installed on a computer: https://support.steampowered.com/kb_article.php?ref=7728-QESJ-4420

The default configuration isn't great (it acts as a keyboard and mouse iirc), but perhaps it would be possible to map it to more useful controls.

I have a generic bluetoh controller. I wanted to know if I can use it through SX OS. I usually use it over USB with the help of Sys-con

Hi there,
I had your mod working, but my Xbox mapping was out so I updated the controller. Ever since there when I tried connecting the controller it would crash my system. I tried removing the controller from the database and added it again with no luck. I’m running the latest version of atmosphere and FW 10.0.4

Thanks for your great work on the device

Hey, I am the developer of the 1Controller Magisk module for Android. That project's aim is to support as many controllers as possible.
However that project only contains keylayout files for the controllers, so no custom drivers.
Still I'll link it here in case it helps you in any way.
https://github.com/Electric1447/1Controller

Since the Elite Controller 2 has native Bluetooth support and the controller is pretty similar to the regular Xbox Controller (don't quote me on that) you could add support for it?

hi i copied thefiles to the root of my sd but atmosphere won load error code 0xffe title id01000000000000 im on latest atmosphere

report_00000000055f7fa3.zip

can implement for sxos?

Once paired with My Ps4 Controller Could not pair anything else. Tried to use my switch pro controller and would sync. could not sync other ps4 controllers, or wii u pro controller after the first one was sync.

Switch 10.1.0 latest Atmosphere booted with fusee.

If you connect a wiimote, it will be interesting to tell the Switch to detect wiimote arrows as left stick or as arrows.
This would be useful in games such as SSBU, which obligate the player to use the left stick to move the character.

I found a old Bluetooth controller that's meant to be for the gem box and it linked up if I do that same as before can we see if we can get that working too cause a good controller

Originally posted by @oxley192 in #42 (comment)

The controller pairs with the console, but the leds keep flashing as if it was trying to connect to the console and they don't stop, i've included a picture of the nro you included but i don't know which one it's the smash controller, sorry

I've seen that you recomend wiping the switch controller database in case the controller was paired via USB, but how can i do that? Thanks in advance

Hello! I've been looking for something like this since my joy-cons have this annoying drift problem..
I tried pairing a dualshock 4 and a wii u pro and none of them worked. I paired them the way it said on the main page and I also did a reboot.

(P.S. I don't know if this helps but I installed this on an older version Atmosphere, Atmosphere later crashed, so I updated it and there was no crashing.)

Hope you can help!

Would you please had support for PS3 controllers

Hello !

It worked well for 2 days and now I'm getting this error whenever I'm trying to pair it again.

DualShock 4 Gen2

What I did so far:

• Reseted controller
• Rebooted
• Deleted all controllers profils (Disconnect Controllers via System Menu)
• Reapply the files on my SD card.

Running Firmware 10.1 on Atmosphere 0.14.1

Just before it crash, I see the Paired message on top left. After reboot, if I just try to open the controller via the PS button, it just crash again.

Looking for help 👍
Good work on this software so far, its amazing

(English isn't my mother tongue so please be nice with me :) )

Controller support for Xiaomi Gamepad would ve aprecciated, awsome work, contrats and thankyou.

Website link: https://xiaomi-mi.com/accessories-for-tv/xiaomi-mi-bluetooth-gamepad/

I have no idea what happened... I installed this as described, copied 'atmosphere' folder to the root of SD, booted and then Official Pro controller cannot be recognized. I tried for 15 minutes straight getting it to connect via USB, syncing, pairing, every option I have ever used in the past, and no matter what, the pro controller would never connect with the switch. It's lights would blink back and forth forever, and that's it. A 'paired' notification would pop up on screen when I connected via USB but no input would ever be recognized.

To test if the pro controller was the problem, I paired it with my vanilla switch and it synced up instantly and was able to be used within 5 seconds.

After deleting the missioncontrol files and re-installing fresh atmosphere, the pro controller worked again instantly, just like the vanilla switch, the normal expected behaviour.

I'm running the latest firmware and atmosphere releases.

Title was pretty explanatory.
I paired and used the controller without issues the first time.
Now, after a wake up of the console, everytime I try to pair crashes my Switch.
Tried disconnecting all controllers from menu, resync, restart.
Nothing worked.
What can I try more?

I tested this with 2 controllers, both had the same stick behavior and the d-pad didnt seem to work

Example
https://youtu.be/2cfhNkggOn0

Would be cool to use since it's pretty much laid out like a pro controller already.

Back button reads as L, start reads as R, right bumper does not work at all, left bumper reads as X, X does not read at all,

Support for the PowerA pro controller would be appreciated

Link to Controller on website: https://www.powera.com/product/enhanced-wireless-controller-for-nintendo-switch-mario-silhouette/

The Controller shows up as Lic Pro Controller in the NRO provided but acts just like a normal pro controller.

Pressing the analog sticks, RB, start and select, the home button or X doesn't send any input to the console.
Pressing LB send the input for the X button instead of left bumper.
(Console is on the latest version of atmosphere)
I tried disabling and enabling the sys-con module, it didn't solve the problem.

I tested both my Wii U Pro controller and my PS4 controller. The former hasn't been tested on another device in a few years so it may be defective. When I hold left on the Wii U Pro controller's left analog stick it registers as holding it right. It's a bit different on the PS4 controller, when I hold it diagonally to the left/top it starts to frizz out. I used the "calibrate control stick" settings to check these.

I know that motion control isn't implemented yet and won't work with an Xbox controller, but when using my Xbox One S controller with the switch it acts as if it is receiving a motion control input causing the aiming of a bow in Zelda to go all over the place, the issue stops as soon as i turn off motion control in the game. The same issue happens in other games as well but all have the same option to turn motion control off so its not a super big problem to me.

hi! thanks for this great app!
I know the controller works on switch, but I'd like to be able to swap dpad <-> LS to be able to play zelda links awakening or other games that could require this.

not sure how feasible this is but this could be useful even to play with the ds4/xbo/wiiu/sw pro dpad instead of the analog stick with some game where analog doesn't add much or anything at all.

Thanks again for you work, keep it up :)

When I try to boot Atmosphere it gives me the following error:

This is the log file:

report_059dbd11.zip

It doesn’t recognize buttons x, rb and when i push both joysticks on my xbox controller

See title. Unlike my wiimotes, the home button on my XBone S controller doesn't do anything. Awesome project btw :)

Atmosphere 0.14.1
Hekate 5.3.2
Switch firmware 10.1.0

Tried it with a few controllers, all of them 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 (Am I supposed to just hold the ps button?) - Pairs fine with a magicns

Tried Disconnect Controllers under the Controllers and Sensors menu, without success

Is there a way to make a patch to work on sxos because it is very good and I could not make it work on sxos maybe with some patches if I can achieve this

I can't seem to pair my DS4 Controllers. Just got a fresh copy of AMS 0.14.1 and also copied MissionControl. I tried pairing a DS4 V1 and DS4 V2 but no luck. After holding down Share + PS4 btn the controller starts flashing fast but nothing ever happens in the Change Grip screen.

Just to confirm: btdb only shows my two joy-cons.

Firmware is v10.1.0

The mapping of the xbox one controller is all messed

After following the install instructions, the console will not boot into switch os.

`Panic occurred while running Atmosphere.

Title ID: 0100000000000008
Error Desc: sdt::abort() (0xFFE)`

So, after I installed this build of MissionControl on my switch, the Nintendo Switch Pro controllers (knockoffs I bought from ebay) that I had weren't connecting to my switch. I have attached a copy of my addresses at the end. Both the pro controllers are Xenoblade chronicles edition, if that matters.

Help me support these controllers back on my switch.

The game freezed when the PS4 controler ran out of battery, happend twice, once in retroarch and once in carrion

like when I open ur NRO I can select my controller I.E: the joy cons or pro controller and be able to remap the right stick axis and have the ability to invert them and be able to switch back to normal controls later when I am done

After getting the Wii U Pro controller working my Switch Pro controller won't pair wirelessly. It does the small vibrate to indicate pairing and the switch pairing notification pops up but nothing happens after that

Hello@all.

Would it be possible to add support for the Moga XP5-X Plus?
https://www.xbox.com/de-DE/accessories/mobile-gaming/moga-xp5-x

I have been using sxos for a long time and it's my first time using any sys-module, but I have tested this on my original switch and I can confirm that as of August 29, it will not work on Sxos. I have tried other sys-modules from other sources (and tested it) and this is one does not work when trying to connect my Wii Remote. I think it might be my configuration that I need to fix, but I am looking foward to this in the future seeing that this might have potential. (I also erased all sys-modules before testing to make sure)

report_0000000005548e62.zip

Fatal crash on boot after installing the files, not sure what to do to even make it boot again. Will try reinstalling atmosphere. Very frustrating.