TASEmulators / TASEmulators/BizHawk

Feature / ApiHawk tool request: SaveRAM importer/exporter for other emulators

Open
#1,659 15 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Ext. tool: Future tool Request: File format support
Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

Here's a list of all the formats that have been requested to date. --yoshi

ext system emu
.brm Sega CD ?
.fla N64 OpenEmu
.gme PSX ?

Also #3142 for NDS.

re: .gme, drop first 3904 octets leaving 131072, that's the mem card

Problem w/ Mupen (N64) may be solved? https://github.com/TASEmulators/BizHawk/issues/3122#issuecomment-1236213602

Prior art (JS targeting browser): https://github.com/euan-forrester/save-file-converter

Original request follows.


Could anyone add a way to read or to convert Sega CD .brm files from other emulators into the format Bizhawk uses?

.brm sizes are 8KB, 16KB, 32KB, and 64KB, but Bizhawk's SaveRAM is 24KB and I haven't found a way to be able to convert it, or to even reduce the KB size to see if that way it would "match" with the .brm sizes. Renaming them like how I could do with Saturn or Playstation save files doesn't work here.

So hopefully someone is able to add this option in the future.

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating BizHawk's existing SaveRAM import/export entry point and compare its format handling with the .brm sizes and the .gme rule described here. Done means the requested emulator save formats can be read or converted, with related context reviewed in #3122 and #3142.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.