- --
Viewing Issue Advanced Details
| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 09395 | Graphics | Minor | Always | 11 hours ago | 11 hours ago |
| Tester | hap | View Status | Public | Platform | MAME (Official Binary) |
| Assigned To | hap | Resolution | Fixed | OS | |
| Status [?] | Resolved | Driver | |||
| Version | 0.286 | Fixed in Version | 0.287GIT | Build | |
| Fixed in Git Commit | 2c9b220 | Github Pull Request # | |||
| Summary |
|
||||
| Description |
It occasionally writes wrong tiles to the background tilemap. If you're unlucky, it will create glitchy obstacles, basically an instant gameover. It looks like it's timing related, increasing the Z80B clocks gets rid of the bug. |
||||
| Steps To Reproduce |
Play the game (good enough to get to stage 3 or 4), and it'll usually happen at least once. An easier way to repro on 0.286: boot sprcros2, hold INS to fast forward and wait for the 3rd demo sequence. The biker will collide with a glitchy obstacle until the time runs out. This easier method won't work on 0.287 if you clock the Z80s at 2.5MHz. |
||||
| Additional Information |
Already fixed, I just want this bug documented. Fixed here: https://github.com/mamedev/mame/commit/2c9b22082852dd888361ed5f5bb4ecfa0ea72623 Additional (unrelated) fixes here: https://github.com/mamedev/mame/commit/88d3d5fde04e046ef02a5f89f4e93cdd6e7d791b Regressed when the MAME driver had a big refactor in order to transfer copyright ownership, which was necessary because of an incompatible source license. |
||||
| Github Commit | |||||
| Flags | Regression | ||||
| Regression Version | 0.172 | ||||
| Affected Sets / Systems | sprcros2, sprcros2a | ||||
|
Attached Files
|
attract mode
| ||||
Relationships
| There are no relationship linked to this issue. |
Notes
0
| There are no notes attached to this issue. |