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

Request: ability to disable appending RTC data to save file #3303

Open
apbeckman opened this issue Sep 29, 2024 · 2 comments
Open

Request: ability to disable appending RTC data to save file #3303

apbeckman opened this issue Sep 29, 2024 · 2 comments
Labels
feature:usability UX issues due to unclear UI severity:nice to have Low priority feature requests

Comments

@apbeckman
Copy link

This consistently causes problems with the portability of save files in Pokémon games, as well as compatibility with save editors such as pkmn-chest — which displays an error message saying the file is invalid once an in-game save has been performed using mGBA. This can be fixed by opening the file in a hex editor and deleting the last 16 bytes,though it'd be more convenient to just not write them to begin with

@profi200
Copy link

The data is needed to keep the RTC in sync and working the same way it would on a real gamecart. Open an issue on these tools that think a save with RTC footer is invalid.

@endrift
Copy link
Member

endrift commented Sep 29, 2024

Specifically, that data is the data that is stored on the RTC itself along with a bit of synchronization data so that it can be moved between systems without the clock becoming wrong. This includes to and from cartridges, where the clock would be flat wrong without it.

FlashGBX for example knows how to read/write this data for cartridges, and editors like PKHeX have already added support for this footer too.

@RetroEdit RetroEdit added feature:usability UX issues due to unclear UI severity:nice to have Low priority feature requests labels Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature:usability UX issues due to unclear UI severity:nice to have Low priority feature requests
Projects
None yet
Development

No branches or pull requests

4 participants