Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
02741 Graphics Major Always Dec 15, 2008, 04:33 2 days ago
Tester Smitdogg View Status Public Platform
Assigned To Resolution Fixed OS
Status [?] Resolved Driver
Version 0.128u5 Fixed in Version Build
Fixed in Git Commit Github Pull Request #
Summary 02741: flamegun, flamegunj: On the 4th or 5th stage, the graphics go bad.
Description On the 4th or 5th stage, the graphics go bad. The entire screen is glitched to the point where you can't play anymore. It didn't number the levels, but I lost the 3rd level with a failure, then past 2 more levels, and then the glitch happens. I tested it in both sets.
Steps To Reproduce
Additional Information flameguj -> flamegunj in 0.133u1
Github Commit
Flags
Regression Version
Affected Sets / Systems flamegun, flamegunj
Attached Files
png file icon 0019.png (1,731 bytes) Dec 15, 2008, 04:33
png file icon 0020.png (2,086 bytes) Dec 15, 2008, 04:34
png file icon 0021.png (1,958 bytes) Dec 15, 2008, 04:34
Relationships
There are no relationship linked to this issue.
Notes
4
User avatar
No.04097
Smitdogg
Senior Tester
Mar 29, 2009, 18:12
On stage 5-3 of Shikigami No Shiro, a similar graphics bug happens. I've only tested it so far in MAMEUI but it might be related to this bug.
User avatar
No.04098
Haze
Senior Tester
Mar 29, 2009, 18:37
Sometimes it happens if it sends an unhandled GPU packet in the PSX emulation, causing subsequent ones to fail.

In some cases this is because there is something we don't handle, in other cases it seems to be because the game has crashed anyway, and starts ending garbage / data at the wrong time.
User avatar
No.15775
MetalGod
Senior Tester
Nov 13, 2018, 22:41
edited on: Nov 14, 2018, 12:21
Tested on mame 0.203
I've played the whole game twice and I've never seen any similar thing to the reported bug.
It is fixed as well as 3123 ( https://mametesters.org/view.php?id=3123 )
User avatar
No.15975
izius
Tester
Dec 30, 2018, 01:25
Tested a few old versions. This was fixed in 0.142u5 - I just did a complete playthrough without any problems.