Closed ohyocbz closed 1 year ago
@ohyocbz - thanks for the bg report! Can you try this test build? GodMode9_794.zip
@ohyocbz - thanks for the bg report! Can you try this test build? GodMode9_794.zip
Hello! Sorry for the long wait and reply. I was also busy irl so it took me quite some time to check this out on my own at night. Here's what happened so far:
The "129kb" save file inject that I uploaded here before was finally working and could play perfectly 😄
I also did backup the new save to the gm9/out folder and I was surprised that the file size went back to 128kb or its usual bytes size
I tried to play it on my computer using mGBA emu to continue and save once again and I find it very odd on why the save file size went back to 129kb (I read somewhere that it was for RTC data or sumn so I should probably ignore it when that happens)
So I use this new 129kb save file, put it on my sd card and boot the payload until this message appeared out of the blue:
i got nervous and thought my sd card got corrupted but im glad my OS repaired it and found no errors. Before I was about to replace the GodMode9.firm from winrar, is it normal for a debug payload firm's file size to be larger after a single use?
I replaced it and boot up godmode9 and inject the new incorrect size save file and it works like a charm and was indeed playable
Thank you so much for your time and effort on fixing this 🙇🏻♀️
Thanks a lot to you for testing this as thorough as you did. You're right, the additional 1kb is some emulator specific RTC data. I've got no way of keeping this data or even restore / use it. Also, no need to worry about it, as you see, mGBA just rebuilds the data when you import the save back.
As for the error and the GodMode9.firm
size - I'm at a loss here. Something weird happened to cause this. Maybe you did mix up GodMode9 firms? The file itself should not change size when running.
Thanks a lot to you for testing this as thorough as you did. You're right, the additional 1kb is some emulator specific RTC data. I've got no way of keeping this data or even restore / use it. Also, no need to worry about it, as you see, mGBA just rebuilds the data when you import the save back.
So I'll have to use this test build payload you gave me for the mean time when injecting or dumping my saves with RTC
As for the error and the
GodMode9.firm
size - I'm at a loss here. Something weird happened to cause this. Maybe you did mix up GodMode9 firms? The file itself should not change size when running.
I think I did mixed up without noticing while transferring, I'll just have to be careful from now on
So you want to report a bug? Hold on, there are ways you could make things easier for us:
Give a clear description of the bug (what happened?). An error "Savegame inject failed!" occured when trying to inject a GBA save file from my microSD card, only to find out that my save file size was ~129 KB (131,088 bytes size mentioned on File Explorer; 135,168 bytes size on disk) instead of exactly 128 KB (131,072 bytes)
Give us clear steps to reproduce (when/how did it happen?). Copied the GBA raw format save file from my Windows computer --> Pasted it to the root of my 128 GB microSD card --> Booted my 3DS via GodMode9 --> Pressed L to mark it and Y to copy the save file to the clipboard --> Went to S: SysNAND Virtual and select "agbsave.bin" --> AGBSAVE options --> Inject GBA VC save
Give us info about your system (where did it happen?). In SysNAND Virtual agbsave.bin injecting GBA VC save
A photograph or even a short video of the bug happening is always helpful!
Some additional attachments including the save file:
20221106_BugReport.zip
Info about your system Include this info to make our work easier:
Console type (O3DS/N3DS) N3DS
Anything special about your console? (defects, custom modifications,...) None
Bootloader (boot9strap/fastboot3ds) boot9strap
Did you chainload GodMode9 via Luma? Yes
Helpful hint: if you followed the Guide, boot9strap is your bootloader and Luma is your chainloader.
Help yourself Especially for any kind of boot issue ("GodMode9 doesn't boot"), but also in many other cases these steps make a lot of sense and we will ask you to do them anyways:
Have you actually read this? [X] I have read the information above