7 ms·

I've not done NES specifically, but I've written some emulators. As the pack-in game and a cultural landmark, I'd probably be targeting SMB 1 accuracy first an

I've not done NES specifically, but I've written some emulators. As the pack-in game and a cultural landmark, I'd probably be targeting SMB 1 accuracy first and foremost. It doesn't seem to do anything crazy like vertical scrolling, so my ignorant assumption would be that it'd be a good game to start with. > there are several bugs that need to be reproduced such as the oamaddr bug for example Given what I've heard about how pipes work, that sounds like a good place to start digging in. Do you have any specific references for that? I'd much rather hear first-hand experience rather than google results, since so much of early console hardware documentation is flat out wrong.

eyegor 7y ago
Unfortunately I do not, I've toyed around with small cpu architecture emulation and a touch of gameboy. The bug I was referring to is also called the sprite overflow bug. http://wiki.nesdev.com/w/index.php/PPU_sprite_evaluation http://wiki.nesdev.com/w/index.php/PPU_sprite_evaluation Edit: There's also a bit of documentation in one of the bizhawk nes cores: https://github.com/TASVideos/BizHawk/tree/master/BizHawk.Emulation.Cores/Consoles/Nintendo/NES https://github.com/TASVideos/BizHawk/tree/master/BizHawk.Emu...