-
Notifications
You must be signed in to change notification settings - Fork 14
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
Overwrites SRMs made by SNES9x+Mesen S as blank, but will keep and load SRMs made by itself #18
Comments
I believe this is almost certainly related to another issue that I had opened back in the day in the repository that was previously used for the bsnes core. See here: libretro/bsnes#41 The various implementations of bsnes do not seem to fully support right now the libretro API used for SRAM access, which leads to saves being overwritten if savefile compression is active in the frontend. To prevent this annoyance, do the following:
After disabling SaveRAM compression you should be able to switch between all SNES/SFC cores and still retain your saves without any overlap. I tested it on my Windows 11 system a few minutes ago with all the latest nightlies and everything seems to be functioning as intended with this workaround. |
Thanks for the workaround. Confirmed that it works that way. Hopefully SRAM compression support will be patched in later, but it's nice to be able to use the core in the meantime. |
As written in the problem statement, BSNES 115 + HD will overwrite an SRM initially created by the current SNES9x and Mesen-S cores. Using a 9/25 nightly of Retroarch in Win10. Does it with every game, but the latest test was quickly creating a file in DKC3 in SNES9x or Mesen-S, then loading it in BSNES. The 0% file I created is not there, all 3 slots are completely blank, and will be blank when I return to the other cores. Saves will work if I keep using BSNES-created SRMs in BSNES, and other cores will load them, but as soon as I flip back to BSNES they will be overwritten as clear again. Thanks in advance.
Of note, the Mercury cores based on older BSNES builds do not exhibit this issue.
The text was updated successfully, but these errors were encountered: