[Bug Report]: Mission Control 0.6.4 causes PANIC IN Atmosphere

[kronictripy420]

Switch Firmware Version

13.2.1 (Latest)

Atmosphère Version

1.2.6 (Latest)

Mission Control Version

0.6.4 (Latest)

Boot Method

Fusée

Issue Description

When sitting on the Change Grip/Order screen to connect BT controllers, I put PS4 con in pairing mode. After a few blinks the light bar in back stays soild, I tried to move anaologs around and nothing, so I held ps bottom down to shut off then tried again, almost immediately after the PS4 con. starts blinking the screen goes black and I get a

Panic Occured While Running Atmosphere Title ID: 010000000000BD Error: std: :abort <0xFFE>

Press POWER to continue.

To reproduce I have to try and connect PS4 controller then shut off when back light is soild and try to reconnect the controller it will cause "PANIC"

Error Report

Additional Context

Im using a boot.dat file I found on gethub for Atmosphere 1.2.6 which is the fuees.bin needed to use my sxos rcm payload injector, emuMMC 13.2.1, downloaded mission control from hb store on switch didn't work so I looked on gethub y it might not be working and someone posted a master of a few files that they changed to run smoother on emuMMC: 13.2.1, Atmosphere 1.2.6, so I downloaded them and just copied the files to the to the directory in which they belonged, also my computer never asked me if I wanted to overwrite any files so I thought that Mission Control was missing some files that's why I added them and also is when this problem started cuz I never knew how to start Mission Control.

[ndeadly]

Please post the .bin file referenced in the screenshot you posted. That is the error report. The error code displayed is a generic abort message and lacks useful information.

[kronictripy420]

how do i post it i tired to just drag n drop from desktop

[Masamune3210]

either change the file extension to a supported extension and drag and drop or upload it to somewhere and share the link

[kronictripy420]

fatal errors.zip

[ndeadly]

how do i post it i tired to just drag n drop from desktop

I think github limits the file types you're allowed to post. I would just add it to a .zip archive and post that You beat me to it

[kronictripy420]

thanks

[kronictripy420]

i appreciate the help thanks so much, if u dont mind me asking how do u go about making a hb app

[ndeadly]

Your error report shows error 0x202 occured, which is fs: Path not found. This indicates that MC could not find a required file, which is strange because the only required files are automatically created if they are not found. This could point to something like filesystem corruption. Which filesystem is your sd card formatted with?

Unfortunately, I forgot to save debug information when I released 0.6.4 so I can't pinpoint exactly where the error was thrown. If you want to run this version I just compiled and post the new error report I can try to determine where this error is actually being generated.

MissionControl-0.6.4-master-0ee33b3-new.zip

if u dont mind me asking how do u go about making a hb app

This is not the place for this kind of extended discussion. See https://switch.homebrew.guide/homebrew_dev/introduction.html or join a homebrew related discord server if you want to learn about developing for switch.

[kronictripy420]

So I looked on my sd card and my PC and comparing files and realized that I have some files from a older ver of mission Control Info.json Manifest.install

[kronictripy420]

I think ab older ver not sure

[kronictripy420]

Well I went through the master .zip already had it in PC and the new ver of mission Control versus my sd card I didn't see much of difference but just reinstalled from the master.zip and the new ver. here on gethub, got it working but can't connect PS4 con.

[kronictripy420]

Have tried like 5-6 times nothing show up on console and con. just keeps blinking then shuts off/ also now can't get btparing working anymore

[ndeadly]

So I looked on my sd card and my PC and comparing files and realized that I have some files from a older ver of mission Control Info.json Manifest.install

These files are not part of Mission Control.

Well I went through the master .zip already had it in PC and the new ver of mission Control versus my sd card I didn't see much of difference but just reinstalled from the master.zip and the new ver. here on gethub, got it working but can't connect PS4 con.

There should be no functional difference between the latest master .zip and the one I sent you. It is compiled from exactly the same commit as the release version. However, I can't be certain current build and debugging info I generated exactly matches the old release since my toolchain has likely been updated since then. This is why I need an error report from the same version.

Have tried like 5-6 times nothing show up on console and con. just keeps blinking then shuts off/ also now can't get btparing working anymore

It's possible you have a bootleg PS4 controller and are experiencing this issue https://github.com/ndeadly/MissionControl/issues/430

[kronictripy420]

These files are not part of Mission Control. here is the zip

[kronictripy420]

[Uploading MissionControl.zip…]()

[kronictripy420]

and for the bootleg ps4 controller i doubt it seeing as i purchased it from a retail store and if they are indeed sell counterfeits then they are FAULSELY ADVERTIZING.

[kronictripy420]

This is why I need an error report from the same version The nro file is the same version its just the extra files that were on the root of the sd card, the version i uploaded is the same version from which the error was produced

[Masamune3210]

and for the bootleg ps4 controller i doubt it seeing as i purchased it from a retail store and if they are indeed sell counterfeits then they are FAULSELY ADVERTIZING.

You would be horrified by the amount of bootleg controllers that make it onto shelves

[ndeadly]

Uploading MissionControl.zip…

This just links back to this issue...

and for the bootleg ps4 controller i doubt it seeing as i purchased it from a retail store and if they are indeed sell counterfeits then they are FAULSELY ADVERTIZING.

Try the fix suggested in the linked issue anyway. I've had a few users reporting this with PS4 controllers recently. It's possible there's a new Sony hardware revision that also has trouble staying connected, but I'd say it's more likely that these users have 3rd party or bootleg controllers. It's entirely possible for them to make it onto retail shelves.

This is why I need an error report from the same version The nro file is the same version its just the extra files that were on the root of the sd card, the version i uploaded is the same version from which the error was produced

Not sure what you're talking about here. There is no nro file. You just need to install the new build I linked, reboot and trigger your error, and then post the error report referenced in the crash screen.

[kronictripy420]

The .nro that sits in the switch folder is 0.6.4 when I downloaded this I believe from gbatemp it had extra files in the main directory of the folder/ and I have installed the new build u linked, but mission control doesn't trigger any errors anymore like I said in recent comments, but I can't get any of my PS4 controllers like 8 of them to connect none of them will, also btparing is not working now that I have installed the new files linked or maybe the files I asked about earlier info.json Manifest.install Are maybe part of btparing idk not sure wut those files were/are even for sorry for all the confusion

[kronictripy420]

And there was a recent update to PS4 system not sure about the controllers

[kronictripy420]

I can't believe that there would be that many bootleg controllers out there/ how sony would let them get away with this.

[Masamune3210]

Sony doesnt care unless someone complains, as it would be prohibitively expensive and time consuming to try to police the entire market of multiple countries over just some knockoff controllers

also, DS4's don't have upgradable firmware, so the console update doesn't matter. Only one that does is the DualSense

[ndeadly]

I would try deleting your paired controllers, holding the reset button on the controller and then trying to pair again. If you can't get any of the 8 to connect at all then something is very wrong.

Honestly, your SD card sounds like a mess. I don't know what btparing or the other random files you're talking about are. You're installing homebrew from unofficial sources with all kinds of random junk added. It wouldn't surprise me if you're also using an exFat card and experiencing corruption.

I would suggest you delete/rename your atmosphere/contents directory and start over fresh, with nothing but the official Mission Control release (or the one I posted above), reboot and try again.

And there was a recent update to PS4 system not sure about the controllers

System update won't affect controllers

I can't believe that there would be that many bootleg controllers out there/ how sony would let them get away with this.

If you bought 8 controllers from a reputable retailer it is reasonably unlikely that they would all be bootlegs. However, whether they are bootleg or not doesn't really matter here. If they're disconnecting, they're disconnecting. Just try the fix and see if it works.

[kronictripy420]

Honestly, your SD card sounds like a mess. I don't know what btparing or the other random files you're talking about are. You're installing homebrew from unofficial sources with all kinds of random junk added. It wouldn't surprise me if you're also using an exFat card and experiencing corruption.

You think I'm some kind of dumbass I did research on atmosphere & Hekate for 6 days before I put it on my switch

[kronictripy420]

And no I have a 256gb sd fat32 I'll send a screenshot of my sd card

[kronictripy420]

and yes your right about btparing sorry thats just the name for the .nro file in switch folder, what i meant was

[kronictripy420]

[Uploading nx-bted-0.9.3.zip…]()

[kronictripy420]

and these are what is on my sd card as of per screenshot

[kronictripy420]

![Uploading Screenshot (7).png…]()

[kronictripy420]

![Uploading Screenshot (9).png…]()

[kronictripy420]

showing the fat32 files system

[Masamune3210]

Honestly, your SD card sounds like a mess. I don't know what btparing or the other random files you're talking about are. You're installing homebrew from unofficial sources with all kinds of random junk added. It wouldn't surprise me if you're also using an exFat card and experiencing corruption.

You think I'm some kind of dumbass I did research on atmosphere & Hekate for 6 days before I put it on my switch

no need to get hostile, you can do research on something for years and still miss things. Nobody knows everything......

Also your screenshots didn't upload, you have to wait till they are done before you hit comment or else the link gets broken

[kronictripy420]

yeah i know im sorry just ticked me off a little, n ok ill repost them

[kronictripy420]

[kronictripy420]

[kronictripy420]

If you bought 8 controllers from a reputable retailer it is reasonably unlikely that they would all be bootlegs. However, whether they are bootleg or not doesn't really matter here. If they're disconnecting, they're disconnecting. Just try the fix and see if it works.

also i have never had a ps4 controller connected before, im supposed to be sitting on the change grip/order screen right?

[kronictripy420]

You're installing homebrew from unofficial sources with all kinds of random junk added.

i only downloaded one file for my switch from an unoffical source and that was the mission control liked here MissionControl.zip and above

[kronictripy420]

every thing else has either been from here Github or homebrew store or the offical web site https://apps.fortheusers.org/

[Masamune3210]

That site isn't official, it's a community effort. The only official site to get most of not all of homebrew for the switch is from their respective GitHub repos

[kronictripy420]

Well either way I appreciate both and all of you for your hard work, I was just asking y mission control was causing panic in atmosphere

and fixed if it from the master ndeadly posted

now I have it working I can't connect PS4 controllers

I start Mission Control in hbl hold x to delete connected

well when I do this how do I get back to change grip/order there r no controllers connected so I have to connect original con. back to get there

On Mon, Feb 28, 2022, 6:02 PM Masamune3210 @.***> wrote:

That site isn't official, it's a community effort. The only official site to get most of not all of homebrew for the switch is from their respective GitHub repos

— Reply to this email directly, view it on GitHub https://github.com/ndeadly/MissionControl/issues/433#issuecomment-1054779089, or unsubscribe https://github.com/notifications/unsubscribe-auth/AX57ZU3KHEWTMLL3CYRUH73U5P5IDANCNFSM5POGW5ZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you are subscribed to this thread.Message ID: @.***>

[kronictripy420]

Is this what Mission Control looks like in hbl

[kronictripy420]

[kronictripy420]

And this happened to nx-bted 0.9.3 when I installed the master ndeadly posted on here, not that I really care about it just thought it would be Kool to pair headphone while playing games but not a big concern

[kronictripy420]

Btparing manager Intialize f601

[kronictripy420]

[ndeadly]

@kronictripy420 you don't need nx-btred. Since 13.0.0 HOS has had native bluetooth headphone support. This is probably the source of your problems (and now I understand what you meant when you were talking about "btparing" - that's nx-btred's btpair app). Having nx-btred present now that native bluetooth audio is active is almost certainly interfering with bluetooth operation.

btpair probably broke with changes in 13.0.0. This app relies on a feature of Mission Control to redirect system events used in controller pairing. If something goes wrong with the app you can end up with a situation where the redirection never gets switched off and the console stops receiving those events. This is probably why all your controllers stopped working. It was likely the act of rebooting the console, rather than the new build I posted that appeared to "fix" it.

Delete /atmosphere/contents/0100000000000081 and reboot.

Also, please try to keep your thoughts contained to single posts. This isn't a chat server :)

[ndeadly]

And please take a read of https://github.com/ndeadly/MissionControl#usage as the fact you're trying to launch .nro homebrew at all suggests that you don't understand how Mission Control is supposed to work.

[kronictripy420]

Ok I did what you said, so I copied all of my contents folder to desktop, completely deleted atmosphere folder off sd card and did a fresh install put contents folder back, in atmosphere folder and the put the mission control in contents "010000000000bd00" and exefs_patches "bluetooth_patches" and config "MissionControl" folders back where they belong and rebooted atmosphere,after reboot deleted all pervious connected controllers, go to change grip/order then put PS4 controller in pair mode and it starts blinking for a good 1-2 mins then shuts off nothing happens to console just won't pair so I retried like 10 times with all 8 of my PS4 controllers and nothing also I tried to also install sys-modules to maybe turn on mission control not sure and the bottons to open sys-modules aren't working and I put them in there respective respiratories

[Masamune3210]

If no system module patches are working either you are installing them incorrectly or your sd card's filesystem is messed up.