In Nestopia, whenever I do a soft reset in most games that use mapper IRQs, mapper IRQs never trigger until a hard reset or a new game is loaded. MMC5 IRQs are fine, but MMC3 and some other mappers' games have this problem. So maybe MMC3-style IRQs are causing these problems? I'm using the latest version, 1.37, for Windows.
MMC3 IRQs should still work after a reset, so it's probably just an emulator bug, you can notify the author on the
Nestopia forum.
Heh, sorry to bump this topic, but I was just now worrying about this, because I was testing my game with Nestopia, and it does have problems (IRQs don't fire) after a soft reset. However, this does happen with many (all?) other MMC3 games, as stated by strangenesfreak, so it probably is just a bug with the emulator. It's been a while since the last release of Nestopia, hasn't it?
tokumaru wrote:
Heh, sorry to bump this topic, but I was just now worrying about this, because I was testing my game with Nestopia, and it does have problems (IRQs don't fire) after a soft reset. However, this does happen with many (all?) other MMC3 games, as stated by strangenesfreak, so it probably is just a bug with the emulator. It's been a while since the last release of Nestopia, hasn't it?
Yes. Pretty unfortunate too, because IMO that is a
very nasty bug that should have been fixed a while ago. It hurts Nestopia's accuracy for testing MMC3 homebrews, especially when there's a difference between hard and soft resets. :/
- Wait for RockNES' MMC3 fully working and your problems will be history!
![Wink ;)](./images/smilies/icon_wink.gif)
Hahahaha! OK! =)
The thing is that Nestopia is my emulator of choice for playing only. It's interface is good, it has blargg's NTSC filter implemented, and I find it a pretty decent emulator to play games on.
This is why it is in my list of emulators to use when programming, and I expected my game to run fine on it. Well, it does, so far, it's just the soft reset thing, but that happens to all MMC3 games, it seems.
Marty has fixed the bug for the next version. I think the reason it hasn't come out yet is because of the work he's doing with XML-based ROM image info (which is apparently just about completed). I also wish he released an update to fix this and other issues long ago, but I'm not the developer, so I don't control this.
My Nestopia works all right, I have version 1.35.
Bregalad wrote:
My Nestopia works all right, I have version 1.35.
Until a new release fixes the problem, you might want to preserve your version, because AFAIK, the latest version 1.37 is the only version that suffers from this problem.