Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement proper RAMBO-1 (mapper 64) IRQ counter behaviour #89

Closed
koitsu opened this issue Aug 12, 2014 · 6 comments
Closed

Implement proper RAMBO-1 (mapper 64) IRQ counter behaviour #89

koitsu opened this issue Aug 12, 2014 · 6 comments

Comments

@koitsu
Copy link
Contributor

koitsu commented Aug 12, 2014

It seems games using the RAMBO-1 (mapper 64) IRQ counter do not behave properly in Nestopia. This is understandable given that the difference between it and MMC3 has only recently (~past year) come to light and this information has not been commonly disseminated.

Full details: http://forums.nesdev.com/viewtopic.php?f=3&t=11525

Be sure to read the referenced link in that thread.

And some logic documentation, as well as a recommended alternate approach that might fix Hard Drivin':

http://wiki.nesdev.com/w/index.php/RAMBO-1
http://wiki.nesdev.com/w/index.php/Talk:RAMBO-1

@rdanbrook
Copy link
Member

Thanks for this issue report, I'll look into it soon.

@joepogo
Copy link
Contributor

joepogo commented May 23, 2016

Hey Koitsu, is this mapper related to tengen by chance?

@koitsu
Copy link
Contributor Author

koitsu commented May 23, 2016

Did you look at the nesdev wiki links provided in the original post? Please do.

@joepogo
Copy link
Contributor

joepogo commented May 23, 2016

Yea, shortly after I posted this, I did look it up. I see my shinobi ticket and the skull and crossbones are on the same mapper, so yesit is Def tengen related. :)

@joepogo
Copy link
Contributor

joepogo commented Aug 22, 2016

hey rdanbrook, any luck with this one? Ive been going back ad forth with dragon about it, but you know how that goes.

@rdanbrook
Copy link
Member

This is being handled in the jgemu repo.

@0ldsk00l 0ldsk00l locked as resolved and limited conversation to collaborators Feb 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants