01212: kingofb: There are big brown lines at the screens where the boxers are about to start.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
01212	Graphics	Minor	Have not tried	Feb 12, 2008, 14:44	Apr 3, 2008, 07:25

Tester	-Misc Reporters-	View Status	Public	Platform
Assigned To		Resolution	Fixed	OS
Status [?]	Resolved			Driver	dataeast/kingobox.cpp
Version	0.37b16	Fixed in Version	0.72	Build
		Fixed in Git Commit		Github Pull Request #

Summary	01212: kingofb: There are big brown lines at the screens where the boxers are about to start.
Description	There are big brown lines at the screens where the boxers are about to start and it shows the fight money, rounds and where they are resting after each round. Also as soon as a round is over, for a half a second the score and round indicater is still haging there. Don't know if that happens on the real machine or not, it doesn't look like it should.
Steps To Reproduce
Additional Information	Posted by Zip
Github Commit

Flags
Regression Version
Affected Sets / Systems	kingofb

Attached Files	king0001.png (3,536 bytes) Apr 2, 2008, 21:09
	king0004.png (3,212 bytes) Apr 2, 2008, 21:09
	0000.png (4,717 bytes) Apr 2, 2008, 21:10
	0001.png (4,331 bytes) Apr 2, 2008, 21:11

No.00500 Tafoid Administrator Apr 2, 2008, 19:50	Can anyone provide a screen shot of this? I just can't see it..
No.00501 RansAckeR Tester Apr 2, 2008, 21:15	Added snapshots, the first and second are from mame 0.37b16, the third and fourth from 0.124a. In other words, this is fixed. "Also as soon as a round is over, for a half a second the score and round indicater is still haging there." This happens in 0.37b16 and 0.124a, but the score gets cleared at the same time the 'player power' is displayed. That doesn't look like a bug at all imo.
No.00503 Tafoid Administrator Apr 2, 2008, 21:49	I also agree with the end of round observation he made isn't a bug. You confirmed 0.72 as the fixed version? Good Deal.
No.00505 RansAckeR Tester Apr 3, 2008, 07:25	(Can you quote here?) Actually it could be fixed in one of the 71uX versions, but I don't have those compiled. Looking at the whatsnew however, 0.72 is probably right.