Jump to content
Visual Boy Advance-M

killazys

Members
  • Content Count

    0
  • Joined

  • Last visited

Community Reputation

0 Neutral

About killazys

  • Rank
    Newbie
  • Birthday 08/30/1990
  1. Awesome! Please notify me when that becomes available
  2. Hm. That would have to be done every time I want to switch around saves right?
  3. OK. Now when can we expect a fix? Would this be prioritized at all?
  4. Thanks for the reply. I did apply an English patch to this game using IPS-Win. Could that be part of the cause?
  5. I'm trying to transfer some saves from Fire Emblem 6 to my Android device using the Gameboid emulator. Gameboid has not been updated for around a year now, and I fear the dev has since left the project. As such, I turn to you guys for support and help on this issue. Gameboid gives savegame options of SRAM, Flash, Flash 128K, and EEPROM. FE6 is detected as SRAM, and selecting SRAM in Gameboid saves the file as 32K in size (if a new game is started from Gameboid and there is no .sav file already present in the directory). This is not compatible with the VBA-M saves that are 64K in size. In VBA-M, if I select SRAM + Flash (128K), it still saves as 64K. These 64K size saves can be *read* properly by Gameboid, but they cannot be saved to. Any attempts to save will simply not work; the game will not crash or anything, but the save will just not be overwritten. Attempting to load the game with the 32K savefile in the same directory via VBA-M results in VBA-M overwriting the save, even though it can load from it properly. Is this something that can be resolved relatively easily? Any help would be greatly appreciated.
×