> I am having an interesting intermittent bug with Gorf and MAME 0.145u8 (and earlier
> updates, too). I frequently use the autosave state function [autosave 1, CORE
> STATE/PLAYBACK OPTIONS], but when I exit Gorf from the high score screen, or certain
> portions of the attract screen, instead of a quick exit and save of state, there is a
> long pause, and the state does not save. The previous saved state remains.
>
> Is this an appropriate bug to report on Mame testers?
>
> I'm guessing save state "bugs" don't really apply there, but I'm interested to know
> if anyone else can replicate this problem, and if it's a known issue.
>
> I'm running a self-compiled mame64 v0.145u8, on Windows 7 x64. It's been a problem
> for several versions now. To my experience, if you exit during a gameplay screen, the
> state will save, even if it's in attract mode. That's what I've been using as a
> workaround.
I played around with this some and you are right - at certain times the save function doesn't seem to work correctly. You can notice how normally when you ESC to exit it will do it quickly. When you are going to get a malfunction, ESC to actual emulator exit takes quite a bit longer than normal. It's a valid bug as once something is set up with -autosave capability, it's expected to work 100%. So, feel free to submit it to MameTesters.
|
Index 
Flat 
Re: Gorf bug?
Reply
