Issue:
I’ll soon be getting a powerful Android handheld, so before getting it I was trying to make sure all my save files from my 3DS worked in Citra on my current Android device - a Samsung Tab S8. All of them transferred over successfully except one - my save data for the eshop game Rusty’s Real Deal Baseball (a game that was insanely difficult to 100%). The strange thing is that it transferred over flawlessly when I tried using the official Play Store version of Citra. But that version is very old, is called the Early Access build, and is missing many useful quality of life things found on current versions. (I’m not even able to map the d-pad for my controller with that version, as it just has left/right axis and up/down axis inputs, as if it were a control stick - and it doesn’t let me set the d-pad on it.) But on every single other Citra version - the latest Nightly, latest Canary, and even the unofficial Citra MMJ fork - after I copy over my save data and start the game, I get a “Save Data Corrupted” message, and it resets the save data to brand new again.
I’ve tried every possible solution I could imagine - including making sure the game, DLC, and save data files were clean and worked (all from my own 3DS). Just to be sure, I also tried it with an online copy of the game and DLC - still didn’t work. I even brought over my actual 3DS system files. I also tried it out with the Windows Nightly Citra on my laptop, and it didn’t work there either. Nothing has worked. Again, the save data worked fine on the Play Store version of Citra. The only variable that has made any difference in the version of Citra. I would really like to use a far-more-current version because of the countless improvements, but for some mysterious reason none of the newer ones will accept the data.
I would really appreciate any potential help with this. It’s been driving me crazy. I included a screenshot of the error message, as well as the log file - I closed out Citra right after the error happened and then copied it to include here, as instructed. Thanks in advance!
I hadn’t gotten any replies after two days, so just thought I’d give this a bump. Is there anyone who can help figure out what’s going on with this? I know it’s a pretty obscure game, but I was hoping the log I attached would help in some way. I’ll also be happy to provide any other info if useful. Again, it’s like the more current, refined versions of Citra are lacking something that the older Play Store version has - since the save data only works on that “Early Access” version. I hope it can be figured out, so I don’t have to keep a second version of Citra installed just for one game. Any reply would be appreciated.
I’ve encountered this problem on the Odin2 as well and have not discovered a solution. I’ve run the game with Nightly, Canary, Play Store, and even MMJ, and each version states that the save data is corrupted everytime I reopen the game aside from the Play Store Version. I haven’t transferred a save from anywhere else, and I’ve tried replacing the game ROM. The only way I’ve been able to work around this issue is with save states on Nightly and Canary.
Huh, that’s interesting. I had never even tested to see if newly created save data also got corrupted after opening the game again. So I tried it out, and sure enough, it does. So the issue certainly isn’t with my save data. Thanks for sharing your experience, that was helpful.
Okay, and sorry for asking - I’m still fairly new to the whole emulation scene. Thanks for letting me know.
So after I understood how you were going to pinpoint where the problem started, I went ahead and spent the time to use your proposed process to find it. And it turns out the problem actually began very recently - just a few weeks ago. The save for Rusty’s Real Deal Baseball works all the way up until nightly-2020. Then in nightly-2021, it stops working. I confirmed this using the Windows versions on my PC first, and then the Android versions on my tablet. The results were consistent on both. Hopefully you can use that knowledge to figure out what changed that caused this? Let me know once you find out anything. Thanks again!
You’ll understand it far better than me, of course, but I did scan through it and noticed the line (multiple times) that said: “core/file_sys/savedata_archive.cpp:OpenFile:66: Path not found” followed by a path that eventually led to a “MBoxInfo____” file. So I tried to find that path to see why it wasn’t found - and at the very end, where the log said the path should’ve ended with “CEC/000d2900/MBoxInfo____”, the 000d2900 folder was missing. The file was just in the CEC folder. Also, the file was called “MBoxList____”, not Info. First I tried adding in the missing folder (didn’t notice the different name of the file initially). The next time the log said “MBoxInfo____ can’t be open without mode create.” After seeing and correcting the name the next time, I just got a different message. But it didn’t fix the problem, as I expected. Worth a shot.
Anyway, maybe that part doesn’t help you, but hopefully the new log does. Let me know if I can provide anything else to help.
Edit: I just tried using the nightly-2020 version so I could look at the log for that, and it had that same exact error message with the same save path info. But the save data works in that version, so that part of the log is obviously irrelevant. I’ll just leave it to the pros who know what to look for going forward.
Client Version Nightly 2038 HEAD-b6acebc
Operating System Windows 10 Version 22H2 (Build 19045.3693)
CPU Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz | AVX2 | FMA
Graphics API OpenGL 4.3.0
Graphics Renderer Intel(R) UHD Graphics
GPU Driver Version 30.0.101.1338
CPU JIT [x]
Hardware Shader [x]
Hardware Shader, Accurate Multiplication [x]
Shader JIT [x]
System Region -1
Shader Disk Cache [x]
Here’s some issues I found with your log that might help.
Client Version Nightly 2038 HEAD-b6acebc
Operating System Windows 10 Version 22H2 (Build 19045.3693)
CPU Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz | AVX2 | FMA
Graphics API OpenGL 4.3.0
Graphics Renderer Intel(R) UHD Graphics
GPU Driver Version 30.0.101.1338
CPU JIT [x]
Hardware Shader [x]
Hardware Shader, Accurate Multiplication [x]
Shader JIT [x]
System Region -1
Shader Disk Cache [x]
Here’s some issues I found with your log that might help.
Client Version Nightly 2038 HEAD-b6acebc
Operating System Windows 10 Version 22H2 (Build 19045.3693)
CPU Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz | AVX2 | FMA
Graphics API OpenGL 4.3.0
Graphics Renderer Intel(R) UHD Graphics
GPU Driver Version 30.0.101.1338
CPU JIT [x]
Hardware Shader [x]
Hardware Shader, Accurate Multiplication [x]
Shader JIT [x]
System Region -1
Shader Disk Cache [x]
Here’s some issues I found with your log that might help.
I just pressed A to go past the intro screen and closed it after the next screen came up. (The error message in the newer versions comes up right after I do that - press A to go past the intro.) Hope that helps.
Client Version Nightly 2020 HEAD-b231a22
Operating System Windows 10 Version 22H2 (Build 19045.3693)
CPU Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz | AVX2 | FMA
Graphics API OpenGL 4.3.0
Graphics Renderer Intel(R) UHD Graphics
GPU Driver Version 30.0.101.1338
CPU JIT [x]
Hardware Shader [x]
Hardware Shader, Accurate Multiplication [x]
Shader JIT [x]
System Region -1
Shader Disk Cache [x]
Here’s some issues I found with your log that might help.
Actually, it seems to load the save as soon as I’m in the game. I can see my character wearing the uniform I picked out long ago. Additionally, the title screen itself looks very different in my completed file compared to the default empty title screen. So I don’t think there’s anything more I can load.
If anything, I wasn’t sure whether I should progress slightly further in the corrupted version. I had been closing it right after it gave the message saying that new save data was created after the corrupted message. So I just pressed A a few more times to pick a default character and go to the same screen I got to in the working version, before closing it. I can give you that slightly longer log if you think it could help. But yeah, I don’t think I can load anything more in the working version unfortunately.
