03972: turfmast: There are glitches at the start of hole 17 on the Japan course.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
03972	Graphics	Minor	Always	Aug 3, 2010, 13:35	Nov 30, 2018, 08:52

Tester	Smitdogg	View Status	Public	Platform
Assigned To		Resolution	Fixed	OS
Status [?]	Resolved			Driver	neogeo/neogeo.cpp
Version	0.139	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	03972: turfmast: There are glitches at the start of hole 17 on the Japan course.
Description	There are glitches at the start of hole 17 on the Japan course. There are a couple of horizontal lines that glitch back and forth. It might happen on the real hardware. I attached a save state.
Steps To Reproduce
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	turfmast

Attached Files	turfmast.zip (26,888 bytes) Aug 3, 2010, 13:35
Attached Files	turfmast_mame_0.203.zip (30,227 bytes) Nov 27, 2018, 13:49 Uploaded by MetalGod

No.06489 Smitdogg Senior Tester Aug 3, 2010, 13:36	I can't remember if this has been brought up or not before, but I didn't find anything searching for turfmast, so I guess it hasn't.
No.06493 Tafoid Administrator Aug 3, 2010, 13:59	That's the issue with Neo-Geo, especially with all the recent 'bugs' brought up where the majority of them have been BTANB. http://www.mametesters.org/rules.html Rules clearly detail the need of having proof the graphic bug exists on original hardware for Neo-Geo before even posting and I'm going to start getting very stickler over this simple to follow bug policy. I'm trying to be lenient but I'm getting sick of all this 'might be a bug' nonsense. This is the last one I'll confirm for Neo-Geo, regardless of how common a game might be to check.
No.06507 treblewinner Tester Aug 5, 2010, 10:23	Turf Masters makes pretty extensive use of raster effects - which this sounds like.
No.15818 MetalGod Senior Tester Nov 22, 2018, 01:10 edited on: Nov 27, 2018, 13:52	Tested on mame 0.203 Not happening now. So I guess the issue is fixed. *Edit. Savestate added to the ticket: