03062: -throttle forgotten with high -frameskip

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
03062	Core	Major	Always	Mar 22, 2009, 17:18	8 days ago

Tester	AndersH	View Status	Public	Platform	MAME (Official Binary)
Assigned To	cuavas	Resolution	Fixed	OS
Status [?]	Resolved			Driver
Version	0.130	Fixed in Version	0.253	Build
		Fixed in Git Commit	65aeb63	Github Pull Request #

Summary	03062: -throttle forgotten with high -frameskip
Description	Use the -throttle option (default), press F11 to display performance ratio, select frameskip with F8/F9 keys, some games run at well above 100% (unthrottled?) at high frameskips. I checked only 3 examples: - 1943: always limited to 100%, OK - invaders: limited to 100% at frameskip 0-9, too fast at frameskip 10 - tapper: limited to 100% at frameskip 0-8, too fast at frameskip 9-10
Steps To Reproduce	The description is clear on this
Additional Information
Github Commit

Flags
Regression Version	0.113u2
Affected Sets / Systems

Attached Files

No.04031 Tafoid Administrator Mar 22, 2009, 22:44	Using TAPPER as an example, I was able to reproduce this behavior. As soon as I hit 9, the emulation acts as if it's unthrottled.
No.04048 Fujix Administrator Mar 23, 2009, 12:24	Yes, I confirmed this! Great.
No.04067 Tafoid Administrator Mar 25, 2009, 16:37	Went back and found a regression version: 0.113u2 Not too sure on the cause.. The only tidbit I see in the whatsnew that might directly effect this game: Changed throttling behavior to only throttle on non-skipped frames. This should give a little better performance on games where frameskipping is necessary. [Aaron Giles]
No.12559 Osso Moderator Apr 27, 2016, 11:21	This seems related to the screen refresh rate. Games with 30 will always will go unthrottled with frameskip 9 and 10, games with 60 won't go unthrottled.
No.14465 Kale Developer Nov 26, 2017, 00:54	Anything that runs at < 60 Hz will sport this bug. So Street Fighter 2 (59.63) yes, Devastators (60) no
No.22802 PL1 Tester 9 days ago	Both invaders and tapper appear to be steady at 100% in v0.262, even with frameskip 10. No idea what commit or version fixed it.
No.22803 hap Developer 9 days ago	Looks like 0.253 is where it was fixed. Not sure which commit, maybe a 'side effect' of one of cuavas's input related commits.
No.22807 cuavas Administrator 8 days ago	It’s caused by 65aeb63a2a1f4f65a6fa0dedabba1b852a189f96, specifically the, “Synchronise with wall clock any time inputs are read. Not doing this has weird effects on relative inputs with frame skipping and contributes to unresponsiveness of menus,” part. It effectively reverts the 0.113u2 change in behaviour mentioned by Tafoid as well as other stuff.