I mean. The game in MAME using the emulation of the encryption doesn't have the bug, so the problem is maybe the hacked roms. Do you have the game or can you test what I'm saying with a board? I'm going crazy with this issue, xD.
Anyone who has a SegaSonic conversion can confirm the bug I am having with 2 converted boards?
I don't have this game, but i created patches for other System32 games so i know how the protection works.
Mame doesn't "patch" the protection, it emulates the protection instead. So when the game loops and it checks the protection, it's OK.
I'm now assuming the game does a check when it goes to the second loop.
I do not have the game, and did not do the patches for this one. Looking into mame source, they have fully emulated the protection at this point instead of catching the reads/writes.
In older source there was protection hacks in place to catch the reads/writes but i can't seem to find which one. (they now emulate an additional nec V25 cpu.)
The older source is here: https://github.com/mamedev/mame/blo...fc4f169a25e8d539/src/mame/machine/segas32.cpp
I can see a calculation protection for the number of levels cleared and such, i guess this is not patched in your rom properly or something.