03677: All sets in cchasm.c, cinemat.c, segag80v.c, vertigo.c: -flicker command-line doesn't effect the vector output

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
03677	Interface	Minor	Have not tried	Jan 19, 2010, 17:46	Jun 22, 2017, 15:38

Tester	Tafoid	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	Fixed	OS	Windows 2000
Status [?]	Resolved			Driver
Version	0.136u1	Fixed in Version		Build	Normal
		Fixed in Git Commit		Github Pull Request #

Summary	03677: All sets in cchasm.c, cinemat.c, segag80v.c, vertigo.c: -flicker command-line doesn't effect the vector output
Description	Use a -flicker with any value doesn't have a noticeable effect on the vector output.
Steps To Reproduce
Additional Information	It might be that these certain drivers are not using a centralized 'vector' framework and might use unique video code.
Github Commit

Flags
Regression Version
Affected Sets / Systems	All sets in cchasm.c, cinemat.c, segag80v.c, vertigo.c

Attached Files

No.13925 Fujix Administrator Jun 22, 2017, 15:38	The vector handling has been updated and this issue is gone now. Although assigning the flicker value (0.0 to 1.0 instead 0 to 100 previously) directly on the command line such like: mame64 -flicker 0.8 spacewar properly reflected in the vector display, adding an value in a mame.ini for the flicker option doesn't work at all.