Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|08073||Save/Restore||Major||Always||22 days ago||1 day ago|
|Tester||JSDS||View Status||Public||Platform||MAME (Official Binary)|
|Assigned To||Resolution||No change required||OS||Windows 10 (64-bit)|
|Version||0.235||Fixed in Version||Build||64-bit|
|Fixed in Git Commit||Github Pull Request #|
|Summary||08073: sms [aliensyn]: State load/save cause the game freeze|
|Description||State load/save cause the game freeze. In case of aliensyn, no problem on title screen or demonstration play but problem happens after start the game.|
|Steps To Reproduce||
1:execute mame with "mame sms aliensyn"
2:start the game
3:try to save state
1:copy attached "1.sta" file to "sms" folder in "state directory" (default is "sta")
2:execute mame with "mame sms aliensyn"
3:start the game
4:try to load state by "1" key.
|Affected Sets / Systems||sms [aliensyn]|
1.zip (4,602 bytes) 22 days ago Uploaded by JSDS
save state for aliensyn
|There are no relationship linked to this issue.|
20 days ago
|I can't reproduce with -autosave on several attempts during game and can only duplicate using your save state you provided which seems to show the pause screen and no key seems to let me go back to game.|
3 days ago
|The game is not frozen, just paused, but not only via the score screen shown by pressing button 2 on the control pad. I've been tricked by the same situation a few times. The state was saved to slot 1 by pressing the "1" key, that the driver maps to the Pause button of the SMS console, what I think makes sense because is equivalent to the Start/Pause button of the Game Gear and the "1" key is MAME's default mapping for a start button. The problem is when the "1" key is pressed to select the save slot 1, the action also affects the running emulation. To resume the game, after load the saved state, press the '1' key again to unpause the console and press the button 2 on the control pad to return to resume the game.|
1 day ago
Confirmed. I knew the pause screen was involved and your explanation makes sense.
Closing w/no change needed.