Galaga ROM 02 Issues with MAME Update

The latest update for MAME has brought some unexpected issues to several games, including Dig Dug and Galaga. Upon testing, it was observed that deleting the config files (cfg) for these games resolves the problem temporarily. However, further investigation reveals that there seems to be a deeper issue at play.

After loading Dig Dug or Galaga in MAME, closing the emulator, and then reopening it, the problems persist. The game continues to display incorrectly, with Galaga booting up in an upside-down screen and getting stuck in what appears to be service mode.

It's possible that this issue is related to the NVRAM write problem, which has been reported before. A hard reset may sometimes resolve the issue, but deleting any galaga.ini or nvram files seems to provide a temporary fix.

Another theory is that uninitialized variables are causing the game to start up randomly, leading to these display issues. To test this hypothesis, it's recommended to create a new folder for MAME, place Galaga.zip in the roms directory, and launch the game with default settings.

It's also possible that an older autosave file may be causing problems due to changes made in devices for version 0.153, particularly those affecting Namco customs. If you're using -autosave, this could be a potential cause of the issue.

In one instance, launching Galaga in MAME version 152 resulted in no display issues at all, suggesting that the problem may have been introduced in version 153. Further testing revealed that only Galagamk and Galaga are affected by this issue, with Galaga displaying correctly after deleting its nvram file.

For those experiencing these problems, it's recommended to try resetting MAME or deleting any galaga.ini or nvram files to see if the issue persists. If you're still having trouble, please provide more information about your system setup and MAME configuration to help diagnose the problem further.

Galaga rom 02