So yes, it's as good as nicoboss's tool in compressing to XCZ-files?Yes, select 8 in the mainmenu.
hi. I am sorry to bother you. Is the file limit still 32gb? Is there any chance of increasing this? I hope you are well. Be safe.
The reason you can't have XCI files bigger than 32GB is nothing to do with NSCBuilder or SX OS, it's that the real retail cartridge would need to be a 64GB cartridge and those don't exist yet, Nintendo haven't made any. So the Switch won't allow an XCI that's essentially emulating a 64GB cartridge.
I am going to have to try this compression with MK11 when I get a chance.
That sucks, is it possible to install the base game to nand, and make an XCI of just the update + dlcs for external hard drive? Or does the external hard drive have to have the base game? I don't have 25 gb to install the update to nand.
I know already that it isn't working. I'm asking for help to make it work.Did you look in output folder? If it's not there it isn't working.
File "squirrel.py", line 2789, in <module>
File "lib\decompressor.py", line 101, in decompress_nsz
File "Fs\Nsp.py", line 9775, in decompress_direct
File "Fs\Nsp.py", line 9575, in get_data_from_cnmt
UnboundLocalError: local variable 'titleid' referenced before assignment
[17728] Failed to execute script squirrel
...................................................
STILL 0 FILES TO PROCESS
...................................................
---------------------------------------------------
*********** ALL FILES WERE PROCESSED! *************
---------------------------------------------------
The problem with nscbuilder that many people here are experiencing (sxos reading / install errors) is being caused by @DarkMatterCore NXDumptool. I and @DarkMatterCore working it out and soon release an update we have an idea what it is..
in the meantime, a workaround is to used hactool to unpack a dumped nsp and repack it again to nsp. then use the repacked nsps files to combine with nscbuilder to a xci/nsp file
hactool instructions
hactoolnet -t pfs0 [nsp file] --outdir [unpacked nsp dir]
Go into the unpacked NSP dir and delete all XMLs and JGPs
hactoolnet -t pfsbuild [unpacked nsp dir] --outfile [new nsp file]
if you have sxos you can just use sxdumper and it should be fine
It's not being caused by nxdumptool at all... The code changes from the custom build I'm preparing won't be part of the public repository - they break the reproduction of the AuthoringTool format I'm trying to maintain.
The fact that a simple repack fixes this issue is what makes me think NSC_Builder does something differently when dealing with nxdumptool NSPs. Other tools and programs work fine with these dumps.
I'm willing to release a custom build with the necessary changes to make NSC_Builder XCI generation work properly, but I won't be maintaining it. This will only be temporary.
@JRoad I tried commenting out all XML/JPG generation and added PFS0 header aligning to a 0x20-byte boundary, just to see if it made any difference, but the generated XCIs using these new NSP dumps were still failing (even though their size is an exact match of the repacks created by hactoolnet).
I suspect file order detection/handling is at fault here. NCAs, ticket and cert are all identical to the ones from SXDumper NSPs, only the file order is different.
nxdumptool saves NCAs first (same order from the CNMT), then the CNMT NCA, then the ticket and finally the cert.
Please take a look at the currently opened issue if you wish to know more about our findings: https://github.com/DarkMatterCore/nxdumptool/issues/59.
Hi.
Can anyone advise on why some of my NSPs compress fine while others compress to 1KB. Seems like all files belonging to certain games (DLC, UPDATE, BASE) get output as 1KB. I read through this thread as best I could but did not find a solution to this. I did try adding the master_key_010 line as suggested for other issues, but this didn't have any impact on my issue.
Any advise is appreciated. Thanks!
HI. Not sure what you mean. This is the first time I'm using this app. I used option 8, dragged an entire folder of nsp files into it and it successfully processed most of the files, but some just defaulted to 1kb. I went ahead and manually dragged a few of the original nsp files that did this and it always resulted in the same 1kb files.are you mistakenly grabbing the files in batchprocess folder in nxdumptool/nsp/