Why is Hekate not recommended as a bootloader? I've never heard anyone else say that.
It can be slow to update compared to fusee-primary, and you can't use blawar's Tinfoil with it unless you're chainloading fusee-primary anyway.
Sig patches for a Hekate setup (not chainloading) are usually slower too.
If you're going to use Hekate, I recommend chainloading fusee-primary when you want to boot your emuMMC.
Hekate can be slow to update, sigpatches for a Hekate setup can be slow to update, and blawar's Tinfoil (last I checked) doesn't work with Hekate unless you're chainloading fusee-primary. I'm not wrong.
Actually, the games didn't need reinstalling.
I'm now going to use hekate for when I need to get to eMMC quick after a poweroff
That's fine, and that's the easiest thing with your setup, but it's recommended that you setup a boot entry that chainloads fusee-primary.
Hekate updated less than 24 hours after Atmosphere 0.14.3 was released, Hekate sigpatches have been completed and shared before fusee-primary patches for the last couple months, and Dz-Tinfoil doesn't block any files on the SD card anymore (I don't know when this changed but feel free to see for yourself).
That's not always the case. It has been days/weeks before.
That's just not true, and there have been times when fusee-primary patches beat Hekate patches by days.
This is good news if it's true. I'm not about to test it though.
--------------------- MERGED ---------------------------
Put fusee-primary in bootloader\payloads and select it. Alternatively, make a config pointing to it.
You can select payloads while in Hekate. Alternatively, you can edit your config on your SD card to point to that payload.
Going back an entire year, Hekate has released HOS compatibility updates within the same day as Atmosphere. It's not slow to update.
It is true, go check the threads. It's been this way since at least Atmosphere 0.14.0, if not earlier. The singular person making the patches does fss0 first.
Even though fusee-primary patches have been faster in the past, that's no longer the case, almost as if it's not a rigid concept or fact that's worth repeating to people anymore.
I said it can be, and it has been in the past. You don't have to go much farther than a year to find instances when it a week or more, not hours. I'm not wrong. Hekate is always going to be slower than fusee-primary, since fusee-primary is bundled with Atmosphere.
You said it can be slow to update, which is provably wrong when you search back any reasonable amount of time. You didn't say "slower than fusee" and leave it at that, don't move the goalpost. Not like sigpatches are ever pumped out in the time between a Atmosphere and Hekate update, regardless.
Your "reasons" for not recommending Hekate to the question asker don't amount to anything other than creating a baseless and unrealistic fear that they might end up with an outdated setup if they're not using the exact software you're outlining.
- Hekate used to regularly lag 7-10 days behind fusee-primary.
- Hekate always lags behind fusee-primary, whether it's a few hours or over a week.
- Signature patches have been released for fusee-primary before Hekate was updated to work.
Using Hekate as bootloader is clearly talking about chainloading. And updating it doesn't matter if you're only using it as a bootloader.
Similar threads
- No one is chatting at the moment.
