Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06433 Crash/Freeze Critical (emulation) Always Nov 19, 2016, 13:26 Nov 25, 2016, 01:27
Tester EoceneMiacid View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Open OS Windows Vista/7/8 (32-bit)
Status [?] Confirmed Driver m72.cpp
Version 0.179 Fixed in Version Build 64-bit
Summary 06433: mrheli: Game freezes in the first stage
Description Right before the first stage starts to scroll downward, the game freezes. Tried several times, happened every time.
Interestingly, the parent set (bchopper) works fine.
Steps To Reproduce Play the first stage for about two minutes
Additional Information
Flags
Regression Version 0.160
Affected Sets / Systems mrheli
Attached Files
 
Relationships
There are no relationsihp linked to this issue.
Notes
3
User avatar
No.13398
Haze
Senior Tester
Nov 20, 2016, 23:09
edited on: Nov 20, 2016, 23:10
almost certainly unhappy with the MCU hookup (they're highly sensitive to timing at the very least)

User avatar
No.13422
Tafoid
Administrator
Nov 25, 2016, 00:49
The MCU image was added in 0.160 and that is when the emulation hanging began.
User avatar
No.13424
Haze
Senior Tester
Nov 25, 2016, 01:27
yeah, the MCUs are meant to cause a bunch of values to be in RAM, the games check these are various points and misbehave if they're not correct.

I imagine a timing error is causing them to be written at the incorrect time and erased, or something like that (or the dump is bad and it writes the wrong value)