Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
08551 Crash/Freeze Critical (emulation) Have not tried 11 days ago 2 days ago
Tester mamefan View Status Public Platform MAME (Official Binary)
Assigned To Resolution Open OS Windows 10/11 (64-bit)
Status [?] Acknowledged Driver
Version 0.251 Fixed in Version Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 08551: darkadv: Map screen display issue & freeze
Description During levels when the map is supposed to appear, it flashes briefly on-screen but isn't visible for any length of time. This seems like a bug, unless I'm doing it wrong. You can see it happen here

More importantly, on a level where the map is not supposed to appear (some levels, such as Metropolis, are that way intentionally), the game freezes. You can see it happen here
Steps To Reproduce
Additional Information
Github Commit
Flags
Regression Version
Affected Sets / Systems darkadv
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
4
User avatar
No.21020
Foxhack
Tester
11 days ago
edited on: 11 days ago
For the first part, you have to *hold down* the button to keep the map visible. According to the flyer, you can only use the map in certain worlds, so the freeze shouldn't happen. https://flyers.arcade-museum.com/?page=flyer&db=videodb&id=273&image=2
User avatar
No.21021
mamefan
Tester
11 days ago
From what I recall, holding down the start button didn't work either.
User avatar
No.21022
mamefan
Tester
11 days ago
Confirmed that holding down start does nothing. When you let go of start, it briefly flashes the map.
User avatar
No.21047
Tafoid
Administrator
2 days ago
I played it a couple times, progressing through 2-3 exits each time, the start button for me (default map "1"), when held, shows what is known on the map. Sometimes when you haven't progressed in a level, this will show partially or full blank. I was not able to get it to crash MAME or hang up the emulation in any way in my tries. It also did not disappear on me.

I'd suggest that the OP play and record the inputs (using "-record game.inp" in command-line) so that if they encounter this emulation issue again, all the exact inputs would help us reproduce.

I'll acknowledge for the time being.