ROM Hack Diferent sizes for a same NSP

[javierjudgment]

Hi! Yesterday I downloaded a backup (I have the original game, but I want to play it in Emunand) of Hollow Knight (NSP) from N Downloader, but when I got into the download folder it only weighs 500 MB. In other websites is5 GB. How can there be so much difference?

I was able to start playing without problem, but I am afraid that in the middle of the game, it will be cut and stop working. This happens to me with all the backups that I downloaded from N downloader.

Thank you!

 

[ken28]

best guess is that you downlaoded just an update file not the whole game.

 

[shado9573]

Maybe that includes DLC + other updates as such?
Did you check weather the downloaded file was a zip file or was it a 5GB NSP?

 

[javierjudgment]

best guess is that you downlaoded just an update file not the whole game.

But why can I play with only a update? Its really strange. I really need a good a place to download fine backups...

--------------------- MERGED ---------------------------

Maybe that includes DLC + other updates as such?
Did you check weather the downloaded file was a zip file or was it a 5GB NSP?

Nope, i havent dowload the 5 gb version, cause im not in home now.

 

[shado9573]

But why can I play with only a update? Its really strange. I really need a good a place to download fine backups...

--------------------- MERGED ---------------------------


Nope, i havent dowload the 5 gb version, cause im not in home now.

Check the .(file extension).
If its an nsp then you can try downloading since it will likely contain game + updates

 

[DocKlokMan]

I have:
Hollow Knight [0100633007D48000][v0].nsp (3.6G)
Hollow Knight [0100633007D48800][v196608].nsp (2.3G)

So neither is 500MB. Unless you set it up special, your emuNAND and regular NAND will share the same Nintendo folder. You just need the application record in your emuNAND to see and access it. So perhaps you "installed" a partially downloaded NSP, got the application record and are now playing from the legit version you have?

 

[thaikhoa]

I have:
Hollow Knight [0100633007D48000][v0].nsp (3.6G)
Hollow Knight [0100633007D48800][v196608].nsp (2.3G)

So neither is 500MB. Unless you set it up special, your emuNAND and regular NAND will share the same Nintendo folder. You just need the application record in your emuNAND to see and access it. So perhaps you "installed" a partially downloaded NSP, got the application record and are now playing from the legit version you have?

To make it clear, SX Emunand uses Emutendo folder.

 

[DocKlokMan]

To make it clear, SX Emunand uses Emutendo folder.

It can, but I believe it only does that if it finds it on the SD card, otherwise it defaults to the Nintendo folder.

 

[javierjudgment]

I have:
Hollow Knight [0100633007D48000][v0].nsp (3.6G)
Hollow Knight [0100633007D48800][v196608].nsp (2.3G)

So neither is 500MB. Unless you set it up special, your emuNAND and regular NAND will share the same Nintendo folder. You just need the application record in your emuNAND to see and access it. So perhaps you "installed" a partially downloaded NSP, got the application record and are now playing from the legit version you have?

Its imposible cause my Hollow Knight is in another SD that i only use for OFW.

 

[Deleted User]

Check the md5 sum. Sounds like a dodgy file or incomplete download to me

 

[Morley]

I have a similar doubt. I download this game 4 times:
16 megabytes
Retro City Rampage DX [0100F17004156800].nsp

22 megabytes + 15 unpdate:
Retro City Rampage DX [0100F17004156000][v0].nsp + Retro City Rampage DX [0100F17004156800][v65536].nsp

391 (different extension file)
Retro City Rampage DX.xci

all work perfectly (I did not test them for more than 5min) but the difference in size is enormous and I tested one more with a file size of 1.8 GIGAS!!

 

[godreborn]

updates always end with 800 for content id. games always end with 000. dlc is random or I haven't figured it out yet.

--------------------- MERGED ---------------------------

btw, you can check the nsp with nsp verify though throws a false positive for nsps that have a different firmware requirement than they did originally. nsc builder will tell you if there are several parts to the nsp like updates or dlc. nsp verify can do it if you see it go over 100%, then starts at 0 again. it's reading each nsp inside the multi-nsp file.

 

[godreborn]

 

[masagrator]

updates always end with 800 for content id. games always end with 000. dlc is random or I haven't figured it out yet.

--------------------- MERGED ---------------------------

btw, you can check the nsp with nsp verify though throws a false positive for nsps that have a different firmware requirement than they did originally. nsc builder will tell you if there are several parts to the nsp like updates or dlc. nsp verify can do it if you see it go over 100%, then starts at 0 again. it's reading each nsp inside the multi-nsp file.

DLC is game titleid + 0x1000 + DLC ID (from 0x1 to 0xFFF).

I have a similar doubt. I download this game 4 times:
16 megabytes
Retro City Rampage DX [0100F17004156800].nsp

22 megabytes + 15 unpdate:
Retro City Rampage DX [0100F17004156000][v0].nsp + Retro City Rampage DX [0100F17004156800][v65536].nsp

391 (different extension file)
Retro City Rampage DX.xci

all work perfectly (I did not test them for more than 5min) but the difference in size is enormous and I tested one more with a file size of 1.8 GIGAS!!

Difference is because of how much data was dumped.

For game to be identified correctly and installed iirc you need only 3 files - 2 NCAs and cnmt. But dumpers can dump more files - instructions, legal notations, in case of updates - deltas, etc. That's why there are different sizes of NSP.

XCI can be done in two ways - by dumping image 1:1 which means xci will have exact size of cartridge from which was dumped (if cartridge was 2GB, you will get slightly below 2GB image) OR by dumping image and cutting dummy data that contains nothing and thus getting real size. You can instantly cut dummy data with XCI Explorer.
Plus there is a issue of update partition which contains FW. Cutting it releases additional few hundreds megabytes from XCI (which with cutting dummy data is when you will get size similar to NSP).