nesdev.com

Hmm, try to categorize: 1) novelty emulator made in mIRC script, outputs graphics on a channel with multiple users to prevent flooding, still very slow 2) emulator that uses several hardware components for some chips (like HardSID support in VICE) 3) emulator designed to reproduce hardware bug-for-b...

Could you try it and pay attention to the statusbar to see if it occasionally shakes? (1 pixel downward and up again). If it does, you'd make an emu-author/perfectionist happy

Welcome.
yes, I've seen it happen on my NES.

Thanks for the test roms blargg.
(small typo by Disch 3 posts above me, nmi_during_brk 1st line "27 30 00" should of course be "27 36 00")

I like it, I got errors with cpu.nes on AB ATX, 9C SYA, 9E SXA. I was able to fix ATX by ORing A with $FF, according to documents it's ORed with $EE, $EF, $FE, or $FF depending on CPU internal state like the program counter. Maybe on the NES it's always ORed with $FF, at least it makes your test pro...

also, whats the deal with the Paperboy glitch where the game boots fine but the controller won't work?

Paperboy expects bit 6 to be set when reading the controller state, this is due to open-bus behaviour, effectively ORing the value with $40.

no

NerveGas wrote:nope something else is hosey.

Does Gauntlet (1) work then? If it doesn't, you've probably got a bug in your 4-screen-mirroring handling.

mmc3 doesn't serve out of video ram right? that's just map 119?

some games, like Megaman 4.

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.

Welcome Vegenad. Programming a NES emulator in Java can be done, your deadline is fine, and your general knowledge (even if it's not much) of hardware is a plus. Not knowing how the NES works on a low level doesn't matter, that's where you'll start: researching and lots of reading. What I was wonder...

Nice demo I like the synthetic voice.

It's a pity though that knowing the NES inside out takes away most of the impressiveness for us.
*edit* peppers: run it on PAL mode.

Maybe Nestopia calculates the aspect ratio based on NTSC_OUT_WIDTH from blargg's NTSC library, which width is about 3% too wide in favour of optimisations. (it's what Sega Li does, with a bit too wide square as result) *edit* Anyway, nice test tepples, and I agree with: Nestopia is probably within t...

Maybe its timer runs at cycles of 1ms?
What does BPS_TO_TIMER(x) do?

Can you make an image that is visible with RGB, invisible with NTSC?

To output "failed" if that test is ran with RGB? If it's not possible, it could just output "tv test failed", and add a "not" for NTSC.

2) I have a number of these carts that have batteries but don't appear to have any WRAM at all!? Is it possible they are saving game data to this internal VRAM instead of using it for video purposes? FWIW, I know that at least 1 game (Kaijuu Monogatari) uses the on-chip sound (wavetable) RAM for it...