- Status
I don't really know what is happening in the background as to what is fusee primary loading during the 37 seconds of boot time compared to hekate's fss0= 17 seconds.
I think @SciresM could have the technical reply to that. But doubt he will want to do so as it might cause some bad reactions from the salty part of the switch hacking community.
I mentioned in another thread that for me secondary's faster boot times were more convenient when I only want to play games. But to this date I am yet to find the real reason as to what makes one way better/different in some uses than the other.
Short answer is fss0 uses hekates config files and sigpatches. Fusee primary uses atmospheres. Primary is slower but I doubt most people are rebooting often enough for the extra 20 seconds to matter.
Hello, may you expand on why sre fusee patches recomended over fss0?
I used a configuration for stock, emummc cfw and sysnand cfw, I guess for this I would need to just use hetake's built in options to force enable/disable emummc prior to running fusee_primary, but with fss0 sigpatches I could disable (or rather, not enable) sigpatches trough hetake ini files when booting, is there a way to do that with fusee? (Jist curious)
Theres a few reasons I recommend primary over fss0, none of them make it objectively better but just my recommendation.
Firstly, anecdotally is has fewer issues. Usually from my experience when people have problems related to games not working switch to fusee primary and its sigpatches fixes the issue.
Secondly its much simpler for support. By this what i mean is users generally dont know if they are using primary or fss0 and trying to get them to figure it out for giving support is a nightmare. Because of this on the discord servers I mod we tend to just recommend fusee primary, because it will cut down on support time and confusion by just having everyone use the same method.
Thirdly, it tends to have faster and better support. The sigpatches always come out for it before fss0 and a certain homebrew app tends to really not like fss0.
If you know what youre doing feel free to use fss0, this is just a personal recommendation not me saying fss0 is bad.
As for booting, usually I would recommend people swapping from sysnand and emunand use the hekate stock sysnand function and chainload emunand through fusee primary. If you want to use both sysnand and emunand with cfw you can keep one as fss0 or just keep using what works for you.
This has been so far the most clear reply I have read regarding the two options. And homebrew wise is also a good reason to eus primary over fss0.
However I am still wondering technically how the patches are being loaded and what takes more time in fusee primary than in fss0.
Questions like: is fss0 skipping sept loading? Is fss0 loading all the same patches/modules that primary is loading and if so which ones is it not loading and are they necessary for what functionality?
What are you talking about homebrew wise? There is no difference between fusee and fss0. The only differences between the two are boot times and required patches. Otherwise Hekate is superior to fusee in every single way. And if you understand how sept works, you would realize that is impossible to skip it.
Regarding sept I will read more into it to understand it's inner workings.
Can you elaborate more how is Hekate "superior to fusee in every single way" if the differences are boot times (faster for hekate) and required patches?
Unlike fusee, Hekate has a wide variety of tools and features at its side not limited to AutoRCM, eMMC dumping, the battery desync fix, the archive bit, and so much more. Its much better and easier to troubleshoot with Hekate as opposed to fusee because you can directly control whatever it is you're launching. For example, you cannot tell if you booted emuMMC or not with Fusee unless you use different themes and even then, fusee will not hesitate to kick you into sysMMC. Hekate not only lets you choose which one you wish to launch but will fail if you try to launch emuMMC preventing you from tainting sysMMC. Combine this with the faster boot times and fusee is useless.
I'll probably just stay where i'm at then. No new games interest me until paper mario comes out
Drax you know perfectly well that you can use those tools with hekate while also chainloading fusee from hekate. The conversation is fss0 vs fusee primary.
no it has nothing to do with your Firmware/Update.
It could be your wrong formated SD Card. YOu also could try to overclock your switch a bit.
I've already partially addressed that with the faster boot times as well as with the emuMMC options. Additionally, booting with fusee as opposed to fss0 means you have to configure BCT.ini as opposed to hekate_ipl.ini which is not as easy since you can modify hekate_ipl.ini from within Hekate but you have to edit BCT.ini manually. This is why so many users had nogc issues despite disabling it in Hekate.
- Status
Similar threads
- No one is chatting at the moment.
