Yeah that's also my understanding. So guily6669 must have the patchable games then
None of the games I have are modded in any kind, tinfoil is even very picky with it and easily throw error that the game license is not valid and doesn't even allow installing unless overriding that security measure
And where I download games they clearly state the game requires FW17+ and have always been like this I just download, install with tinfoil that skips the FW version check and play fine on much lower FW for years and it just always worked with fusee payload with updated Sigpatches.
While with fss0 + Hekate Slatest igpatches I can only play games up to my FW so like I said it looks like Hekate own booting method is overriding some nice feature that always worked and even was a thing since SXOS days...
Ps: of course it gets to a point where it really needs a FW update eventually but usually can play many FW above mine just fine with fusee payload...
Then boot fusee normally and use sys patch. If it breaks then it's Atmosphere that is the issue or a signature patch. I've yet to see soemone else's complain, but I know you use exfat which hopefully most don't. So might be the factor causing the issue.
Still the Hekate Sigpatches that
@impeeza posted have all the firmwares inside the patches.ini that I checked for both fat and exFAT.
And if with fusee payload they work fine I don't see why FSS0 wouldn't with exFAT and the Sigpatches are clearly working since I can install any game and play fine as long as they are not above my FW...
I'm exactly sticking with Hekate fusee payload and still perfecting my OC to the max, but wanted to test FSS0 method to see if OC has any difference in terms of stability since Hekate has a lot of ram and OC stuff in it but whatever I'm simply currently testing 2115.2mhz at 1.212v on memories currently on loop28 of memtest longtest and will proceed with game testing and continuing my GPU undervolt per each frequency and forget about Hekate FSS0 boot method...
I honestly don't get you.
You don't want to update Atmosphere and HOS. You don't want to use sys-patch and dbi as suggested.
Everything works fine for you on your current setup when you use fusee.bin as payload. So why don't you just stick with that? Why are you so obsessed with getting it to work with the Hekate fss0 bootloader?
I already tried sys-patchs and same result at least with FSS0 boot method and updating atmosphere breaks almost everything specially my nice Lineon Conf5 OC which is by far the best by a mile away for Erista and who knows if he will ever update it ever again, its private not open source either...
And everything works fine with atmosphere 1.6.2 which is still the latest full stable release...
If you're not on FW 4.1 or lower, then you're just being stubborn. There is absolutely no reason for you to not update your firmware. None. At least on EMUmmc. If you're using syspatch, and see that Version Skip is ON, then I don't know what else to tell you. The sigpatches don't have a thing to do with ignoring the required FW version (afaik).
Whatever you're using to install the updates, is what you don't have configured correctly. Tinfoil, for example, has a setting to ignore firmware requirements when you install stuff. The other installers likely have the same setting.
EDIT: And I don't even know what this "salty" is that you mention. It's not required for sys-patch whatsoever.
If with fusee payload on my FW16.1 runs everything FW17+ why wouldn't FSS0 Hekate boot method not, that's what I would like to know.
And updating new atmosphere for example breaks the Sigpatches and the OC Im using is not updated and is by far the best and Lineon is not being around discord to hopefully update his nice Conf5.
The SaltyNX is for reverseNX, NX-FPS and other stuff I have...
----------------------------------------
It's exactly like they say on discord, fishes say to stick with fusee and snakes say to stick with Hekate fss0 and chose your poison which for me fishes are winning
And BTW Meha the current original OC suite dev just released a new sys-clk-oc-0331 on discord, just really need is for Lineon to show up with a updated Conf5