Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06249||Crash/Freeze||Critical (emulation)||Always||Jun 19, 2016, 11:26||Jun 20, 2016, 18:43|
|Assigned To||Resolution||No change required||OS||Linux (64-bit)|
|Version||0.174||Fixed in Version||Build||64-bit|
|Summary||06249: mf_bdash: Game freezes|
The game freezes after a series of sound beep.
Personally I have encountered the bug playing the third stage but I suppose it's random.
It's related to bug 03851 but not solved.
|Steps To Reproduce|
|Affected Sets / Systems||mf_bdash|
|There are no relationsihp linked to this issue.|
Jun 20, 2016, 17:02
is this really a bug, or is it giving you the chance to insert more coins to regain your controls?
the games are just home computer / console games with an MCU controlling a lock-out / reset timer, so the described behavior actually makes sense.
Jun 20, 2016, 18:25
This is correct. As far as I can tell, starting at 15 seconds left, the beeps begin with increasing frequency (pitch) every second until your timer hits 0. The digits for hundreds and tens do not seem to erase to 0/show 0 after counting down.
There is a TODO in the source which explains this:
TODO:Even if it might say 110 left, it could be 0 time. The time is being counted off accurately as far as I can tell, just not displaying properly.
I'm not at all convinced there is any type of freeze or hang outside of what is supposed to happen in a timer-based game and outside of the known TODO, the game is functioning as expected.