Unfortunely, since updating to 14.x, the SysModule we need to use in the tutorial no longer works. Is there a solution for this, or do we just have to wait to version 14 support.
Odd. I don't have access to my Switch right now so I can't double-check if the same thing happened, but I could've sworn it worked okay when I updated to 14.1.0 (although not 14.1.1) - that said, don't get me wrong, I'm not doubting you.
Assuming that this isn't the result of user error, then we'll probably have to wait for version 14 support yeah. I'm afraid there's not too much I can do if that's the case. That said, in the meantime, make sure you check that you've done the following:
What's obvious and what you've probably already done, but I'm including just for the sake of ruling them out:
- Updated Atmosphere to the latest version.
- Booted into CFW.
- The client reports that a controller slot is connected when you press the right bumper to assign one (the X changes to an O).
What might not be obvious:
- Make sure you've allowed the client to communicate with other devices on your network. If your network's a private network, allow it to communicate on private networks. If it's public, do the same for public networks. I think you can check/adjust this in Windows Defender/Windows Firewall. I assume that if it worked for you before, then you don't have to change this.
- Make sure your network doesn't have any new settings that'd prevent your computer from communicating with your Switch and vice-versa.
What might be user error:
- Make sure the IP of your Switch matches the one you typed into the client - keep in mind, the IP can change if your router's restarted or something along those lines.
If you went through all of that and it's still not working, then it's more likely it's a sysmodule problem. Either way, I'll double-check and see if it stopped working for me too.
Edit: In retrospect, sorry to hit you with a giant wall of text. I just want to rule out as many factors as I can before I get the chance to check for myself.