I've done some testing and found out that the regression is mame 0.206
The bug is not present in mame 0.205 and previous versions.

No.16133

Haze

Senior Tester

9 days ago

edited on: 9 days ago

yeah this is very sensitive to MCU timing / comms, the slightest thing it doesn't like and it will randomly break on any one of the bosses when it wants data.

I had to play the thing extensively when the MCU was added to make sure it never failed, I guess somebody altered the code.

Tafoid, can you track down the exact revision and point whoever broke it at this report? bit annoying to see this regress after the time put into making sure it didn't crash.

No.16135

Osso

Developer

9 days ago

Couldn't get the attached save state to work with a current GIT build. I got to the boss with the invincibility cheat and didn't get the problem. Would it be possible for the original bug reporter to test this on a current GIT build (without cheats, of course)?

No.16143

Haze

Senior Tester

8 days ago

edited on: 8 days ago

it didn't *always* occur even when it was broken before, but it occurred often enough to be game-breaking usually occurring at least once in a run. I ended up running a stress test sending random inputs to loop the game through over and overagain to make sure it no longer crashed and ran it for some hours last time.

I guess it just frustrates me because a lot of work was put into making it work before, and that was just disregarded for what 'seems' better from a coding point of view, even if it doesn't work.