Wii Wadpacker hex limitation?
- This topic is empty.
-
AuthorPosts
-
January 9, 2015 at 1:37 am #391557
Just a quick question. Does the wadpacker have a limit as far as how high it can go filename-wise before it can’t handle any more?
The reason I’m asking is because as I’ve been adding a lot of custom songs, I’ve now gotten up to folder numbers
500_000001F4
501_000001F5
which are used to generate 000001F4.app and 0000001F5.app
Then wadpacker seems to run into a problem when trying to pack 000001F5.app
“Packing 00000026.app … done.
Packing 000001f4.app … patching SHA1… filesize… done.
Packing 00010001.app … patching SHA1… filesize…”
It seems to look for a 00010001.app file for some reason, then either says it can’t find the file (obviously) OR it simply crashes. Just wondering if this is a limitation I have reached for folder numbers, or if there is something else wrong?
Thanks for any input on this.
January 9, 2015 at 3:36 am #435867Could have put this in the Wii thread, but here’s the answer.
You reached the limit for that content generation. Your next safe bet would be to start putting customs in another folder, preferably in sZME. You can PM me if you’d like to do that. Otherwise, you can try to pack as many songs into one archive as you can. Most of the customs you get should allow for 2 or 3 songs in one.
January 9, 2015 at 5:42 am #435876Thank you, I am trying out the packing as many songs into a slot as I can method. Basically I’m restarting from scratch (deleted all of my custom songs from my SD card and starting back at 052_0000034 with a few songs in it, just to test if it works).
But now I have a different problem, and I’m hoping there is a quick work around. I am clearing the wii cache beforehand, so I assumed that would eliminate this problem, but apparently it isn’t.
When I start RB3, it checks the SD card, then says “There is add-on content in the Wii System Memory that must be moved to the SD card”. It then attempts to do that, and fails (understandably since I blew away everything to start fresh). It then disables SD card mode.
Is there a trick to clearing whatever data is in the memory so it will simply do a full refresh of the DLC content as it normally would after a cache reset?
January 9, 2015 at 5:49 am #435877Check the title/00010005/735a4645 folder on your Wii. You can do this with WiiXplorer or FTPii more easily. Inside the content folder, there should only be 1 app file, or less than that. Any more, and the game might be trying to move that data, but I don’t know why it would erase everything else on your card. This is one thing worth checking out first.
January 9, 2015 at 5:58 am #435879Hmm. Using FSToolbox, I can get to title/00010005/ but I don’t have a 735a4645. Most of mine are 77… something, and one is 72..
Slight update, using WiiXplorer now, and same thing. Much nicer to use though ” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />
January 9, 2015 at 8:08 am #435882Problem has been resolved. Copied all of the old customs back in temporarily to get passed the memory card load, then cleared them all and put in the fresh multi-pak custom files, and it worked like a charm
January 9, 2015 at 4:25 pm #435900Okay. Hopefully everything works fine on your end then.
Edit: Wait, I’ve figured out how to make 3 new content generations. Watch the Wii thread for more on this.
-
AuthorPosts
- You must be logged in to reply to this topic.