01124: gradius3: There's a glitch that is either an offset problem or a visible area problem.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
01124	Graphics	Minor	Have not tried	Feb 11, 2008, 15:37	Jul 20, 2015, 19:29

Tester	robiza	View Status	Public	Platform
Assigned To		Resolution	Bugs That Aren't Bugs	OS
Status [?]	Resolved			Driver	konami/gradius3.cpp
Version	0.109u1	Fixed in Version		Build
		Fixed in Git Commit		Github Pull Request #

Summary	01124: gradius3: There's a glitch that is either an offset problem or a visible area problem.
Description	There's a glitch that is either an offset problem or a visible area problem. Reply from Mamesick: Yeah, that's why I changed back in my 32FX the visible area to 304x224 (which is wrong but at least fixes those issues. An hack a la NeoGeo) IIRC someone here in the past said that this happens on the real PCB too.
Steps To Reproduce
Additional Information
Github Commit

Flags	Verified with Original
Regression Version
Affected Sets / Systems	gradius3

Attached Files	gradius3_0109u1gre.png (24,941 bytes) Feb 14, 2008, 18:03

No.06725 Haze Senior Tester Sep 13, 2010, 22:51	Yeah, this should be checked on a pcb, there are similar problems in other games which have turned out to be non-bugs. Cyberlip on the NeoGeo is the worst offender for this type of thing ;-)
No.06965 haynor666 Tester Dec 28, 2010, 21:17	Probably related to ID 04118
No.08685 haynor666 Tester May 28, 2012, 15:40	Is it possible that this is correct PCB behavior just like in bug 4790 ?
No.08695 Ace Tester May 30, 2012, 20:53 edited on: May 31, 2012, 05:43	Judging by this video of Gradius III recorded off the original board (look at the preview shot): It looks like this is correct PCB behavior, although it seems as if there are too many pixels drawn on the left side of the screen in MAME.
No.08696 haynor666 Tester May 30, 2012, 21:34	Are you sure it's PCB? This guy seems to use autofire, not very common.
No.08698 Fujix Administrator May 31, 2012, 03:50	Because objects on the background are not fully synchronized, the movie is from MAME.
No.08705 Ace Tester May 31, 2012, 22:38 edited on: May 31, 2012, 22:41	What? I doubt it's from MAME judging by the background noise when there's no sound (turn up the volume and you'll see what I mean). Not to mention, this IS a Japanese player playing the game and they can button-mash pretty damn quickly. Take a look at the user's channel; he's got a multitude of Gradius III videos all recorded from the same source. Another thing too: MAME has a pink vertical line during the Gradius timeline during the attract mode. If you look at the snapshot on this video: The line is not there at all, and if you pay close attention at the 13:18 mark, you'll see there's no line at all. I also fired up MAME to check the synchronization of the objects and backgrounds, and they behave exactly like in the videos (I'm using 0.144u4). The sound is also different, which I'll post a separate bug report for.
No.08706 Fujix Administrator Jun 1, 2012, 03:03 edited on: Jun 1, 2012, 03:06	We don't care if the video author is Japanese or not. That doesn't prove anything at all. There are a lot of Gradius III "arcade" videos that Japanese recorded out there.
No.08708 Ace Tester Jun 1, 2012, 17:39	I was pointing something out, Fujix. All I'm saying with that remark is not to jump to conclusions about players using rapid-fire. Either way, I give up. I'll let someone else figure this out.
No.11886 haynor666 Tester Jul 20, 2015, 12:26	Here is another video look at 59:40 Since many Konami games from that era a proven to have trash at edges of screen this bug is 99% also on PCB.
No.11887 system11 Senior Tester Jul 20, 2015, 19:29	Browsing videos on NicoNico as well as the other evidence presented here, this is normal (and typical) slightly dodgy Konami behaviour.