flyinghead
Spawn (Naomi) EEprom not saving or being overridden with defaults on a fresh boot
Platform / OS / Hardware: Windows 10
Github hash:
Hardware: AMD 1850 GTX960
Description of the Issue When booting this game you need to change Network to OFF in the test menu otherwise it'll just be checking the network constantly and not boot. I save and exit after changing this, booting into the game from the test/service the game and it plays just fine. However on a fresh boot it has reverted back to Network = Slave. So the EEprom is not saving correctly or it is being overridden on a fresh boot.
This causes the user to select Network = Off on every play session as it doesn't play in Slaver or Master
Flycast overrides the EEPROM network settings for this game. Since Naomi networking isn't supported on RA it should always sets Network to OFF at boot, which it does on my machine but not on yours for some reason.
Try to locate and delete any spawn.zip.eeprom file you can find in retroarch config/saves files.
It does the same thing. RA Enables Network automatically on this game as notification pops up. Could be an RA issue. Just trying to think why mine wont auto set network to off
Another basic question I shouldn't have to ask: what's the version of the core you're using?
v1.3-56-gc57e888 the latest I believe. So sorry for leaving important info out. Have sent a tip to compensate
Thank you very much for your contribution! You don't deserve a fine though ;) Most people omit crucial information when reporting issues.
Your Flycast version dates from May 1, so it's not that recent. I would suggest you upgrade Flycast with RA core updater.
Updated to c77c3ab and still the same issue. Tried disabling free play toggle as thought that may be causing a clash with the NVMEM/EEPROM, but alas no change
As far as I know there's only one version of this game so that shouldn't be an issue. Can you confirm you are using the spawn.zip MAME rom?
Are you loading any savestate, manually or automatically? A savestate contains the eeprom data so it would override Flycast's settings.
Can you try Flycast standalone and check if the issue is there as well?
This is now fixed with the core and standalone. Thanks for the updates.