Do you have the updated patches? If you do, where did you download them from? As an additional question, do you use Hekate or fusee to launch Atmosphere?
install sys-patch and restar your console, then reinstall problematic games.
Thank you, this was helpful. I was able to update my emuMMC by dumping the firmware from my sysMMC. I have never booted CFW on my sysMMC, so I should be OK.
Try using DBI instead, has always worked without any hassle.
look inside that default.txt
I thought selecting "local wireless play" would do that. Is there any other way? I know Pokemon Scarlet had some unholy button combination one needed to press to make "local lan" play possible, would you happen to know how I can do that in MK8? Searching the internet for "Mario Kart 8 Lan Play" just gives me instructions on how to use the local wireless play function, so it's not terribly helpful. If both consoles need to be on the same FW then I'm cooked, since I'm not going to upgrade the modded switch to 19.0.1 just yet.yeah you dont need to set up lan play to do local wireless lol. I couldn't tell you why your consoles arent finding each other, maybe wireless hardware is damaged on the modded one? you could try connecting it to your wifi and seeing if you're able to make homebrew work that uses wifi, that would at least rule that out
No luck :/
I just updated the patches from a post from ShadowOne333 (new member, forum won't let me link it) and I also tried updating them from Awoo, neither did that. I use Hekate
When I try to build sys-patch I get "target (my folder) given more than once in the same rule"
Download from: https://gbatemp.net/download/sys-patch-sysmodule.38936/
Thanks for the theory, but the wireless connection on my modded console works just fine. I install plenty of games over wifi from my home PC, so if anything was the matter with the wifi connection, I should have noticed some other issues cropping up by now. Sure, the modded console aggressively blocks nintendo's servers, but I don't think that's it. Now that I think about it, I actually don't have to bother blocking nintendo, the console is banned from online play anyways, lol I just realized how pointless it is. Maybe they really do have to be on the same FW version, I don't know. I can't upgrade the modded console to 19.0.1 at the moment to rule that out, but once I do upgrade it, it will be one of the first things I'm going to test out.
you could check if you have usb 3.0 enabled and disable that if it is, because it can cause some interference with wireless. otherwise double check that both games are really on the same update version (it could be that the unmodded console updated the game while you weren't using the console and you didn't notice, for example.) also the dlc had an update at some point, if your unmodded one has the v1 dlc while the modded one still has v0 you might not necessarily notice the difference, but it could be enough to prevent them from communicating
There is no "better" way as both will lead to the same result of CFW with Atmosphere. However, the patches found in this thread are only compatible with fss0 so if you use that method, you don't have to worry about downloading sys-patch as sys-patch is compatible with fss0 and fusee.
would this config be fine for booting cfw on emmuNAND
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0
[Atmosphere CFW]
fss0=atmosphere/package3
emummcforce=1
cal0blank=1
icon=bootloader/res/icon_payload.bmp
[Warmboot Error Fix]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmpEverything looks fine except for cal0blank=1. Atmosphere's own developer SciresM has stated that blanking PRODINFO via exosphere is not foolproof for protection from Nintendo as there is other information they can grab such as battery serial number. Since there aren't ways to blank those, you could go with alternative methods of blocking such as 90DNS.
Is no better option, It is your choice, Using FSS0 Hekate is the second stage, using Payload atmosphére is ithe second stage, each one have their pros and cons
Sorry maybe a bit of dumb question but would i be able to use sys-patch and sigpatches from this forum with fusee
With Fusee payload the sigpatches are not loaded, but SYS-Patch works fine.
That did the trick. I knew it was probably some button combination, like I had to do in Pokemon Scarlet. It now works and both consoles can play with each other. I gotta write this down somewhere before I ask myself the same question a few months from now again.
