02110: All sets in cps3.c: video from a DV cam proves the refresh rate of CPS3 in MAME is wrong

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
02110	Cheat System	Minor	Always	Aug 11, 2008, 15:52	May 31, 2012, 05:33

Tester	emuman	View Status	Public	Platform
Assigned To	aaron	Resolution	Fixed	OS
Status [?]	Resolved			Driver	capcom/cps3.cpp
Version	0.126u2	Fixed in Version	0.127u1	Build
		Fixed in Git Commit		Github Pull Request #

Summary	02110: All sets in cps3.c: video from a DV cam proves the refresh rate of CPS3 in MAME is wrong
Description	an arcade operator provided me a video from a DV cam which proves the refresh rate of CPS1 and CPS3 in MAME is wrong. in the video the black bar caused by VBI is flying up, so the rate must be less than NTSC's rate of 59.94fps. CPS3 FPS is slightly different from CPS1/2. the machines in the video are, from left to right: SF3, SF3(MAME bootleg, please ignore it), Last Blade2, SFZ3, SFZ2AJ, SF2CE
Steps To Reproduce
Additional Information	Split from 02044 for CPS3.
Github Commit

Flags	Verified with Original
Regression Version
Affected Sets / Systems	All sets in cps3.c

Attached Files

No.02058 aaron Developer Aug 14, 2008, 06:41	Guessing that it's the same as CPS1/2, since they all run at the same resolution.
No.02059 Mamesick Senior Tester Aug 14, 2008, 15:52	I wouldn't claim this one as a fix since it's a guesswork. The video provided shows that CPS3 refresh rate is a little bit different.
No.02062 Kold666 Developer Aug 14, 2008, 18:58	it should be verified. CPS1/2 share many video customs and in particular the cpsb21, while if I am not wrong cps3 uses entirely new ones.
No.02064 Fujix Administrator Aug 15, 2008, 03:34 edited on: Aug 15, 2008, 03:34	I reopened the issue to be reconfirmed with the real arcade. (Screen refresh rate has been changed to 59.633333 Hz from 60 Hz in 0.126u5)
No.02076 aaron Developer Aug 15, 2008, 22:57	Whatever you want to do is fine. However, this same issue affects hundreds of games in MAME, and I don't think you want a bug on each of them. I fixed the bug as well as I could based on the data I had. There is a note in the driver that it is just a guess. Not quite sure what you want to do about that. We don't have accurate measurements of the refresh speed for the large majority of games and are relying on guesswork. Everything that currently says 60Hz is guaranteed to be wrong. :)