Skip to content
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

Pokemon Pinball (GBC) - Multiple save issues #726

Chariblaze opened this issue May 2, 2017 · 0 comments

Pokemon Pinball (GBC) - Multiple save issues #726

Chariblaze opened this issue May 2, 2017 · 0 comments


Copy link

@Chariblaze Chariblaze commented May 2, 2017

Build: 0.6-4509-87170f9
OS: Windows 10 64-bit

Expected behavior: Pokemon Pinball (GBC) has 8KiB of SRAM, so mGBA should use 8KiB for SRAM and create 8KiB .sav files. Saves store high scores, quick saves, Pokedex entries, and custom key configs. It should also be possible to import a save file from a cart or another emulator.

Actual behavior:

When the game is run - SRAM is correctly resized to 8 KiB
On the 4th-ish frame - SRAM is resized to 24KiB
When the title screen is shown - SRAM is resized to 32KiB
If the Red table is played - SRAM is resized to 48KiB

If the game is reset - Quick save data persists, custom key configs do not

If a 8 KiB .sav is imported from a cart or bgb - No save data is loaded

Tips for reproducing:

Once in a game, you can quick save on the Start menu. If quick save data is present and is working, you'll see a "New game/Continue" menu when starting a game.

Custom key configs are set in the options. By default all actions have one binding, so an easy way to test if the data is being preserved across resets is to bind two keys to an action.

Here is a good 8KiB .sav with high scores, quick save data, Pokedex entries, and custom key configs. You can press B on the title screen to bring up high scores. This .sav has a high score on the Blue table (press right): "5th WGW 136,210,700"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants