Unusual Playback issue for lastfght

[Chad]

http://replay.marpirc.net/r/lastfght
http://replay.marpirc.net/inp/7/3/9/zer ... olf145.zip

I played this back perfectly, pausing a bit at points to check out some screenshots, at least I thought it was perfect, until I realized I missed the exact final score (it got passed the first boss and was around 22000 at that point) but after attract mode didn't show on the highscore list. So, I thought I'd play it back again to extract the last achieved score before the last life was lost. But now I can't get it to playback and even begin to finish the first board. Didn't look like nvram was in play. Anyone else have luck with this one on the attempt after your first?

[Zerstorung]

I just tested this out, as it is my recording. Using the playback creates an NVRAM file for the game for some strange reason. Deleting it allows you to play the inp back properly again.

[mahlemiut]

Remember that NVRAM is per-device now, so the filename of the NVRAM is not easily predictable. -nvram_directory NUL (or -nvram_directory /dev/null depending on OS), should do the trick.

[The TJT]

Remember that NVRAM is per-device now, so the filename of the NVRAM is not easily predictable.

Cryptic. What does "per-device" mean?

-nvram_directory NUL (or -nvram_directory /dev/null depending on OS), should do the trick.

I guess that means a read-only file named "nvram" in your MAME folder still does the trick.

[mahlemiut]

It means that a file is created for each device in the system that has some form of NVRAM. A good example are CPS-3 games, which now creates a separate file in nvram/<game> for each indicidual SIMM chips the game uses, and another for EEPROM data (settings and so on). Previously, this would have all been combined into a single .nv file. NVRAM filenames are now named based on the device's tag, which is simply a string that uniquely identifies that device. You can use -listdevices to see a list of devices (and their tags) that a driver uses.

[Chad]

ahh, finally the option does good. It will always hide the user from this nvram initialization state penalty. Or to the busy body user (or script): just delete all files in nvram/game/*.* as well as nvram/game.nv. That was it.