Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06433||Crash/Freeze||Critical (emulation)||Always||Nov 19, 2016, 13:26||Jan 5, 2019, 06:25|
|Tester||EoceneMiacid||View Status||Public||Platform||MAME (Self-compiled)|
|Assigned To||AJR||Resolution||Fixed||OS||Windows Vista/7/8 (32-bit)|
|Version||0.179||Fixed in Version||0.201||Build||64-bit|
|Fixed in Git Commit||Github Pull Request #|
|Summary||06433: mrheli: Game freezes in the first stage|
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|
|Affected Sets / Systems||mrheli|
|There are no relationship linked to this issue.|
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)|
Nov 25, 2016, 00:49
|The MCU image was added in 0.160 and that is when the emulation hanging began.|
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)
Jan 5, 2019, 02:28
Fixed in mame 0.201
0.201: Overhaul V30/8751 comms using DPRAM and GENERIC_LATCH_8 [AJR].