I guess? You can always build your own provided you have the access to the source code.Everyone is making his own release ?!
I guess? You can always build your own provided you have the access to the source code.
I'd say that both sources can be trusted, despite the fact that the files are slightly different. Official repo is gone now, but the community is working behind the scenes to bring us the working versions.
I mean, your repo were dmca'd. Can't you update this and upload the updated version here or on a page like github hosted in the eu for example? Or have you been forbidden to continue working on this tool?correct
What changed tho, did you stop trusting them for some reason (if you were downloading from there before)? Or were you always getting releases from GitHub? If so, everything's fine with that website and with releases from this community as well.
Maybe it's the fw then ? I'm on 17.0.1, with ams 1.6.2
If it's not that then I really have no clue but yeah, knowing a little bit about how that works would be interesting
Honestly, no. Nothing worth of using 18 yet.Im on ofw 17.0.1 and 16.1.0 ams 1.6.2, should i join the "cat dog update my console" to 18.0.0?
@impeeza i got to ask, the sys-patch 1.5.1 posted above has been updated by @TotalJustice ? or by yourself ?
Sorry to bother with that but i have OCD on this and the official repo is now gone for good... and i'm not sure anymore where to get the OG source and info...this triggers my OCD big time
IPS patch creator and LockPick are still easy to find, for now...
Could you or someone here DM me the "not so usual place" you're reffering to ?
The modified code was around in some discussion channels so anybody could build itThree cats site
View attachment 428666
Yandex @impeeza
View attachment 428667
Now my OCD is off the limit, sizes and CRC32 are not the same
Everyone is making his own release ?!
Neither, a week know developer of the scene shared the modified code whit me and I shared with you.Impeeza made his own, they made their own, I made my own. So yes
No.I mean, your repo were dmca'd. Can't you update this and upload the updated version here or on a page like github hosted in the eu for example? Or have you been forbidden to continue working on this tool?
The log file is still there, that's why it's green, even after you deleted the system moduleThat is possible. I'm on 18 and 1.7.0.
Edit: So that's not it. I downgraded my emuMMC to 17.0.1 and ams to 1.6.2. Same thin. All are orange except ctest is still green. I get that it doesn't matter, but it's driving me nuts not knowing why both yours and Blythe93's ctest is orange and mine is green.
Like I said previously, I even tried removing sys-patch and my ctest was STILL green. How is that? Green means it's patched by sys-patch. How can that be if I deleted it? Anyone have any explanation for that, and also why the same set of sigpatches aren't patching my ctest but they do for others? Something has to be causing it and I know it doesn't matter but I still want to know why and/or what is causing mine to behave differently.
No.
The log file is still there, that's why it's green, even after you deleted the system module
Sometimes even the same code at the exactly same environment create different binaries because the timestamp of building is included in the binariesThe size and checksum differences are because of build environment differences. The version of libnx you use, the devkitA64 version, the operating system ect. It can all influence the build process enough to change the outcome. If you don't trust the builds in the wild you will have to build yourself.
Sometimes even the same code at the exactly same environment create different binaries because the timestamp of building is included in the binaries
you can play online without upgrade the firmware.Except you play online
Then you inevitably lock yourself out. You don't have to update immediately. But sooner or later you will have to update because otherwise you won't be able to access the eShop or play against others online.you can play online without upgrade the firmware.
in some many moons, yeah may be. but TODAY nop.Then you inevitably lock yourself out. You don't have to update immediately. But sooner or later you will have to update because otherwise you won't be able to access the eShop or play against others online.
See you a week after the firmware release@
in some many moons, yeah may be. but TODAY nop.