#HOW TO LOAD SAVE FILES ON PROJECT 64 WINDOWS#

Especially Zelda Majora's Mask, what with owl statues not being supported and File 3 being deleted upon adding them to USA/PAL.Д«ut otherwise you can pretty much always count on renaming the save file to get it to load in other game regions. One exception is commonly the Japanese versions of games, since the save file format is more likely to change due to storing names and text with added support for the kana character sets (which the English and PAL versions usually like to delete). It seems to work quite often more than you seem to expect.ДЄlmost every game that I've reversed the save chip/mempak formats for-or even just transferring the save to test on features in a different region of the game-has worked just fine. One could implement flexibility to all of those things by having support for dynamic save file names.

#HOW TO LOAD SAVE FILES ON PROJECT 64 WINDOWS#

Do I want to have a unique save file for every single hacked or good version of the game and have to go through the trouble of copying, pasting and renaming to duplicate file names in Windows Explorer every time I want to test out my saved progress on an alternate version of the ROM?.

Do I want my save file to be universal to non-modded and non-hacked ROMs with different CRCs?.

Do I want my save file to be universal to all USA versions of the ROM (v1.0, v1.1 etc.) but not PAL?.Do I want my save file to be universal to all ROM versions (at the risk of save structure breakage)?.I wouldn't bother with GoodN64 'friendly' names honestly. For DK64, it's NDOE, and on both Zelda's it's NZSE.ДЄnd, there is a 5th byte after that, at header, indicating part of the mask ROM version, which GoodN64 inaccurately uses as 'V1.0', etc. Also, On some ROMS (at least for Zelda: Majora's Mask (both the original and the one inside the GC Collector's Edition GCM/ISO) and DK64), there appears to be a 4 character identifier at 0x3B.

How to load save files on project 64