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

[Data Loss] [RetroArch] Roms for separate cores with same names cause overwriting #1341

Open
4 tasks done
Aepoh opened this issue Nov 7, 2024 · 0 comments
Open
4 tasks done
Labels
bug Something isn't working

Comments

@Aepoh
Copy link

Aepoh commented Nov 7, 2024

Prerequisite Steps

  • I have searched existing issues
  • This issue is not a duplicate of an existing one
  • I have checked the EmuDeck Wiki
  • I have read the Troubleshooting Page on the EmuDeck Wiki

What distro are you running?

SteamOS

Which SteamOS Branch are you using?

Beta

What happened?

Experienced with Mario Tennis (64 & GBC) and Mario Golf (64 & GBC).
Mario Tennis has 2 versions, one for N64 and for GBC but both are called Mario Tennis and both store their save files and savestates in the same location. When starting up Mario Tennis (GBC) after Mario Tennis (64) the data from 64 will be overwritten with a new save from GBC. Loading the two games back to back will cause both saves to get wiped.
This is why you don’t put save data and savestates from different cores in one big pile. Over on the RetroArch depot I was told this is not default behavior for RetroArch.

I have resolved this myself by renaming the roms and re-adding them with SRM, but many people are likely to get caught out by this and potentially lose a lot of data.

Relevant log output

No response

@Aepoh Aepoh added the bug Something isn't working label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant