For some reason the title IDs do not match (01002F3010AF4000 vs. 0100630010252800), which causes the update to not be applied correctly. It should be possible to extract the base, correct the title ID to 0100630010252000, and repack it, or just create a merged .nsp, but that is outside the scope of this post.
Thanks for the game, update & explanation
I'll look around to see if I can do the former (matching title IDs); the latter is outside the scope of my abilities for sure!
Thanks again.
TL;DR: Download the main game NSP from the first spoiler below and use it with SuperEpic_The_Entertainment_War_Update_v1.1_NSW-VENOM. The other two options are primarily educational.
I wanted to take a closer look at this sooner but have been rather busy so please excuse the late reply.
Needless to say that the scene update should have been nuked because it is not usable with the base release, which VENOM somehow failed to notice. So much for my confidence in nukenets. It's been three years and three months since 2020-10-27.
Coincidentally you have three options:
This NSP was sourced from P2P, but the signed hashes match so it should be safe. Compability with the scene update was confirmed.
if you already have both scene releases and don't want to get/archive the P2P dump, but be aware that it is a somewhat more involved process.
Despite almost all relevant files being identical between the "wrong" scene XCI and the compatible P2P base NSP, simply changing the title ID of SuperEpic_The_Entertainment_War_NSW-VENOM isn't enough to make it work, because the main data archive ("data.unity3d") differs between the two dumps due to four slightly changed files inside of it, which unfortunately prevents applying the update as that requires the correct RomFS. Luckily a relatively small patch from the scene archive to the P2P one can be used to recreate an identical RomFS thus enabling successful updating.
See the commented scripts for further patches.
, which results in the NSP being unusable due to Rights ID issues.
Because he did not provide a new release, and I totally didn't waste time on debugging and working around these issues myself before finding the fork, here is a quick and dirty hack for the
).
2a. For the x32 binary (CRC32: D22C8F28) replace 0x69 with 0x78 at offsets 0x2DFF8 and 0x2E047.
2b. For the x64 binary (CRC32: 0E9ABC82) replace 0x69 with 0x78 at offsets 0x2BC17 and 0x2BC64.
3. Save the file.
The remaining bugs (e.g. PFS0 header padding issues) will change the resulting NCAs, but can be ignored as this is purely cosmetic and has no effect on playing the game since NACP, ExeFS and RomFS contents are identical. Because it's not at all worth it to bother injecting the fixing patches into the existing binary just to make the NSPs identical for no good reason, there are "-alt" versions of both scripts included for use with hacPack v1.36-r2 plus the above hex patches.
Otherwise just build from source, which is easy enough even on Windows, so I'm not sure what SciresM
You can do so with the second script provided in the above option.
This is most useful for playing on hardware as both transfer and installation time are decreased:
Code:
2.25 GiB - scene base XCI + update NSP (does not even work)
0.85 GiB - P2P base NSP + scene update NSP
0.85 GiB - scene base XCI repacked as NSP + scene update NSP
0.49 GiB - scene base XCI + update NSP merged to single NSP
Be advised that this merged NSP will fail to launch in Yuzu if the regular update is also installed (on hardware it works fine). Either don't install the latter in the first place or remove it with one of the following methods for Yuzu:
- Open the game's properties menu by right-clicking on SuperEpic in the game list, then selecting Properties.
- Uncheck the update in the Add-Ons tab.
- Click OK.
If you are using the mainline Linux AppImage execute this in a terminal window:
Use the below commands on Windows, but replace "%AppData%\yuzu" with the emulator's installation directory if you are using the portable mode:
Code:
set "root=%AppData%\yuzu\user\nand\user\Contents\registered"
del "%root%\00000022\f61f8c3dfee82ba62f3c8461dcadadf0.nca"
del "%root%\0000007E\fa651920a8b809a3df8b7cd1a590c344.nca"
del "%root%\000000CF\62727c52b2534d4b1d63b4580557efd9.nca"
del "%root%\000000D8\fef32fca188609626fa0bed899994690.nca"
These custom NSPs will fail signature checks for obvious reasons but they have been tested successfully (Yuzu/hardware) and the generating scripts are provided for transparency.
For comparison here are the hashes of all five NSPs:
Code:
db3fcf696e1ce1dd665a1e7f4f2fb15d4bb0266c9ea9f24d181f731079efdaa2 *SuperEpic - The Entertainment War [0100630010252000][v0].nsp
b130d690f2cb706a30d935a84d4158b80d925586471dc05afab1bc29605c931a *SuperEpic - The Entertainment War [0100630010252000][v0][repacked].nsp
ba24f72f5c2ed08e949861774b8d237dcf2cd1de53ef733295a1308f46a67918 *SuperEpic - The Entertainment War [0100630010252000][v0][repacked-alt].nsp
d56d32464a13c75ed4483041114ee88d7c29e39b3ea492afae3fbc9f034306b1 *SuperEpic - The Entertainment War [0100630010252000][v65536][merged].nsp
b45ea58431ed28493e9ea97e95f4d16ebde06e91e505c60a18579195181d6209 *SuperEpic - The Entertainment War [0100630010252000][v65536][merged-alt].nsp
Wow, this is mind-blowing. I can't thank you enough for the lengths you go to not only share, but to educate. Great kudos to you (again, a *clap hands* Like option would be appropriate).
I'll look into Options 2 and 3 to try and replicate your custom NSPs It will take me some time to understand for sure but I'm really happy to learn!! Thank you!! 👏