Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06922 Save/Restore Minor Always Mar 25, 2018, 17:45 Apr 10, 2019, 12:49
Tester rcoltrane View Status Public Platform MAME (Official Binary)
Assigned To Resolution Invalid report OS Windows 10 (64-bit)
Status [?] Closed Driver gladiatr.cpp
Version 0.194 Fixed in Version Build 64-bit
Summary 06922: ogonsiro: INP playback failure
Description Today I tried to record an .avi of my Ohgon no Shiro 1cc gameplay but the .inp playback failed to reproduce my entire gameplay. It went out of sync in the middle of the 3rd stage against the green knights and I was unable to record my gameplay.

I tried to playback another .inp recording I did prior to this one and it also went out of sync, this time at the very 1st stage. Something is going wrong with the .inp recording, at least with this game, which uses very fast inputs, since you have to move the joystick up and down pretty fast sometimes during the intermissions to make the big shield.
Steps To Reproduce Play the entire game or at least until the end of the 3rd stage while recording an .inp file. QUit MAME and go back to the game to playback the .inp file you recorded.
Additional Information
Regression Version
Affected Sets / Systems ogonsiro
Attached Files
zip file icon (7,909 bytes) Mar 26, 2018, 04:17 Uploaded by wuemura
.inp file
? file icon ogonsiro - 1cc - rcoltrane.inp (408,419 bytes) Mar 27, 2018, 02:10 Uploaded by rcoltrane
There are no relationship linked to this issue.
User avatar
Mar 25, 2018, 23:54
Please attach your .inp file (in compressed .zip or .7z) so someone can observe the issue
User avatar
Mar 26, 2018, 04:19
Can't reproduce.
Recorded with:
mame64 ogonsiro -record ogonsiro.inp

Play with:
mame64 ogonsiro -playback ogonsiro.inp
User avatar
Mar 26, 2018, 13:41
edited on: Mar 26, 2018, 17:48
@tafoid: ok, I will attach my full .inp playthrough here later today.

@wuemura: Have you played the entire game recording an .inp file and after that have you tried to playback it to the end? EDIT: I guess not, your .inp file has 18kb in size, where my full playthrough has 399kb.
User avatar
Mar 27, 2018, 02:12
I've attached my full 1cc playthrough .inp file here to you guys to analyze and see what could have happened. It lost sync at the green guys in the middle of the 3rd level. Until that point, the playback was fine.
User avatar
Mar 27, 2018, 03:44
edited on: Mar 27, 2018, 03:45
Your playback seems to get near the end of the walking mode of the level with movements you'd expect - as soon as the first fight start, things seem to be going awry. I'm changing your reporting version to 0.194 as that is what your .inp says you used to record with (and, I assume, it was the mainline build from as that is what I attempted to play it back with.

Confirming based on playback
User avatar
Senior Tester
Mar 27, 2018, 16:08
can't confirm

seems more likely a user error (didn't clear nvram before recording?)
User avatar
Mar 28, 2018, 11:29
edited on: Mar 28, 2018, 11:32
Do I need to erase my nvram every time I want to record a new .inp file? Why an nvram file would impact my inp recording?
User avatar
Mar 28, 2018, 16:22
I forgot the who procedure with recording/using .inps as well. Each recording requires a cleanly created NVRAM or making sure the current NVRAM you have isn't use by setting your NVRAM_DIRECTORY in your .ini to NUL

If you can confirm your issues with clean NVRAM record, then clean NVRAM again and playback we might have something.
Adjusting to acknowledged until we get confirmation from OP about his issues with proper playback/record.
User avatar
Senior Tester
Mar 28, 2018, 16:43
yes, you need a clean nvram before recording or playing back

otherwise the game boots into an unknown state.

if the game is in an unknown state various things will not execute with precisely the same timing in-game, especially randomly generated things, but even something as simple as the game not having to init the nvram on boot can throw everything off by a frame or two.

this means that at some point the inp will go out of sync, it's basically guaranteed to.
User avatar
Senior Tester
Apr 10, 2019, 08:12
After a year, the tester did not confirm the issue with a proper playback/record with clean NVRAM
I guess this report could be closed.
User avatar
Apr 10, 2019, 09:38
Sounds valid.
User avatar
Apr 10, 2019, 12:49
I'll note here that ensuring reproducible playbacks is one reason I added the -nonvwrite option.