mgba: mGBA doesn't write any battery files or save states
I tried using mGBA for my Pokémon tournament. I configured mGBA in portable mode to the right settings, and then copied the folder onto a USB-flashdrive. I then handed this drive around so people could get a copy. However, the copied version of mGBA failed to create .SAV files next to the rom - regular save states did not work either.
Without knowing anything about it, I suspect it has something to do with “portable mode”? IMO, portable mode should be default for an application that does not provide an installer/uninstaller. Writing permanent data somewhere on the filesystem without the option to remove it isn’t very nice.
EDIT: I forgot to mention something important - i wrote a batch script to quickly copy and launch the ROM with
start "" "%userprofile%\Desktop\mGBA\mGBA.exe" "%userprofile%\Desktop\mGBA\ROM.gba"
Maybe it’s related to the use of backslahes in the parameter?
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 18 (8 by maintainers)
hey i figured out PRECISELY what is going on with the saving issue. turns out thers a glitch in the emulator that occurs EXACTLY after loading your current savefile and starting the game. once in if you complete actions in games and save and leave the game or exit to the consoles menu [or anything that involves leaving the mgba emulator game you are playing] the emulation software glitches out and refused to load or save any savefiles created after returning. basically if on a vita or wii and you temporarily exit the app or the console sleeps the game you are playing will no longer register saves. it will however keep the most recent savefile UP TO the first point you exited. on the vita i tested this, using single and multiple actions and various methods of leaving the game from total leaving to just putting the console on screen sleep or pressing the PS button. upon returning and doing LITERALLY ANYTHING after these actions NOTHING saves. however ALL ACTIONS and game data achieved PRIOR to these things after loading the game up and then saving actually created a valid savedata. so the mgba developer team just needs to find where in the code it is causing the game to exit upon going standby and basically write the app to always run in the background. that should theoreticaly prevent games from thinking you left. otherwise if you want to keep your savefiles and play being able to save just make sure you save BEFORE doing anything that might exit the game. i did however find a bypass for lack of savegame capabilites: 1.use the “take screenshot” option 2. go to the “save state” option 3. save state 4. when you restart your game back up, if your normal savegame fails just load the save state. i tested it and taking a screenshot seems to guaraantee the ability to create a savestate every time. to check whether the state saved just move or change the visuals around you in some way and go to “load state” and select whatever # state you saved. if its different from your current view, it worked.
but there you go. i found what was going on with this rediculous saving issue and even found a way around it. now someone please go fix it.