- fss0 needs "kip1patch=nosigchk" in order to load sigpatches but not "atmosphere=1"
- (chainloading) fusee needs "atmosphere=1" in order to load sigpatches but not "kip1patch=nosigchk"
kip1patch=patchname Enables a kip1 patch. Specify with multiple lines and/or in one line with , as separator. If actual patch is not found, a warning will show up
atmosphere=1 Enables Atmosphère patching. Not needed when fss0 is used.
I guess both are included in the INI to let people use fusee or fss0...so there is no correct or wrong method. All can boot atmosphere. I prefer fss0, some prefer chainloading fusee. This is just a matter of personal choice (and none are bad).
https://github.com/CTCaer/hekate?tab=readme-ov-file#boot-entry-keyvalue-combinations
ps : if I understood it correctly, kip loading should be removed from fusee in a near future...so fss0 is, IMO, better.
Thank you for the reply. I've read so much about all of this the last few days y brain is spinning. lol
So the rentry guide says to put this in the ini file:
[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp
It is not using fss0 and there is no atmosphere=1. But documentation states "(chainloading) fusee needs "atmosphere=1" in order to load sigpatches". I'm confused. What would adding that line accomplish and why does the rentry guide omit it? It feels like conflicting information.
Also, if it states that "kip1patch=patchname" is the old method that is required for patching with fss0. Even if that old method still works, what is the new method? What would the line be for same function using the new method? Rh guide uses "kip1=atmosphere/kips/*", but the only instance of that in the documentation is:
{-- Custom Firmwares --}
[Atmo Vanilla]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
# Note:
# The above adheres to emummc.ini. It will launch emuMMC if enabled, otherwise sysMMC.
# The kip1 line can be omitted if wanted. It's in example in order to mimic fusee behavior.
To me that sounds like that line from the rh guide does nothing and can be omitted? Which goes back to my question, regardless if the old method of ""kip1patch=nosigchk" still works for fss0, what would the new method be?
Last edited by RedColoredStars,