ndeadly

@Sinthrill that sounds perfect if it can be used without triggering Amiibo errors in games. Do you own a copy of Splatoon 2? If so, or you know of another...

Do you get this same error without Mission Control running? That log shows no attempt to read NFC data, only the initial handshake. This could mean that HOS is simply...

It looks to just show a second connection attempt. Nothing new. I will try a few things after work today with the parameters your controller is sending. I would still...

Thanks, appreciate you taking the time to investigate. I will have to check later whether this new log contains anything interesting. At a glance, still no attempts to read NFC...

> I didn't realize SMO has amiibo functionality. I can give it a shot and try to get one of those errors with this controller. You had those errors just...

Yeah, this is exactly what we've been looking at already. It's why I wanted a log from the licensed controller in the first place. The info on parts of that...

Please confirm the module is running (`MINUS` + `DPAD_UP` button combo on the left joycon should activate the capture function when connected wirelessly), that you are on the correct menu...

You still didn't confirm the module is actually running. Nothing Bluetooth related has changed since 14.0.0, and Atmosphere updates don't affect Mission Control (unless they enforce a newer minimum libstratosphere...

@Pentalex have you tried charging the controller? This can happen with low controller battery too.

You could also try this build of the current development branch. I've made several minor accuracy improvements to controller emulation that may make connecting more reliable in some cases. [MissionControl-0.7.0-develop-c5093b2.zip](https://github.com/ndeadly/MissionControl/files/9568524/MissionControl-0.7.0-develop-c5093b2.zip)