(07-26-2013, 09:24 AM)nightflyer Wrote:The reason is for games using multiple file names in SAVEDATA_FILE_LIST: when only one file is updated, the SAVEDATA_FILE_LIST is created and this one file name is stored in PARAM.SFO. But the other files are not necessarily being updated and thus not stored in SAVEDATA_FILE_LIST. In such a situation, we have a mix inside one savadata directory: the updated files can be handled according to SAVEDATA_FILE_LIST but the other files have to be handled the old way.(07-26-2013, 06:34 AM)gid15 Wrote:(07-25-2013, 09:37 PM)sum2012 Wrote: r3325Jpcsp is using the date of the savedata file to find out if this is a pre-r3306 file or not:
Log 1 use r3304 save - fail
Log 2 use r3325 save - Sucess
edit:add r3304 save log
#3 only load log
- if date of savedata file < 2013-07-12: file is interpreted as pre-r3306
- if date of savedata file >= 2013-07-12: file is interpreted as r3306 or later
This should work for normal users, but will not work if you specifically do tests now with r3304: e.g. create savedata now with r3304 and try to import them with r3325, they will be interpreted with the new format because their creation date was after Jul 12.
Wouldn't it be easier to check if there is a value for saveFileSecureEntriesAddr if there is no SAVEDATA_FILE_LIST? Because if there is, we know it must be a savefile from an old revision right?
Anyway, I tried r3326 and loading worked so far, so good work and thanks.
I hope to get rid of this compatibility option in a few months... when nobody tries to read old savedata anymore.
Always include a complete log file at INFO level in your reports. Thanks! How to post a log