That is not a sigpatch issue. If a game initially boots then the sigpatches worked, any issue that happens after the game opens is unrelated.
- Status
BOTW doesnt work for me either after updating
Edit: hes right its emuiibo
i don't even us it so idk how that happened :s
Last edited by Lazy0wnage,
Doesnt matter. Unless the game is giving you an error saying its corrupt or that you dont own it then it is *not a sigpatch issue*. Most likely the cause is a sysmodule you have that doesnt work on newer atmosphere versions such as emuiibo.
Last edited by Ibcap,
I'm getting "the software was closed because an error occurred" with several games like BOTW, Mario Kart 8, Mario Odyssey, Smash with a clean installation of Atmosphere 0.14.2 with the latest sigpatches from this thread, latest OFW too.
When I switch to SX OS everything works just fine, any idea what could be going wrong with my setup?
When I switch to SX OS everything works just fine, any idea what could be going wrong with my setup?
Couple possibilities. First, make sure you're using fusee primary and not hekate. Second, some stuff when installed via sx' installer won't work on atmosphere so maybe you can try reinstalling via atmosphere. Third, you can try the maintenance mode trick, that will sometimes fix bad data.
- Joined
- Aug 1, 2008
- Messages
- 1,856
- Trophies
- 1
- Age
- 41
- Location
- Sacramento, CA
- Website
- www.sniffglueworshipsatan.com
- XP
- 1,669
- Country
I believe XCIs installed with SX OS's installer (and some NSPs, too) still don't work in Atmosphere. I highly advise against using SX OS at all if you can help it, for various reasons, some more obvious than others, but the biggest reason being, according to most people, is the fact that their code is literally ripped from Atmosphere and various other open-source applications. A big no-no in my eyes, as well. Not to mention that it doesn't play well with most homebrew, and developers as well as other users will tell you, in so many words, that they will not help you fix TX's bullshit, so to speak. Stick with AMS, you'll thank us later.
Also, to add on to what @lbcap stated, the Atmosphere payload that Hekate loads greatly affects things like sigpatches and even homebrew (like Tinfoil). Tinfoil only works with fusee-primary (and the "Atmosphere" sigpatches, too). What you need to do is make sure that Hekate is loading THAT payload and not fusee-secondary. You can edit your hekate booloader ini to do this automatically, add it to the "Launch" menu, or you can do it manually from the "Payload" menu. Otherwise you'll need the "fss0/Hekate" sigpatches (yeah, there's two signature patch branches now) if you continue to go with the default bootloader settings.
Last edited by GuyInDogSuit,
Well, that was fast and really informative, thanks for replying @Ibcap and @GuyInDogSuit , I really appreciate your help.
And yes I'm only booting Atmosphere via fusee primary and I think those games were installed through XCI with SX OS in the past, I had no idea about that issue. (Edit: I've tested reinstalling those titles in their proper NSP format and now they're working just fine, case solved!)
Thanks for all the additional info @GuyInDogSuit , I will definitely stick to Atmosphere only after fixing those installations.
And yes I'm only booting Atmosphere via fusee primary and I think those games were installed through XCI with SX OS in the past, I had no idea about that issue. (Edit: I've tested reinstalling those titles in their proper NSP format and now they're working just fine, case solved!)
Thanks for all the additional info @GuyInDogSuit , I will definitely stick to Atmosphere only after fixing those installations.
Last edited by TheMartiniPolice,
- Joined
- Aug 1, 2008
- Messages
- 1,856
- Trophies
- 1
- Age
- 41
- Location
- Sacramento, CA
- Website
- www.sniffglueworshipsatan.com
- XP
- 1,669
- Country
So I have to reinstall BoTW? oh sh¡t...LMAO
Yeah, someone mentioned earlier (in this thread? don't remember) that emuiibo is broken in combination with even Atmosphere 0.14.2, which was causing loading their game to fail. Reinstalling sounds like a pain, for sure, but the alternative is a tad faster.
For people having issue with some games not booting remove emuiibo
sd:/atmosphere/contents/0100000000000352
sd:/atmosphere/contents/0100000000000352
Last edited by burhansalih,
In any case, it is recommended that the cause of any problems occurring after updating CFW/FW should always be sought first with the installed sysModules, which are then no longer compatible with a more recent CFW/FW version and require an update.
Oh by the way, Mario Kart 8 was the only title that persisted with "the software was closed because an error occurred" even after doing a fresh install with NSP.
But weirdly enough the problem goes away after rebooting into maintenance mode (holding volume + and - before starting the system) and going back into Atmosphere.
To add more info to my previous situation, I'm not running any sys modules in the background.
But weirdly enough the problem goes away after rebooting into maintenance mode (holding volume + and - before starting the system) and going back into Atmosphere.
To add more info to my previous situation, I'm not running any sys modules in the background.
Common issue, thats why I recommended trying that. I believe it has to do with the console caching bad data but im not sure.
OFW 10.2.0 is out and it breaks CFW. Do not update if you're using CFW and wait for AMS 0.14.3 and new sigpatches.
Update : AMS 0.14.3 is out.
Update : AMS 0.14.3 is out.
Last edited by masterchan777,
Isn't that issue something that could be reported to atmosphere? Maybe there's an issue when injecting fusee primary, or chain-loading it?
This is not an issue with fss0 payload/sigpatches method it seems.
Yep, in the same boat here... any ideas when that might be?
Respect to those who make them, of course.
@Ibcap is normally very good at posting on the main page when sigpatches have been updated.
- Status
Similar threads
