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
Describe the bug
mGBA appends several bytes to the end of the Pokemon Emerald save, probably for the RTC (as I could not replicate this issue with LeafGreen which does not have a ).
To Reproduce
Steps to reproduce the behavior:
Copy save file last modified/created by mGBA to SD card.
Open save file in pkmn-chest
See error
Expected behavior
Save file will load as normal.
Screenshots
If applicable, add screenshots to help explain your problem.
Console (please complete the following information):
DS/DSi/3DS using a Flashcard
DSi (Using SD card)
3DS (Using SD card)
Version [v2.2]
Additional context
Save file will run just fine in mGBA and GBArunner2. Also works in pkhex. Will also work in pkmn-chest after removing the added bytes at the end of the file (after the string of FF FF FF FF...).
The text was updated successfully, but these errors were encountered:
mGBA appends the rtc to the end of the save file as you stated. This makes the file larger than most save managers are expecting, so it won't load. To fix that, open the save in a hex editor on your computer, delete the last line, and then save it. In mGBA settings you can also disable RTC for games so this does not continue to happen.
Describe the bug
mGBA appends several bytes to the end of the Pokemon Emerald save, probably for the RTC (as I could not replicate this issue with LeafGreen which does not have a ).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Save file will load as normal.
Screenshots
If applicable, add screenshots to help explain your problem.
Console (please complete the following information):
Additional context
Save file will run just fine in mGBA and GBArunner2. Also works in pkhex. Will also work in pkmn-chest after removing the added bytes at the end of the file (after the string of FF FF FF FF...).
The text was updated successfully, but these errors were encountered: