-
Notifications
You must be signed in to change notification settings - Fork 202
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
Feature Request - Select Backup RAM size #267
Comments
This should not be too much complicated, since all possible sizes (from 8KB to 512KB) are already emulated and it's just hard-coded to 512KB on startup. The only issue will be that changing the size will probably require to format existing RAM cart file since it's not possible to know used size. |
Formatting isn't a big deal, with the ability to make copies of various .brm files and shuffle saves to and from the internal ram file, although small, would allow for it to all be on the new one with a bit of patience. |
Since this issue was created, https://github.com/superctr has posted this tool: https://github.com/superctr/buram which can parse and create BRAM files. So changing the size doesn't need to require reformatting the BRAM file anymore. I have an implementation of resizing these files here: https://github.com/euan-forrester/save-file-converter/blob/main/frontend/src/util/SegaCd.js#L151 While this issue is being worked on, users in the meantime can resize their saves using: https://savefileconverter.com/#/sega-cd |
If it's not possible already, instead of automatically using 512kb (8192 blocks) for the backup ram cart, could it be selectable from 128kb and up?
My reasoning is that I use a Mega Everdrive X5 on my home consoles, which has 128kb backup ram. I'd love to be able to copy the .brm files back and forth from the official console to my Genesis Plus GX install on Switch.
As of right now the files can't be interchanged due to size difference. No tools that I've found can extract and write saves from a .brm file, otherwise that would be a solution.
The text was updated successfully, but these errors were encountered: