Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Same name/different case save files causing backup issues. #24

Closed
DakuTree opened this issue Sep 15, 2015 · 6 comments
Closed

Same name/different case save files causing backup issues. #24

DakuTree opened this issue Sep 15, 2015 · 6 comments

Comments

@DakuTree
Copy link

Had two profiles on Timesplitters 2 with the same name, different case (DAKU & Daku (This being the newer one)).
On the backup menu, the filenames of both of these are different (4F-GTSE-DAKU.son & 4F-GTSE-Daku.son), but they return the same data. (Everything is the same as the oldest profile)
Doing a mass-backup caused the oldest profile to be backed up twice, and the newer one doesn't appear to be backed up at all.
Sadly found this all out after reformatting my card 😢, meaning the newer save was lost.

I'm assuming this bug will also exist in any other game with multiple named profiles (Timesplitters 3 is the only one that comes to mind...).

@Antidote
Copy link

Looks like filenames aren't case insensitive, easy fix.

@Antidote
Copy link

Alright, try the change I just made in card.c for GCMM and see if that solves the problem:
devkitPro/libogc#7

@DakuTree
Copy link
Author

That seems to have fixed the issue. Thanks.

@Antidote
Copy link

No problem :D

@suloku
Copy link
Owner

suloku commented Feb 25, 2016

I can't believe I wasn't subscribed to gcmm git notifications, I will update as soon as I can. Thank you very much for noticing + fix.

@Antidote
Copy link

You're welcome!

@suloku suloku closed this as completed in 75a5e02 Feb 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants