Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06901 Crash/Freeze Major Always Mar 6, 2018, 10:41 27 days ago
Tester Gryzor1363 View Status Public Platform MAME (Unofficial Binary)
Assigned To Resolution Open OS Windows Vista/7/8 (64-bit)
Status [?] Confirmed Driver snes.cpp
Version 0.195 Fixed in Version Build 64-bit
Summary MESS-specific 06901: snes [jdredd and clones]: Judge Dredd (all regions) stops working after title screen
Description Upon launching the game, emulation stops working after first title/copyrights opening screen.
Steps To Reproduce Select SNES machine, then input game "Judge Dredd" as cartridge, wait for initial title screen to fade, then the persistent black-screen should occur every time. Issues is reproducible in all regions available (US, Europe, Japan).
Additional Information Bugs observed using MameUI64 0.195 official build to launch systems / games. Noteworthy is that game worked from MAMEUI64 0.187 up until MAMEUI64 0.193 as per personal testing, albeit with video corruption in status info bar in the upper section of the screen. (colours corrupt/garbage on icons). Issue not initially reported since SNES driver has a "Video emulation is not 100% accurate" pop-up.
Flags
Regression Version 0.194
Affected Sets / Systems snes [jdredd and clones]
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
8
User avatar
No.16148
Gryzor1363
Tester
Feb 15, 2019, 17:17
Behavior seems persistent after testing on latest MAMEUI64 0.206.

Please also note that similar behavior has been found in Cliffhanger (All Versions). Title screen works, and then a black-screen prevents further actions.
I will dedicate separate ticket for it if confirmed and required.
User avatar
No.16149
Osso
Developer
Feb 16, 2019, 09:05
The clock change in https://git.redump.net/mame/commit/?id=6b0f14ed7ba4eb854f4f9ff67112e88ef6589c74 caused the regression, while fixing a lot of other things, apparently.
User avatar
No.16150
Gryzor1363
Tester
Feb 16, 2019, 14:23
Thanks for the heads-up. So you confirm similar regression in both games are related to this root-cause ? should I raise a clone ticket for Cliffhanger in this case ?
User avatar
No.16151
Osso
Developer
Feb 16, 2019, 14:45
If they share the same regression, it's not necessary to open another bug report.
User avatar
No.16153
Gryzor1363
Tester
Feb 17, 2019, 12:56
Duly noted. AFAIK they share the same dysfonction, "symptomatically", while I do not know of previously working versions of MAME for this game prior to the regression.
User avatar
No.16320
AmatCoder
Tester
Apr 10, 2019, 23:48
AFAIK, spc700 runs at 2048 Mhz but it has internal divider.
This is the cause of the inconsistency between docs: The actual clock input is 2.048MHz but the effective clock rate is 1.024MHz.
User avatar
No.16339
Gryzor1363
Tester
30 days ago
Thanks for the usual quality input AmatCoder. Any chance it can be fixed in the coming releases ?
User avatar
No.16352
AmatCoder
Tester
27 days ago
If you ask to me... I don't know.

IMHO this would need revert the clock change (or apply the internal divider to cpu cycles).
It will break "Rival Turf / Rushing Beat" again but I believe that it is an issue with 5A22 cpu master cycles.

Moreover, I can confirm that "Cliffhanger" is broken by this issue (also "Taekwon-Do" and "Super Tekkyuu Fight!").