You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed yesterday in the libretro Discord server, it appears that this core in its current form is incompatible with the "SaveRAM Compression" functionality as implemented in RetroArch. This leads to an overwrite of the savefile upon launching any content, since the core does not recognize the .srm file in its compressed form.
Here's how to reproduce the issue:
Set "SaveRAM Compression" under Settings -> Saving in RetroArch to ON.
Load up any other SNES cores available (snes9x, Mesen-S, bsnes-mercury, etc.), then run any piece of content and save some progress, so that the change to the save is clearly identifiable (for instance in the file list after the title screen).
Now load this core or any of its variants available (for instance bsnes-hd beta), then run the same content previously used with the same .srm savefile. Any previously saved progress in the savefile will be gone.
The text was updated successfully, but these errors were encountered:
because this core do not support libretro api's retro_get_memory_data/size for sram/system ram access, the internal save function should not be using .srm as that file extension as that is reserved for libretro use... also RA should have sort savestates/saverams by folder/core names as default to avoid other core overriding another cores save file, just incase for some they are incompatible or in rare cases something like this
As discussed yesterday in the libretro Discord server, it appears that this core in its current form is incompatible with the "SaveRAM Compression" functionality as implemented in RetroArch. This leads to an overwrite of the savefile upon launching any content, since the core does not recognize the .srm file in its compressed form.
Here's how to reproduce the issue:
The text was updated successfully, but these errors were encountered: