Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,303,069
  • Replies Replies 7,368
  • Likes Likes 266
  • Haha
Reactions: Blythe93
Atmosphere still works with sig-patches if loaded via package3 and hekate. Or you can just use a modded fusee.bin such as this one that I compiled for the latest atmosphere which has ips kip patches support.
This fusee got the usb 3.0 working in atmosphere?
 
It's the exact same Fusee.bin than original, only the process of KIP patches reenabled.
Newbie question
Now I have sys-patch fully working
I download sigpatches and updated in SD
If fusee.bin is regular one.

Do I need change with KIP patches enabled?
Could I have sigpatches and sys-patch together?
Could I delete sigpatches?
 
If fusee.bin is regular one.

Do I need change with KIP patches enabled?
Could I have sigpatches and sys-patch together?
Could I delete sigpatches?
If you have sys-patch, you don't need sigpatches or the modified fusee.bin.
You can delete sigpatches or leave them be, they won't conflict with sys-patch. Sigpatches won't work at all if you aren't loading Atmosphere's package3 via Hekate's FSS0 or using the modified Atmosphere's fusee.bin [1.7.0][1.7.1].
 
Sigpatches won't work at all if you aren't loading Atmosphere's package3 via Hekate's FSS0 or using the modified Atmosphere's fusee.bin [1.7.0][1.7.1].
Sorry, I think I understand but a little confusing with this sentence

“package 3” is equivalent to modified fusee.bin?

Why is better or not sys-patch vs sigpatches?
 
“package 3” is equivalent to modified fusee.bin?
For loading sigpatches, loading Atmosphere's package3 via Hekate's FSS0 or using the modified fusee.bin with support for the kip patches restored results with sigpatches being properly loaded and game backups working again.

Why is better or not sys-patch vs sigpatches?
As of lately, I've noticed that some users were experiencing problems with sigpatches (games worked for some, but not for the others), while sys-patch worked for pretty much everyone, including those that had problems with sigpatches. Therefore, I personally recommend sys-patch.

As for the differences between two, sys-patch requires less frequent updates and it's easier to update among other things. TotalJustice, the original author, made a thread here, explaining what makes sys-patch good.
 
For loading sigpatches, loading Atmosphere's package3 via Hekate's FSS0 or using the modified fusee.bin with support for the kip patches restored results with sigpatches being properly loaded and game backups working again.


As of lately, I've noticed that some users were experiencing problems with sigpatches (games worked for some, but not for the others), while sys-patch worked for pretty much everyone, including those that had problems with sigpatches. Therefore, I personally recommend sys-patch.

As for the differences between two, sys-patch requires less frequent updates and it's easier to update among other things. TotalJustice, the original author, made a thread here, explaining what makes sys-patch good.
Well, thank you
After all if it works don't touch. sys-patch seems like it's working so I don't need to know much more about sigpatches. I have updated for now but not active as I don't need while everything is working as I need
 
  • Like
Reactions: Blythe93
@impeeza and @Blythe93 Thank you for trying help me out and i figure that i didnt have the nx-ovlloader in my sd to access the sys-patch now it working with my fusse.bin normal straight payload not to hekate. I apologize for 1 bad language on my last post because of being frustrating I am not smarter than a 5th grader :cry::cry:. LoL
 

Attachments

  • 20240822_204151.jpg
    20240822_204151.jpg
    1.2 MB · Views: 78
I replaced my standard hekate.ini with this one and all my games is now gone. Is that normal?
I transferred a game. Transfer is ok, signature is invalid. Line 2,3,4 XCI=NSP
Line 5: signature invalid
 
I replaced my standard hekate.ini with this one and all my games is now gone. Is that normal?
I transferred a game. Transfer is ok, signature is invalid. Line 2,3,4 XCI=NSP
Line 5: signature invalid
May be it depends if you start a SysNAND or an EmuNAND
 
i've been away from hacking since 16.0
did anything changed?
sigpatch is the same for 18.1.0 or i should not update?
 

Site & Scene News

Popular threads in this forum