Some of the following information has been updated in later posts so please scroll down further to view these updates. Not everything has been updated though as there was no need for it since the information is already in this post. The updates do include all of the Dragon Ball (Z)(GT) games that are listed here as well as a new Pokemon game the was recently released. There is also more information about the IPS patches for all of the Pokemon games.
I've been using VisualBoy Advance for some time now (since version 1.3) and have built up quiet a large rom collection for it. Although the best Gameboy emulator out there (in my opinion) it is still not perfect. Below are a list of games that do not seem to work well in the latest versions of this emulator but do work in older versions or by modifying some of the emulator's setting.
Using all of the information in this topic (not just this post) you should now be able to use all of the below listed games on the latest version of VBA without any problems (at least as far as being able to save your game).
Dragon Ball Z Games
(See below for an alternative fix for these games)
Dragon Ball Z - Legacy of Goku
As of version 1.7.1 of VisualBoy Advance this game will display a message stating that it will not run on the current hardware.
This message does not show up in version 1.6.0 of VisualBoy Advance (I'm not sure about other versions exept 1.1 but that version is too old to worry about) and does not seem to have any other problems.
Dragon Ball Z - Taiketsu
First of all make sure you do not have an into hacked version as this version of the game will crash the emulator. Other then that it basiclly has the same problem as Legacy of Goku showing a similar message when you try to play it.
Pretty much the same way. This message does not show up in version 1.6.0 and will play perfectly.
Dragon Ball GT - Transformation
This game will also display a similar message as the above games but only after you have beaten the second planet after the game has saved.
Once the message shows up on the screen reset the emulator and load your game. You should be on the planet select screen and be able to continue your game. The only other problem here is that you will have to do this after every planet. I will do more research into this and post a better fix if I find one for this game.
IPS Save Patches - A thing of the past.
Anyone that plays the GameBoy Advance Pokemon games should know about the countless save patches for these games. I have discovered a setting in VisualBoy Advance that will make these patches obsolete.
"Corrupt Save" message and/or inablility to save your game. This problem is caused by VisualBoy Advance being unable to correctly detect the the save file size of these games.
Known Games Effected:
The simplist way to fix this problem is to increase the Flash Memory size in the emulator (Options->Emulator->Save Type and choose "Flash 128K"). However (although not confirmed) this might cause problems in other games that use 64K memory. The other solution is to create a "vba-over.ini" file in the same directory as the emulator itself. With this file you can set "game specific" options that will only be used for the games you specify. Instructions for creating this file can be found in the readme file for VisualBoy Advance. I have provided the specific setting for each known effected game below:
e-Reader (U) [PSAE] flashSize=131072 Pokemon Ruby (U) [AXVE] rtcEnabled=1 flashSize=131072 Pokemon Sapphire (U) [AXPE] rtcEnabled=1 flashSize=131072 Pokemon FireRed (U) [BPRE] flashSize=131072 Pokemon LeafGreen (U) [BPGE] flashSize=131072 Pokemon Emerald (U) [BPEE] rtcEnabled=1 flashSize=131072The legend for this code is in the read me file and I have also provided it below for your convinence.
[????]=The four character "Game Code". This can be found by choosing "Rom Information" from the file menu of VisualBoy Advance. This code must match the game you will use it for or the setting will not work. Make sure that the codes above match the rom you are using if these setting do not seem to work.
rtcEnabled=Real Time Clock <0 for false, anything else for true>
flashSize=Flash Memory Size <65536 (64K) or 131072 (128K)>
saveType=Save Type <0 for automatic, 1 for EEPROM, 2 for SRAM, 3 for Flash or 4 for EEPROM+Sensor>
The Real Time Clock setting is only used for games that need it so having it enabled for a game that does not use it really won't effect the game at all.
With this file you can leave the Flash Memory setting at 64K in the emulator and not worry about messing up any of your other game saves. When you open one of the above games the vba-over.ini file will override the emulator's default setting and use 128K memory for that game even if you have it set for 64K.
Regardless of which method you choose you can now play the game without a save patch! The game will run as it would on the real GBA without any problems and you won't get a "Save is Corrupted" message when you go to load your game again. The only problem with either of these methods is that they cannot fix an existing save file. You will have to start a new game with these setting enabled. Yes I did try this and even though it increased the save file size to 128K it still gave me a corrupt save message when I went to load my game (even though it loaded anyway). A corrupt save message does not mean you can't load your save (as you really still can) but it does get annoying and this fix will help to prevent it from ever showing up again in these games.
Other problems have been found with these Pokemon games when you use the IPS patches. See below.
Scroll down to post #9 if you want to know how to fix those corrupted saves that you have.
Please let me know if you are still having problems with these fixes and I will try to do what I can.
Edited by Haldrie, 31 March 2007 - 07:36 PM.