are these all the patches needed for atmosphere 17.0?Well thanks to MrDude and the release of latest IPSPatchCreator here are the sigpatches for FW18.0.0
OP will be updated when full set of patches get available, there is no new Atmosphère Patches, well, because there is no new Atmosphère yet
So what does this mean?Atmosphère 1.7.0 (prerelease)
fusee no longer supports applying IPS patches to KIPs.
- The only KIPs that are ever present are a) atmosphère modules, b) custom system modules, or c) FS.
- The IPS subsystem was originally designed to make nogc patches work for FS, but these are now internal, and it appears the literal only kip patches that exist are for piracy.
- I could not find any kip patches posted anywhere made for any other purpose.
you use package3Hmmmm, so how to apply our sweet sigpatches for now with AMS 1.7.0-pre when fusee no longer supports IPS sigpatches to KIPs?
Sys-patch is the best option if it gets updated. Forks are frowned upon if supported is needed.Sys-patch or building ams with this feature enabled
Sys-Patch is already updated! and Happy June 15thSys-patch is the best option if it gets updated. Forks are frowned upon if supported is needed.
So Package3 or Sys-Patch imho the alternatives imho
Strongly suggest this yes. (thats what I will do)For those who chainload fusee through hekate, do we have to move to syspatch?
yes they are, they are now for all firmware up to 18.0.0 and Atmosphère up to 1.7.0are these all the patches needed for atmosphere 17.0?
no move, but is highly recommended have both of them.For those who chainload fusee through hekate, do we have to move to syspatch?
Can I use these patches with Atmosphere alone or do I have to use Hekate? Thanks!Well thanks to MrDude and the release of latest IPSPatchCreator here are the sigpatches for FW18.0.0
OP will be updated when full set of patches get available, there is no new Atmosphère Patches, well, because there is no new Atmosphère yet
Happy (pre)June 15th everybody! and the new COMPLETE set of sigpatches is Here, remember to use the latest Hekate on FSS0 Package 3 mode to be able to load the sigpatches, and/or use SYS-Patch Sysmodule.
You can NO LONGER use OFFICIAL Atmosphere with signature patches. They're no longer supported.Can I use these patches with Atmosphere alone or do I have to use Hekate? Thanks!
[config]
autoboot=0
autoboot_list=0
bootwait=0
autohosoff=0
autonogc=1
updater2p=1
backlight=100
[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp
[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp
[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp
https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10389534Can I use these patches with Atmosphere alone or do I have to use Hekate? Thanks!
I always have this question...
What really the "atmosphere=1" line does?
atmosphere=1 | Enables Atmosphère patching. Not needed when fss0 is used. |