04050: twineag2: Missing graphic effect in screen transitions

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
04050	Graphics	Minor	Always	Sep 6, 2010, 18:04	Sep 7, 2010, 23:31

Tester	robiza	View Status	Public	Platform	MAME (Official Binary)
Assigned To	robiza	Resolution	Fixed	OS	Windows XP (32-bit)
Status [?]	Resolved			Driver	seta/ssv.cpp
Version	0.139u2	Fixed in Version	0.139u3	Build	Normal
		Fixed in Git Commit		Github Pull Request #

Summary	04050: twineag2: Missing graphic effect in screen transitions
Description	In different moment there's a screen transition; in a real HW the screen is clean from the bottom of the screen probably the effect is handled by 1c0064-1c0065 the value go down from d4 to 30 and go up from 30 to d4
Steps To Reproduce
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	twineag2

Attached Files	twin eagle ii.3gp (1,563,205 bytes) Sep 6, 2010, 18:04

No.06695 robiza Developer Sep 6, 2010, 18:07	22s and 43s: you can see the effect
No.06696 robiza Developer Sep 6, 2010, 18:29 edited on: Sep 6, 2010, 20:16	1c0060-61 = 002b 1c0062-63 = 002c 1c0064-65 = 00d4 60-61 or 62-63 maybe is start screen y 64-65 probably is end screen y 00d4-002b = decimal 169; 169 x 2 = 338 (y resolution) 00d4-002c = decimal 168; 168 x 2 = 336 (y resolution) the y resolution in the driver is 336 6a-6b : 0x12 -> start screen x 6c-6d : 0x102 -> end screen x 102-12 = f0 -> decimal 240 the x resolution in the driver is 240
No.06698 Haze Senior Tester Sep 7, 2010, 10:33	I remember Jan thought that the registers were actually the CTRC registers, that control screen size.. of course reducing the screen size to 1 pixel or whatever in MAME won't behave quite how the PCB does ;-)
No.06699 robiza Developer Sep 7, 2010, 16:24	ultrax use the same effect
No.06700 Haze Senior Tester Sep 7, 2010, 23:31	ulrax and twin eagle 2 seem to be the same codebase... they have the same protection and everything IIRC ;-)