STILL CAN'T LOAD FS, CAN'T RUN NSP GAMES WITH FUSEEHere they are, Atmosphère with FS patches re enabled and the correspondent sigpatches.
STILL CAN'T LOAD FS, CAN'T RUN NSP GAMES WITH FUSEEHere they are, Atmosphère with FS patches re enabled and the correspondent sigpatches.
Nsp or converted xci?STILL CAN'T LOAD FS, CAN'T RUN NSP GAMES WITH FUSEE
This fixed it for me too. Thank you so much for posting this.Sigpatches are not working for me under FW 18.1.0 and new atmosphere, even when using fss0.
This version of Sys-patch works flawlessly, though.

yes you must no upgrade your fimware until all loaders/sysmodules/homebrew get updatedI think FW 18.1.0 brings more problems than expected. I am having serious problems when booting with Hekate. I am also having problems when using sigpatches. I think I'm going back to 18.0.1 until all these issues are solved.
The only thing that seems to work properly in FW 18.1.0 is booting from latest version of fusee.bin and using sys-patch_1.5.1_patched.

It's a matter of taste, some people like peanut butter and Jelly and other jelly and peanut jelly, others only jelly or only peanut butter...noob question here, sorry in advance: if the sys-patch module solution works, why are people going through the hassle of making, releasing and using patched versions of atmosphere bring back support of syspatches? Is there a tradeoff of some sort using one instead of the other?
There are another kip patches, not only sigpatches...noob question here, sorry in advance: if the sys-patch module solution works, why are people going through the hassle of making, releasing and using patched versions of atmosphere bring back support of syspatches? Is there a tradeoff of some sort using one instead of the other?
What is the difference of this version 1.5.2 and the previously released patched version of 1.5.1?install SYS-PATCH sysmodule
https://gbatemp.net/download/sys-patch-1-5-2-binary-fw-18-1-0-atmosphere-1-7-1.38686/

The version displayed on the NRO and Overlay ha ha ha ha, just for remove the -dirty tag, my OCD was killing me.What is the difference of this version 1.5.2 and the previously released patched version of 1.5.1?
Thanks for explainingThe version displayed on the NRO and Overlay ha ha ha ha, just for remove the -dirty tag, my OCD was killing me.
So is this an alternative to the patched fusee.bin? An alternative way of re-enabling kip patches?Here they are, Atmosphère with FS patches re enabled and the correspondent sigpatches.

Using Hekate's FSS0 loading method.Thanks for explaining
So is this an alternative to the patched fusee.bin? An alternative way of re-enabling kip patches?
Sorry I am a little confused![]()
Sorry I meant the attachments from your post here: https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10437484Using Hekate's FSS0 loading method.

The only way to load FS KIP patches at boot are:Sorry I meant the attachments from your post here: https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10437484
What are they used for?
Sorry for my noob questions. Is it fusee.bin that needs to be modified or Atmosphere modules themselves? I was under the impression that fusee.bin should be modified to enable FS KIP patches but your released a modified Atmosohere package so now I am not sure anymoreThe only way to load FS KIP patches at boot are:
period.
- If you inject fusee.bin as your payload, Modifying the atmosphère code to reenable that and build a new version.
- Using Hekate's FSS0 package 3 loading method.

I made a full built of atmosphère the only change on the code was reenable fusee FS KIP loading, so you can use only the fusee.bin or all the set including the sigpatches.Sorry for my noob questions. Is it fusee.bin that needs to be modified or Atmosphere modules themselves? I was under the impression that fusee.bin should be modified to enable FS KIP patches but your released a modified Atmosohere package so now I am not sure anymore
Thank you for your patience with my questions