Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
00939 Graphics Major Always Feb 7, 2008, 10:31 Feb 19, 2011, 21:37
Tester The tECHIDNA View Status Public Platform
Assigned To hap Resolution Fixed OS
Status [?] Resolved Driver
Version 0.120u4 Fixed in Version 0.141u3 Build
Fixed in Git Commit Github Pull Request #
Summary 00939: rjammer: Various graphic errors
Description Unfortunately, Roller Jammer got worse with the tubep.c update: now there are various new bugs that weren't in MAME version x, with x equivalent to 0.120u4 > x > 0.101:

1) Enemies sometimes flicker in and out very fast, like a weird raster effect (watch the 2nd runthrough of the attract mode)

2) Enemies far ahead on the road do not show up

3) Signs on the sides of the road rarely appear

4) The last "R" in "JAMMER" on the title is wrong, it's not completely filled in (I can get screenshots of this compared to 0.101 if needed)

5) Enemies start out as blue (1st round enemies), then turn to maroon (2nd round enemies) 2/3 of the way into the attract mode (they're constantly maroon in the attract mode in 0.101)
Steps To Reproduce
Additional Information
Github Commit
Flags
Regression Version 0.101u5
Affected Sets / Systems rjammer
Attached Files
gif file icon Roller Jammer 0.61-0127u2 - Wrong Title.gif (2,786 bytes) Sep 8, 2008, 20:51
gif file icon Roller Jammer 0.61-0127u2 - Missing GFX.gif (8,346 bytes) Sep 8, 2008, 20:51
Relationships
There are no relationship linked to this issue.
Notes
4
User avatar
No.02412
M.A.S.H.
Senior Tester
Sep 8, 2008, 20:53
> Enemies sometimes flicker in and out very fast, like a weird raster effect (watch the 2nd runthrough of the attract mode)

No flicker anymore.

> Enemies start out as blue (1st round enemies), then turn to maroon (2nd round enemies) 2/3 of the way into the attract mode (they're constantly maroon in the attract mode in 0.101)

Can't find any maroon enemies.
User avatar
No.07237
hap
Developer
Feb 19, 2011, 17:17
It's (still) broken as described in the description. Disregard MASH's comment.
User avatar
No.07239
Tafoid
Administrator
Feb 19, 2011, 19:44
Freshly built binaries of the 0.101u's indicate 0.101u5 is the culprit.
User avatar
No.07242
hap
Developer
Feb 19, 2011, 21:36
cause: It hits some invalid opcodes in m6800.c. In 101u5, timing for those was increased from 0 to 99 cycles per opcode, to prevent infinite loops. That's a bit over the top :P .. changed 99 to 5 now, and rjammer works again.