Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
07719 DIP/Input Minor Always Jul 31, 2020, 21:51 Aug 13, 2020, 17:33
Tester rcoltrane View Status Public Platform MAME (Official Binary)
Assigned To Resolution Open OS Windows 10 (64-bit)
Status [?] Confirmed Driver atarisy1.cpp
Version 0.222 Fixed in Version Build 64-bit
Summary 07719: indytemp: [possible] inp playback issue
Description After finishing the game with 1 coin and 3 lives on hard, I tried to playback the gameplay to record a video, but the inp file lost sync at the 1st level and ruined the playback.
Steps To Reproduce Record an .inp file while playing the game and after playing it for some time, quit the game and try to playback it.
Additional Information I've attached my latest .inp file here to be analyzed.
Flags Possible
Regression Version
Affected Sets / Systems indytemp
Attached Files
? file icon indytemp - 1cc hard 3 lives.inp (387,206 bytes) Jul 31, 2020, 21:51 Uploaded by rcoltrane
There are no relationship linked to this issue.
User avatar
Aug 12, 2020, 19:26
It's possible that desyncing on this game is caused by nonvolatile data being changed. This likely affects numerous other games as well.

Perhaps the INP file format should be changed to include a checksum of NVRAM data taken when recording begins to ensure integrity.
User avatar
Aug 12, 2020, 20:59
nvram must be clean, in fact, for .inps to work at all correctly.
The leading MAME high score site insists on such usages when recording inputs for submissions.
f) As of 15 September 2001, the use of nvram files is prohibited, unless otherwise specified in special rules. If a person thinks a certain game fits into that category, he must contact any of the editors so they can discuss the issue. After the discussion all the editors will vote for or against the idea and present a final decision. All games will be discussed on a case by case basis.
You can also download this file to ensure no nvram is used if you use the commandline. (usage: record {gamename}). It should be noted that in some games, having hiscore.dat present can affect playback, as can memory cards (memcard\memcard.*), so it would be wise to remove these before recording.
The same goes for difference files (diff\*.dif), which contain changes made to a CHD (Compressed Hunk of Data - typically a Hard Drive or CD image). If the corresponding file isn't deleted or moved before recording, the INP is likely to be unplaybackable.
It is strongly recommended that you set the nvram_directory option to NUL (or /dev/null for Linux/BSD/OS X users) in mame.ini, or simply add to the commandline -nvram_directory NUL or -nvram_directory /dev/null on Linux/BSD/OS X.

Of course, I always seem to forget when dealing with .inps, but they have a high chance of playback issues when such nvrams are not default/cleared.
User avatar
Aug 13, 2020, 17:33
In this case I had no NVRAM recorded. I always check if a NVRAM file is present and I delete it before recording (i've learned it from Haze in the past), but in this game I had NVRAM disabled before playing/recording. So I think it's not a NVRAM-related issue.