this post was submitted on 17 Mar 2024
38 points (95.2% liked)
RetroGaming
19617 readers
345 users here now
Vintage gaming community.
Rules:
- Be kind.
- No spam or soliciting for money.
- No racism or other bigotry allowed.
- Obviously nothing illegal.
If you see these please report them.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
IIRC most emulators use .sav. You should be able to just drop it in the rom folder for most emulators.
Does this one work? https://github.com/skylersaleh/SkyEmu
yeah the .sav's are generally all the same because they're just almost always just a binary dump of RAM contents.
From 11+ years ago? I'll give it a shot here tomorrow.
Hey, you're playing a game from almost 30 years ago!
The data is actually exactly the same as what would be on a cartridge. The same way you can use a .gb file from the 90s, you can use a .sav file from the 90s too. Emulators were made to read those original files, not the other way around. Every GB emulator should have no problem reading those files.
Now save states is where you'll run into trouble. Those are unique to the emulators, since the consoles never had them, meaning each emulator had to create them from scratch. You might find some cross compatibility, but generally not, I'd think.
This should generally be true for most emulators. And for most consoles themselves, actually -- you could run most ROMs from a console and even .sav files between emulators and consoles! (e.g., with an EverDrive)
This is awesome.
yes, even 11 years ago. it is dumping the ram state of the emulated processor and game state not of the emulator on it's host system. There may be different header data or something that could cause problems but realistically all .sav's really should be the same.
Thanks!!! It worked.
hell yeah! enjoy your game :)
OMG you are all wonderful people. It worked!!!