I've already thought about that and I think the MMC5 version should work with an EWROM board. At least that's what I've decided to work with after giving v2.0 a good test on the EverDrive. It's so much easier to decide to make a repro at the drop of a hat since I've gotten a Famicom for my collection. Certain games are so much cheaper, obviously, and especially for acquiring repro donors it's a lot more viable :-)
Oh so you made the repro out of the MMC5 version after all?
That's neat to know, how well does it work?
I might do a repro of my own with the gold cart and all later on, if the MMC1 version gets fixed for proper real hardware.
Maybe it might be good to just go with the MMC5 patch set and exclude the MMC1 set on the main page until things can be sorted out.
Thing is, the MMC1 set does work perfectly on FCEUX.
It's other emus and real hardware that struggle with it.
I could probably add a note specifying that, but I'll wait a bit before doing that.
Another thing would be to add an optional patch exclusively for the MMC1 version which removes the Animation, and that would make it work on real hardware (I supposed).
Is anyone willing to test if solely removing the Animation from the MMC1 makes it work without issues on real hardware?
I'm trying to play through the MMC5 version of the latest 2.0, and it just hard locks up my system constantly. I'm playing on an Everdrive N8 Pro, in an AV Famicom with a HiDefNES mod kit installed. I've played through a bunch of games with this set up no problem. With this though any time I enter or leave a cave (shop or dungeon) there is a high chance for the game to hard lock. Like I have to reset the system hard lock.
I'm not sure what to respond.
I haven't heard of such an issue from any other issues at all, not even others playing in real hardware with the MMC5 version, so I don't know exactly where the issue could be. Are you using optional patches?
If you are, then try booting several ROMs, each with a different set of patches applied (one with Redux alone, one with Redux + 1 optional patch, another with Redux + another optional patch, etc.)
That could help know which feature is breaking it precisely.
I can't do much to test this out, as I have never experienced such a bug in any of my playthroughs with both versions.