it's here on the thread.
but if you use Hekate you don't need to use modified fusee.bin
Post automatically merged:
A simple search on this thread:
https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10391081
Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)
- Thread starter ShadowOne333
- Start date
- Views 2,291,131
- Replies 3,563
- Likes 249
but if you use Hekate you don't need to use modified fusee.bin
https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10391081
As a matter of fact, it's already linked in the first post, right bellow the hekate_ipl.ini settings.
I'm not sure which tutorial you're talking about, but Atmosphere v1.7.0 removed the support for kip patches, therefore sigpatches won't work unless you launch Atmosphere's package3 via Hekate's fss0 or use a modified fusee.bin with kip patches support restored. sys-patch module works in any case.
I don't get it, I changed back to my Hekate with fusee payload and all games work fine and I only have Hekate Sigpatches posted by Impeeza, the only thing that doesn't work is tinfoil however even with FSS0 was already getting corrupted due to beta testing new OC with erista CPU UV support.
Either that or tinfoil is working bad with atmos 1.7.0 cause it was self corrupting, then after a few restarts was OK, completely deleting and downloading it again just opening the installer would still throw a error sometimes, had to do it a few times until it worked (all of this with FSS0 and Hekate Sigpatches but never happened before beta testing the new upcoming OC for erista and Atmos 1.6.2)...
However now currently everytime I change to FSS0 tinfoil works and going back to fusee it stop working but all games work fine
I don't have sys-patch, shouldn't the installed games stop working with atmos 1.7.0 fusee??
My original hekate fusee payload settings:
My FSS0 hekate settings:
Note: Had to add Safe mode cause hekate FSS0 is stupid enough not to boot if it doesn't detect loader.kip instead of just booting atmosphere without it like fusee payload which doesn't care if it's there or not...
Ps: I'm not using the modded fusee either... Does fusee only breaks new game installing and installed games still work fine???? (I thought without Sigpatches all games would stop working)
Either that or tinfoil is working bad with atmos 1.7.0 cause it was self corrupting, then after a few restarts was OK, completely deleting and downloading it again just opening the installer would still throw a error sometimes, had to do it a few times until it worked (all of this with FSS0 and Hekate Sigpatches but never happened before beta testing the new upcoming OC for erista and Atmos 1.6.2)...
However now currently everytime I change to FSS0 tinfoil works and going back to fusee it stop working but all games work fine
I don't have sys-patch, shouldn't the installed games stop working with atmos 1.7.0 fusee??
My original hekate fusee payload settings:
Code:
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=47
noticker=0
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0
[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp
[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmpMy FSS0 hekate settings:
Code:
[config]
autoboot=0
autoboot_list=0
bootwait=3
noticker=0
autohosoff=0
autonogc=1
updater2p=0
backlight=47
[Atmosphere CFW]
fss0=atmosphere/package3
kip1patch=nosigchk
kip1=atmosphere/kips/loader.kip
emummcforce=1
icon=bootloader/res/icon_payload.bmp
[Atmosphere SAFE MODE]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/icon_payload.bmp
[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmpNote: Had to add Safe mode cause hekate FSS0 is stupid enough not to boot if it doesn't detect loader.kip instead of just booting atmosphere without it like fusee payload which doesn't care if it's there or not...
Ps: I'm not using the modded fusee either... Does fusee only breaks new game installing and installed games still work fine???? (I thought without Sigpatches all games would stop working)
Last edited by guily6669,
New sigpatches please for FW 18.0.1.
Seems the NFIM patches indeed need a new IPS file.
New full set of patches:
Last edited by impeeza,
First time seeing the hidden descript.ion files in sigpatches. Are they some leftover files?
Nop they are used by some file managers as annotations or description for files. I really love TotalCommander and it use these files for descriptions of each file
Post automatically merged:
Some eones ago, all zip package had those
First of all thanks for updating the patches.
Second to that, do I assume correctly that AMS 1.7.0(-pre) still works with FW 18.0.1?
Don't forget to update the firmware / cfw number in the OP, mate
Thanks for the patches!
AH sorry, this info eluded me, thanks.
I dont wanna sound rude, but as far as I can tell he did reflect that in the name? (1.7.0p-cfw-18.0.1)Don't forget to update the firmware / cfw number in the OP, mate
Thanks for the patches!
Ah yeah, but I mean in the first post of the thread, which still said 18.0.0 and Atmosphere 1.6.2
yep, corrected nowAh yeah, but I mean in the first post of the thread, which still said 18.0.0 and Atmosphere 1.6.2
are the same for 18.0.0 and 18.0.1
bruh... including hekate_ipl.ini is a nono. I know you think it will knock down the number of false bug reports from people who don't know what they're doing, but it also messes up people's configs who actually took the time to set it up the way they want to. That's the very reason it isn't included in a release .zip of hekate. You could add it as its own attachment if you really feel strongly about including it.
I'm using system 18.0.1 and atmosphere 1.7.0 and I'm having problems with some apps or games not recognizing the sigpatches. For example the tinfoil
You don't need sigpatches for ofw unless you're for some reason installing pirated games on ofw. The provided download is for 18.0.1 sigpatches. But why even worry about it? Just get rid of the sigpatches altogether and use sys-patch. I've deleted the sigpatches folders and the corresponding lines from the hekate ini file, use only sys-patch, and have zero problems.
Similar threads
-
@
SylverReZ:
Google isn't very helpful anymore, you get recommended loads of crap that doesn't solve the thing that you're looking for.+1 -
@
Sicklyboy:
@K3Nv2, afaik yeah but I also don't think that it runs on home grade routers like openwrt/dd-wrt does. OPNsense runs on full-on x86 PC hardware -
-
-
@
Sicklyboy:
idk, I mean it had a new release back in March https://github.com/openwrt/openwrt/releases
-
-
-
-
-
@
K3Nv2:
Or from what ive heard ways to set custom imgs for 1st party routers so locked down now days -
-
@
Sicklyboy:
I've turned more features on in OPNsense lately and it's getting kind of high on RAM usage, I see. Probably bump that up to 4GB soon
-
-
@
Sicklyboy:
I only have 1 gig internet but internally I have 10 gig connectivity for everything on my lan lol
-
-
-
-
@
Sicklyboy:
eventually this desktop is going to act as a server too, just for the hell of it. Because this PC is WAY fucking overkill for how little I use it.
-
@
Sicklyboy:
And once I do that, my desktop OS that I interact with is just going to be a virtual machine and use GPU passthrough to connect everything
-
-
-
-
-
-