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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,212,284
  • Replies Replies 7,309
  • Likes Likes 266
And I would do the same. He earns all our respect. My question was more about his reasons.
AH, Ok, sorry I didn't understanded. His reasons was he do not want the hard work put on Atmosphère got disrespected by any small cricket on the pond. so if anybody wants to change any they must take the effort.
 
  • Like
Reactions: ciaomao
With all due respect, may we ask why you shouldn't help?
Because the only thing it really enables is piracy, and SciresM is very much against piracy. Impeeza is being respectful and abiding by SciresM personally asking him to not publicly post this specific thing. Props to Impeeza for the respect.
 
  • Love
Reactions: impeeza
Hey I have the latest Sys Patch 1.6.0 installed, do I need to install the latest Sigpatch as well?

IF so what is the link to the latest Sigpatch and how do I check which version I have?
 
looking at the avatar i think its @bth ?
one would imagine that BornToHonk would reveal that yes.

i am not hexkyz however, lmao (my pfp is the default github generated one, and to me, it seemed to resemble a clown, so i kept it that way) (i changed it to avoid confusions with other people who use github genrated profiles, as apparently some people cant tell the difference)

clown.jpg
 
Last edited by bth,
one would imagine that BornToHonk would reveal that yes.

i am not hexkyz however, lmao (my pfp is the default github generated one, and to me, it seemed to resemble a clown, so i kept it that way) (i changed it to avoid confusions with other people who use github genrated profiles, as apparently some people cant tell the difference)

View attachment 563294
take your time on that project haha
 
The guide https://gbatemp.net/threads/building-atmosphere-on-windows-using-msys2.613446/ is aimed to teach how to build Atmosphère from Code.

now the changes you need to put on the source files I am not allowed to share, SciresM asked to no do it.

but you can compare the changes on the commit 46a4357 (Nov 13, 2023) https://github.com/Atmosphere-NX/Atmosphere/commit/46a43578829163cd08b9ddcaaacc6febd1e71e0e to learn what lines where removed and which ones you need to put back on the files before built it.
Thank you so much @impeeza, walked through the steps this weekend and have everything working perfectly on FW21.2.

At the end of the guide it did say "as you are getting a new set of binaries, you need new set of sigpatches" but I was able to use the sigpatches linked in this post without issue. Perhaps because I only used fusee from my build.
 
  • Love
Reactions: impeeza
Thank you so much @impeeza, walked through the steps this weekend and have everything working perfectly on FW21.2.

At the end of the guide it did say "as you are getting a new set of binaries, you need new set of sigpatches" but I was able to use the sigpatches linked in this post without issue. Perhaps because I only used fusee from my build.
Perfect, also SYS-Patch will take automatically the changes needed for the new binary.
 
  • Like
Reactions: protivakid
Thank you so much @impeeza, walked through the steps this weekend and have everything working perfectly on FW21.2.

At the end of the guide it did say "as you are getting a new set of binaries, you need new set of sigpatches" but I was able to use the sigpatches linked in this post without issue. Perhaps because I only used fusee from my build.
You are using v21.2.0 firmware and the sigpatch here is for this verison. That's why it works without any issue.
 
Last edited by johnliu,
  • Like
Reactions: protivakid

Site & Scene News

Popular threads in this forum