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
Bug Report
GodMode9's built-in GBA VC save-dump function is now consistently creating outdated files when it was working correctly an hour before. Dumping saves via GBAVCSM produces files that are up to date and makes subsequent GM9 built-in dumps start outputting those instead. The result is the same regardless of whether one deletes any saves already on the micro SD before dumping or simply overwrites.
No firmware or software updates were conducted within the one-hour time span — I spent that time playing Pokémon Emerald and using GM9 to back up my save. I ran into the issue on self-made VC injections of Pokémon Emerald and Pokémon Ruby, with the bug initially spotted on the former, then verified to also be affecting the latter.
Steps to reproduce:
Turn on console, boot Emerald or Ruby, close it, then turn off the console;
Hold Start on boot to enter GM9, then head to S: > agbsave.bin > AGBSAVE options... > Dump GBA VC save. Save file is successfully dumped to \gm9\out;
Reboot, launch FTPD, and copy the save file over to the PC;
When loaded in PKHeX or mGBA, the save is functional but out of date, as verified by checking playtime and party/box contents;
Turn off FTPD and the console;
Boot back into GM9, run the GBAVCSM script, and use it to dump the save of the game that was previously booted. The resulting file is up to date and makes GM9's usual dump method now produce that same save. Doing a GBAVCSM dump of all saves at once also works and makes GM9's dump catch up, with the save output from GM9 depending on the GBA game that was most-recently booted.
My troubleshooting process:
Deleted any backups already on my micro SD before dumping again;
Replaced GodMode9.firm (and all folders in \gm9\out) with a fresh copy of the same version;
Confirmed that VC Emerald and Ruby still saved and loaded correctly and that their saves were properly loaded on my PC via PKHeX/emulation;
Suspecting the issue was somehow cache-related but finding no solution within GM9, I happened across GBAVCSM, which I set up and got to produce the correct saves;
Went through all possibly-related open and closed issues on GitHub;
Manually updated Luma3DS to v13.0.2 after the problem began (was previously on v12.0.1);
Double-checked my micro SD's condition as requested by the bug-report template.
System
Console: O3DS XL
System version: 11.16.0-49E
boot9strap
Luma3DS: v13.0.2
GodMode9: v2.1.1
Did you chainload GodMode9 via Luma? Yes. Also, GodMode9.firm is the only file in \luma\payloads.
Micro SD
FAT32, 64GB micro SD in an SD adapter
chkdsk /f reported no errors
No prior issues with it
No backup card I can test with
I've annexed a zip containing two save files for each game — one pre-issue, one post-issue — on the slim chance they might be useful.
Thank you for your time.
Have you actually read this?
[X] I have read the information above
The text was updated successfully, but these errors were encountered:
Bug Report
GodMode9's built-in GBA VC save-dump function is now consistently creating outdated files when it was working correctly an hour before. Dumping saves via GBAVCSM produces files that are up to date and makes subsequent GM9 built-in dumps start outputting those instead. The result is the same regardless of whether one deletes any saves already on the micro SD before dumping or simply overwrites.
No firmware or software updates were conducted within the one-hour time span — I spent that time playing Pokémon Emerald and using GM9 to back up my save. I ran into the issue on self-made VC injections of Pokémon Emerald and Pokémon Ruby, with the bug initially spotted on the former, then verified to also be affecting the latter.
Steps to reproduce:
My troubleshooting process:
System
Micro SD
I've annexed a zip containing two save files for each game — one pre-issue, one post-issue — on the slim chance they might be useful.
Thank you for your time.
Have you actually read this?
[X] I have read the information above
The text was updated successfully, but these errors were encountered: