[Bug Report]: NFC reads gets the system stuck

[jeda]

Switch Firmware Version

19.0.0 (Latest)

Atmosphère Version

1.8.0 (Latest)

Mission Control Version

0.12.0 (Latest)

Boot Method

Hekate

Issue Description

After updating to Mission Control 0.12.0, I ran into issues while using my DualShock 4.

As soon as a game attempted to use NFC, whether for amiibo or not, everything would freeze - CPU 4 would get stuck at 100% (according to Status Monitor Overlay), not even letting me go back to HOME, until the game stopped attempting to read NFC.
I ran into this issue with Splatoon 3 (which crashes once you try to switch zones when this issue happens, probably unrelated as it struggles to load data), and Sky: Children of the Light (using the STAR scan function).

To reproduce, you just have to use anything that tries to read NFC.

Error Report

No response

Additional Context

After testing, seems like commit 6ce89a7 is the culprit.

I reverted this commit and recompiled. Since then, I no longer experience the issue and Mission Control returns to the old behaviour prior to this update (aka. "An error occurred while trying to access the amiibo.").

[jeda]

Changed the title as this might not be an issue specific to DS4.

[ndeadly]

Hmm, that commit was supposed to fix all these nfc issues. I was only able to test with Splatoon 2 though. Will look into it

[k1gs]

I have the same problem too.

HOS:

• [19.0.0]
  Atmo:
• 1.8.0
  Mc version:
• 0.12.0

This happens when the Dualsense controller is connected in Splatoon 3 when entering the wardrobe in the game, and the NFC box. I will separately attach a video of how the bug manifests itself, I hope it will help. I'm sorry that I can get into this Issue like this, I just thought I could report the problem right here

[tthe3d]

Can you share the version you compiled without the commit? For the people that run 19.0.1 .. This is unusable in certain games like splatoon 3.

[jeda]

Ah... I swore I did, since I had thought of it after noticing there hasn't been any new release yet.

There you go.
MissionControl-0.12.0-master-4ed9ebc.zip

[tthe3d]

Thank you !!

[tthe3d]

I just found out about a temporal fix for the error message. Turn on airplane mode , enable Internet and bluetooth leaving NFC disabled. This way console doesn't look for NFC signals.

[CountDarkk]

Idk if i'm stupid or not (i'm not a tech genius), but have you tried to use something to replace the console's function so that instead of reading the nfc signal from the controller it reads the nfc signal from apps like emuiibo? (idk, just what i thought woukd be, don't judge me).

[ndeadly]

The issue stems from low level queries to the MCU handling NFC requests. It's a problem with emulating the state machine behaviour. We're not even trying to send any amiibo data, just tell the console we don't have anything for it. Software like emuiibo is injecting amiibo data at a higher abstraction level and would not help us here.

With that said, can somebody give this a try? This build tells the console we're a Licensed Pro Controller instead of an official Nintendo one, which I think avoids the attempts to read NFC data altogether. Pretty sure it will work, mostly just want to know if there are any unforseen side effects of doing this.

MissionControl-0.12.0-licpro-test-5521028.zip

[CountDarkk]

Oh wow. The build..actually fixed it. I'ma also test it for bugs if you want. But it fixed the whole problem.

[CountDarkk]

I've tested all the button and functions.. and it seems it has no bugs. I think you can post it as build 0.12.1.

[ndeadly]

Cool, I will integrate this into the 0.13.0 release for 20.0.x support then.

I've known about the potential fix for a while, but licensed controllers have some of the official features blocked (button remapping, stick calibration etc). I recently found a way to patch it to support those features though, so i should be able to add them back (and as a bonus support them for real licensed controllers too)

[CountDarkk]

Yeah, but as far as i know i don't think atmosphere or hekate support firmware 20.0.x. Try leaving it for 19.0.x for now.