02914: -str/-seconds_to_run does not account for runtime stored in save states

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
02914	Save/Restore	Feature	Always	Feb 9, 2009, 19:13	Nov 16, 2018, 19:05

Tester	Coadey	View Status	Public	Platform	SDLMAME
Assigned To		Resolution	No change required	OS
Status [?]	Closed			Driver
Version	0.129u3	Fixed in Version		Build
		Fixed in Git Commit		Github Pull Request #

Summary	02914: -str/-seconds_to_run does not account for runtime stored in save states
Description	When using the -seconds_to_run feature combined with -state or -autosave, the previously elapsed time stored in the save state isn't taken into account. For instance, if you save a state 30 seconds into a games execution, and later use that state with "-str 35", mame will exit 5 seconds into the session, rather than 35. This is compounded when using -autosave, as the save state elapsed time will always increase.
Steps To Reproduce	Record a save state (e.g. auto.sta) ./mame -autosave GAME Load the state and use str: ./mame -str TIME -state auto GAME
Additional Information	This was discovered when using save states to jump into the attract mode for a random game and using -str to auto exit (before jumping to a new random game during an idle front end).
Github Commit

Flags
Regression Version
Affected Sets / Systems

Attached Files

No.03748 couriersud Developer Feb 18, 2009, 19:17	I would consider this as "feature, not a bug". "-str" is mainly used for regression tests and to a much lesser extend benchmarking. Therefore the time is measured since startup and requires "-noautosave". Consider this a "debug" feature.
No.03754 Tafoid Administrator Feb 18, 2009, 20:15	Sounds reasonable. I'll set this as "Feature" then.
No.03868 couriersud Developer Mar 1, 2009, 14:45	I doubt this will be changed, assigning to Aaron for comment
No.15789 MetalGod Senior Tester Nov 16, 2018, 19:05 edited on: Nov 16, 2018, 19:06	I guess this old "issue" could be closed.