[Bug Report]: Controller immediately disconnects.

[Bungwr]

Switch Firmware Version

11.0.1

Atmosphère Version

1.3.2 (Latest)

Mission Control Version

0.7.0 (Latest)

Boot Method

Unsure

Issue Description

Using a dualsense controller when in pair mode it kinda almost pairs but then disconnects. On switch side nothing happens.

Error Report

No response

Additional Context

Tried 2 dualsenses and checked on other systems and they're working perfectly. I'm not sure if my frimware is the issue but maybe is. Reinstalled Mission control plenty of times. Deleted Controller folder on config. Done just about anything and I really don't know what the issue is still twt. Any help appreciated tysm<3

[Bungwr]

Just tried dualshock4 and same issue.

[ndeadly]

Try charging your controllers. I have had several similar reports lately and in most cases the issue has turned out to be low battery.

[Bungwr]

I don't think the battery is the issue. I tried 3 controllers. Tried charging them but it's the same issue. Do I need to update my firmware perhaps?

[ndeadly]

It's worth a try. I always test my releases on the most recent firmware at the time. Although all firmwares should be supported, the further back you go the less thoroughly tested things are going to be for the current release. You're always better off keeping your firmware up to date anyway.

[reichembach]

Same thing happening to me when connecting a Dualshock 4. After syncing, it shows as paired but immediately disconnects. Happens both docked and undocked on latest firmware/atmosphère/mission control. Booting through hekate>fusee.bin if it matters

[ndeadly]

@reichembach and you've tried charging the controller?

[Bungwr]

@reichembach and you've tried charging the controller?

I don't think it's a battery issue.. (at least for my side) Temporary fix is using a older version of mission-control and seems fine now.

[ndeadly]

@reichembach and you've tried charging the controller?

I don't think it's a battery issue.. (at least for my side) Temporary fix is using a older version of mission-control and seems fine now.

Yeah I believe you, but many people with similar issues have just needed to charge the battery. Which version did you downgrade to? Maybe it gives some clues as to what changed

[Bungwr]

Yeah I believe you, but many people with similar issues have just needed to charge the battery. Which version did you downgrade to? Maybe it gives some clues as to what changed

I think it might be 0.4.1 or 0.6.2 I'm not really sure... Is there a way I could check?

[ndeadly]

There's no easy way to check at the moment, but your atmosphere version might hint and which version you have based on what can work with it.

[Bungwr]

Yea but I think I even downgraded atmosphere to make sure it works. It might be 0.6.2 as I'm on atmosphere 1.2.5 but I'll try and compare files sizes which may seem the only possible way to find out.

[estgold]

Same issue, same version, before updating Atmosphere, works fine. I will try update Switch firmware or downgrade mission controll version

upd.

Kefir 646, manualy install Mission Control 0.6.4 from releases. Disconnection fixed

[reichembach]

Tried 0.6.4 but it crashes atmosphère, probably cause that mission control version doesn't support latest firmware. Based on the previous comment though, that the controllers don't disconnect on 0.6.4, maybe it has something to do with the newly added motion support for those controllers?

[ndeadly]

Tried 0.6.4 but it crashes atmosphère, probably cause that mission control version doesn't support latest firmware.

Yes, you would need to downgrade Atmosphere to a lower version in order to use that version.

Based on the previous comment though, that the controllers don't disconnect on 0.6.4, maybe it has something to do with the newly added motion support for those controllers?

This may be in part, because controllers weren't actually instructed to disconnect prior to 0.7.0. I made this change because the previous behaviour was to abort and crash the system if anything went wrong. The downside to this however, is that I don't get any debugging information when something does go wrong. Based on a previous report I got, I suspect the issue has something to do with file operations. This may be related to the motion support as you say, as that adds additional file operations to load and store the motion controls calibration. What I don't understand though, is why I can't reproduce it with either of my DS4 controllers, or why it hasn't been reported for any other controllers supporting motion controls.

Here's a version I built that removes the disconnection code. If the same error triggers, it will now crash your console, but it will generate an error report that you can upload here for me to take a look at.

MissionControl-0.7.0-ds4-disconnect-fix-4f5cb51.zip

[reichembach]

Sorry for the late reply, could only test right now. Tried the version you provided but the result is the same, pairs and instantly disconnects. Also didn't crash, which I assumed it would based on this

If the same error triggers, it will now crash your console, but it will generate an error report that you can upload here for me to take a look at.

EDIT: I tried looking for a log just in case but couldn't find anything that seemed related to mission control. If there's any specific place I should look, let me know

[ndeadly]

If this is the case, then it must be getting disconnected by Nintendo's code in your case. Try following the instructions here https://github.com/ndeadly/MissionControl/issues/342#issuecomment-954172676 and see if it helps.

[reichembach]

There were no controller profiles to put the flag in, but I tested it again a few hours later and it didn't disconnect anymore! I have no idea why it suddenly started working, but I'll take it lol

[ndeadly]

@Bungwr could this be the same problem you've been having? https://github.com/ndeadly/MissionControl/issues/488#issuecomment-1169120107

[Bungwr]

@Bungwr could this be the same problem you've been having? #488 (comment)

Hi ty for mentioning me for this. I don't think it is the same issue as my controllers r updated and it have the same issue on a ds4. For now I'm using an older version which works perfectly for me. Although I would like the motion controls but I don't like it that much on a controller.

[mrsteyk]

Here's a version I built that removes the disconnection code. If the same error triggers, it will now crash your console, but it will generate an error report that you can upload here for me to take a look at.

MissionControl-0.7.0-ds4-disconnect-fix-4f5cb51.zip

weirdly enough I got a crash (I'm using updated DualSense) report_016cbc44c.bin

[Fireboter]

im having the same issues, did u solve it?

[11701177]

Is there an update on this? This seems to be an ongoing issue. I exeperience the same error

[Fireboter]

Is there an update on this? This seems to be an ongoing issue. I exeperience the same error

I did not, please tell me if u find a solution.

[ndeadly]

I finally got around to adding logging back to the latest development code. Try this build out with your controller and post the mc-mitm.log file it creates on your sd card if the controller is still disconnecting.

MissionControl-0.7.0-debug-logging-f55ca02.zip

[11701177]

Hi ndeadly,

seems like the latest dev release fixed the issue. I was able to connect ps4 and ps5 controlers

[Fireboter]

Hi ndeadly,

seems like the latest dev release fixed the issue. I was able to connect ps4 and ps5 controlers

I'll try tomorrow, thanks a lot!

[Fireboter]

It works, thank u so much!

[ndeadly]

Since the recent posts indicate that the above dev build fixes the reported issues, I'll assume this issue has been resolved in one way or another. If there are still issues when running the latest release then this issue can be re-opened.