Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
01998 Crash/Freeze Critical (emulation) Always Jul 11, 2008, 02:25 Nov 25, 2008, 15:03
Tester denzilla View Status Public Platform MAME (Official Binary)
Assigned To Resolution Fixed OS Windows XP/Vista 64-bit
Status [?] Resolved Driver
Version 0.126 Fixed in Version 0.128u4 Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 01998: crkdown: Player explodes as soon as game starts.
Description Player dies repeatedly once a game has started. crkdownj and crkdownu do not have this problem.
Steps To Reproduce Simply map your controls and begin a game. Its reproducible 100% of the time.
Additional Information This was fixed in 0.128u4 by simply replace the known corrupted set with a new World version of Crackdown.
Github Commit
Regression Version 0.119u3
Affected Sets / Systems crkdown
Attached Files
There are no relationship linked to this issue.
User avatar
Jul 11, 2008, 02:49
edited on: Jul 11, 2008, 02:50
This set (which was added in 0.119u3 - crkdown moved to crkdownu) has always acted this way. You can also see the high score list has the first 3 entries 0'd out - makes me think there are mapping or other memory issues?
User avatar
Jul 11, 2008, 04:34
This happens only in parent set but you can fix it in test mode (press F2). Select the 4th option by presing "service button" (button 9) and then F2 twice. You can see the time limit set to 0. Press the fire button to change the value. Notice that if you set it to 2m30sec it's turning green which means that's the default value. In the clones its already set to that value so the bomb doesnt explode on start.
User avatar
Senior Tester
Jul 11, 2008, 09:43
the settings track on the disc is corrupt (blanked out) and the game doesn't restore it properly unless you do it manually in test mode, it should probably be fixed.
User avatar
Senior Tester
Nov 25, 2008, 04:12
Can this bug be removed? I don't see any Player explosion.
User avatar
Senior Tester
Nov 25, 2008, 14:15
i replaced the disk image with a correct version, so no, it doesn't happen anymore unless you use the corrupt image.