Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
07964 Core Major Always May 3, 2021, 20:54 May 5, 2021, 00:27
Tester Cow View Status Public Platform MAME (Official Binary)
Assigned To Resolution Open OS Windows 10 (64-bit)
Status [?] Confirmed Driver hcastle.cpp
Version 0.231 Fixed in Version Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 07964: akumajoun: Getting on the High Score table does one of the following, all resulting in weird behavior
Description in Haunted Castle's Japanese N Version, Getting a high score either soft resets itself or slows down performance shown here:

Steps To Reproduce Play the game until you reach a score that gets on the high score table.

Added by Tafoid:
A quick way to do this is to run the game with -debug, start the game and when the game start, paste: maincpu.pb@1912=9
That will change your score to 90000 and you can just fast forward emulation letting you take damage to game over.
If someone needs a save state, I can provide one.
Additional Information the bug doesn't occur on any other clone. Only akumajoun
Github Commit
Regression Version 0.148u2
Affected Sets / Systems akumajoun
Attached Files
mp4 file icon Mame 2021.05.04 - (3,678,198 bytes) May 4, 2021, 20:33 Uploaded by Cow
Another reset
There are no relationship linked to this issue.
User avatar
May 4, 2021, 00:27
edited on: May 4, 2021, 21:03
Did some tracing first on release version then day by day and determine a strong probability for regression happening:
March 4, 2013

* Rewrite of 6809/6309/konamicpu cores. 6809 should be cycle exact based on the
6809 datasheet. Inferred 6309 cycle exact timings. Not sure about the Konami
timings; they are definitly different from the previous core but the previous
timings were a guess.
User avatar
May 4, 2021, 02:32
edited on: May 4, 2021, 02:44
Tested and the bug doesn't trigger on MAME 0.147. Couldn't find MAME 0.148u2 so I used 0.149 instead

User avatar
Senior Tester
May 4, 2021, 14:56
how strange, I wonder if it's actually a bug in this revision of the game (or if it's a bad dump that still passes the startup checks) would have come to light quickly if it ended up on location like this, but it's very strange it only happens in this set.
User avatar
Senior Tester
May 4, 2021, 22:53
the regression makes it all the more interesting
User avatar
May 5, 2021, 00:24
edited on: May 5, 2021, 00:32
huh. Once in a blue moon, the game actually doesn't bug out and plays normally after the high score screen and I accidently deleted the video.... Yipeeee