allowing mutiple nmi's breaks Ninja Gaiden

This is an archive of a topic from NESdev BBS, taken in mid-October 2019 before a server upgrade.
View original topic
allowing mutiple nmi's breaks Ninja Gaiden
by on (#31058)
i got my emulator to pass blarrgs nmi timing test by allowing multiple nmi's if the vblank flag is set. but that seems to break Ninja Gaiden and a few other games. removing the code that allows multiple nmi's fixes this problem but nmi timing fails with error 8.

ill have to look at it more, but kinda stumped. seems like its not clearning the vblank flag.

any suggestions ?

thanks

matt

by on (#31059)
Additional NMIs only happen when NMIs are being enabled from a disabled state ($2000.7 is going from 0->1). If the game enables NMIs when they're already enabled, nothing happens.

by on (#31060)
Disch wrote:
Additional NMIs only happen when NMIs are being enabled from a disabled state ($2000.7 is going from 0->1). If the game enables NMIs when they're already enabled, nothing happens.

Is the NMI page on the wiki correct?

by on (#31065)
Here's a more detailed test ROM that might help find the problem:

multiple_nmi.zip

by on (#31068)
Disch, thanks alot for that. you were right, i was not checking the transition, only either states of each.

tepples, cant remember if i read the wiki. i was searching the forums for nmi info, thought i read it there. guess not.

blargg, thanks for the test. all pass. your tests are still the best!!

thanks

matt

by on (#31136)
btw blargg, your test is missing the readme. when i was failing i had no way of knowing what the reason was. passed was kinda obvious.

matt

by on (#31138)
Quote:
when i was failing i had no way of knowing what the reason was. passed was kinda obvious.

Doesn't it print the reason as text on the screen, and also a code that you can look up in the source code?!? I only spent about half an hour writing that test ROM, and I figured the code and text would be sufficient. You should be clearer about what you're referring to, also. I usually don't get a very clear idea of what you're trying to communicate in your posts, and I hate having to guess since I'll often get it wrong and waste time answering the wrong question.

by on (#31140)
i checked again, and it only prints a number. unless there are more bugs with my nes and your test is supposed to.

i did not look at the source before, sorry. i looked at a few other files in the package.

sorry if am not clear in my post. i know some are better than others.

matt

by on (#31143)
Argh, an extra ! was disabling messages for normal builds. I fixed the original zip file; download again and try.

One thing to be clear about is which test you're referring to. At the very least, list the name of the test ROM (and the result code, when it's a problem with your emulator rather than my ROM). In this case, there was another NMI test ROM referred to in your original message, so I wasn't clear which you were referring to (old one or the new one I posted above).