When going through the Mt. Battle challenge in Battle Mode (not Story Mode), if you want to suspend the challenge, the game checks whether the current save is the same one that was initially loaded to start the challenge, to make sure people don't swap memory cards to get infinite attempts. However, it's messing with Dolphin, somehow, since I can't suspend the challenge. It always says it's not the same memory card. I'm using version 14762 on Android.
Pokémon Colosseum Mt. Battle save issue
|
07-31-2021, 03:42 AM
If you've used savestates at all, the game has protection that will catch you. Dolphin has a patch to disable *most* of their save checks that you need to enable if you want to use savestates. I'm not sure if it's on by default or not.
07-31-2021, 03:47 AM
(07-31-2021, 03:42 AM)JMC47 Wrote: If you've used savestates at all, the game has protection that will catch you. Dolphin has a patch to disable *most* of their save checks that you need to enable if you want to use savestates. I'm not sure if it's on by default or not. I know that, I've never used a single savestate (I don't even have those enabled), and I've had no issues throughout story mode. However, in Battle Mode, Dolphin wrongfully triggers that protection. I've tested it by doing a single battle and then suspending the challenge (using the proper in-game process for that). It gave me the error. The patch could work around it, but I can't find it on Android, and I shouldn't have to. I'm playing the game as intended (emulation aside). 07-31-2021, 07:27 AM
Alright, I'll forward this! If you're not using savestates, it definitely shouldn't be triggering.
07-31-2021, 07:45 AM
(07-31-2021, 07:27 AM)JMC47 Wrote: Alright, I'll forward this! If you're not using savestates, it definitely shouldn't be triggering. I did edit the save with PKHeX at the beginning of my story mode playthrough to give myself some items, but I then completed the story all the way through with no saving issues whatsoever until I tried Battle Mode, so I think it shouldn't be related. If push comes to shove and the issue can't be pinpointed, I can restore the save to my memory card and try this on hardware (I'm on vacation right now, but I'll be home in a few days). Thank you very much! 07-31-2021, 08:11 AM
So, here's our guess: this is a problem with GCI folders. Can you try moving your savefile to a memory card blob instead and see if the issue happens? It's under the Memory Card setting instead of GCI folder.
07-31-2021, 08:14 AM
(This post was last modified: 07-31-2021, 08:15 AM by Shady Guy Jose.
Edit Reason: Emoji showing up as question marks
)
(07-31-2021, 08:11 AM)JMC47 Wrote: So, here's our guess: this is a problem with GCI folders. Can you try moving your savefile to a memory card blob instead and see if the issue happens? It's under the Memory Card setting instead of GCI folder. I'll try and see if the Android version allows it. If this can only be done on desktop, it'll have to wait a few days, unfortunately... 07-31-2021, 08:49 AM
Android should let you use memcard blobs. I don't know if you can easily import a save though.
08-05-2021, 02:46 AM
08-24-2021, 03:37 AM
(07-31-2021, 08:49 AM)JMC47 Wrote: Android should let you use memcard blobs. I don't know if you can easily import a save though. Finally got around to testing this again. Even after importing a .gci save to a new .raw memcard using the desktop version and setting my phone to memcard mode, the issue is still here. As a reminder, since this is an old topic, this only happens in Battle Mode Mt. Battle (no issues at all throughout Story Mode), and I haven't even enabled savestates, let alone used them. The only tampering was done early in my playthrough, to give myself some items with PKHeX (no idea if this could be related in any way). In a few weeks, I'll be able to test this save on actual hardware, if needed. |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)