Does one or the other have advantages over the other method ?
I'm using fss0 right now so fusee secondary but just wondering ...
I'm using fss0 right now so fusee secondary but just wondering ...
Hekate has faster loading (by a few seconds) and can seamlessly switch between sysMMC and emuMMC. However, to support the latest firmware with atmosphere, I believe you need to wait for hekate to update (which isn't too long after atmosphere is updated). This is usually recommended one to use.
Fusee-primary focuses on one of the mentioned MMCs, and is a bit of a pain to swap (need to edit the emummc.ini file). Don't need to worry about this if you only need CFW on one of them.
Another thing that wasn't mentioned is that while there are no inherent differences to the boot methods aside from time spent booting, only one homebrew application out of all known homebrew apps will not work with fss0 and that is DZ. But there are plenty of alternative title installers so that is a non-issue.Does one or the other have advantages over the other method ?
I'm using fss0 right now so fusee secondary but just wondering ...
Another thing that wasn't mentioned is that while there are no inherent differences to the boot methods aside from time spent booting, only one homebrew application out of all known homebrew apps will not work with fss0 and that is DZ. But there are plenty of alternative title installers so that is a non-issue.
I know this is an old thread but do we know how Tinfoil is even able to detect which method was used to boot? If both Fusee and Hekate do the same thing and make no difference once hos is running how can Tinfoil tell? I've been wondering since Blawar first waged war against Kosmos but never found out the answer.Another thing that wasn't mentioned is that while there are no inherent differences to the boot methods aside from time spent booting, only one homebrew application out of all known homebrew apps will not work with fss0 and that is DZ. But there are plenty of alternative title installers so that is a non-issue.
I know this is an old thread but do we know how Tinfoil is even able to detect which method was used to boot? If both Fusee and Hekate do the same thing and make no difference once hos is running how can Tinfoil tell? I've been wondering since Blawar first waged war against Kosmos but never found out the answer.
Oh neat, thanks. So in that case even if you're chain loading fusee but you happen to have that file in the bootloader folder it will refuse to work? Seems like an easy work around is to just make a custom build of Hekate with a different path.Tinfoil checks if the patches.ini exist in the SD, fusee-primary don't need it only hekate.
Kind of seems like a hassle though to maintain. Remember the Atmosphere fork just for Incognito to work?Oh neat, thanks. So in that case even if you're chain loading fusee but you happen to have that file in the bootloader folder it will refuse to work? Seems like an easy work around is to just make a custom build of Hekate with a different path.