At the very least the following games depend on hard-to-emulate or just obscure behavior:
- Abarenbou Tengu, Captain Tsubasa 2 and Rampart (U)
- These refer to CHR ROM banks outside their size. A CHR ROM of the correct size will wrap the addresses correctly by discarding the most significant bits, as do most emulators. But if you are developing a flash-cart that just pre-programs its flash/SRAM memory with the CHR ROM data without address wrapping, graphical bugs will happen. If you want to simulate that behaviour in emulator, increase CHR-ROM banks number in iNES header twice and paste zeros in the the CHR area.
- Adventures of Lolo 2, Ms. Pac-Man (Tengen), and Spelunker
- These rely on 1 cycle NMI delay when PPUSTATUS ($2002) bit 7 gets set inside vblank (if $2002 has not been read yet), in which PPUSTATUS bit 7 can be read as true.
- Balloon Fight
- It reads the nametables through PPUDATA ($2007) to twinkle the stars in the background. (The code is at $D603.) The scroll split in "Balloon Trip" also depends to an extent on the correct number of CPU cycles from the start of NMI to the start of display, but it's not particularly picky.
- Bases Loaded II
- The screen glitches after a pitch is thrown (screenshot) if writing $00 then $80 to PPUCTRL during vertical blank does not cause an additional NMI.
- Infamous among emulator developers for requiring fairly precise CPU and PPU timing (including the cycle penalty for crossing pages) and a fairly robust sprite 0 implementation. Because it continuously streams animation frames into CHR RAM, it leaves rendering disabled for a number of scanlines into the visible frame to gain extra VRAM upload time and then enables it. If the timing is off so that the background image appears too high or too low at this point, a sprite zero hit will fail to trigger, hanging the game. This usually occurs immediately upon entering the first stage if the timing is off by enough, and might cause random hangs at other points otherwise.
- Battletoads & Double Dragon and Low G Man
- They read from WRAM at $6000-$7FFF despite there being none on the cartridge, relying on the values produced by open bus behavior. If WRAM is present, some pre-loaded values will cause BT&DD to crash at the end of stage 1 when Abobo makes his first appearance and LGM to crash when playing boss music.
- Bee 52
- This needs accurate DMC timing and relies on PPUSTATUS bit 5 (sprite overflow) as well
- Bill & Ted's Excellent Adventure and some other MMC1 games
- These depend on the mapper ignoring successive writes; see iNES Mapper 001 (the talk page for that page might be informative too). Bill & Ted also turns off and re-enables rendering midframe to switch CHR banks (such as in the black border above dialog boxes).
- Burai Fighter (U)
- It accesses PPUDATA during rendering to draw the scorebar. Incorrect emulation clips the scorebar to half size. See the notes on accessing PPUDATA during rendering on the PPU scrolling page.
- B-Wings, Krusty's Fun House, and Trolls in Crazyland
- They write to CHR ROM and expect the writes to have no effect.
- Cobra Triangle and Ironsword: Wizards and Warriors II
- They rely on the dummy read for the
sta $4000,Xinstruction to acknowledge pending APU IRQs.
- Crystalis, Fantastic Adventures of Dizzy, Fire Hawk, Indiana Jones and the Last Crusade, and Super Off Road
- These do mid-frame palette changes.
- Fire Hawk, Mig 29 Soviet Fighter, and Time Lord
- These need accurate DMC timing because they abuse APU DMC IRQ to split the screen.
- Requires proper handling of bit 4 of the P register for /IRQ.
- G.I. Joe and Mickey in Letterland
- These turn sprite display off and leave the background on. Correct timing of MMC3 IRQs requires that the sprite fetches still clock the scanline counter when either is enabled.
- Huge Insect
- Depends on obscure OAMADDR ($2003) behavior in the OAM DRAM controller; see PPU registers.
- The Magic of Scheherazade
- It maps two non-contiguous PRG ROM pages next to each other, then executes code across the page boundary. Emulators which use pointers to fetch sequential instruction bytes from ROM will fail when taking damage in the RPG-style battles. (Use password
5Wto test this easily)
- Marble Madness and Pirates
- These switch CHR banks mid-scanline to draw text boxes (such as at the beginning of each MM level). Getting these to render correctly requires fairly precise timing.
- Micro Machines
- Requires correct values when reading OAMDATA ($2004) during rendering, and also relies on proper background color selection when rendering is disabled and the VRAM address points to the palette (see the "background palette hack" on PPU palettes).
- Relies on the open bus behavior of controller reads and expects them to return exactly 0x40 or 0x41; see Standard controller.
- MMC2 snoops PPU fetches. If the PPU does not fetch the 34th tile, the ring will be glitched.
- Puzznic and Reflect World (FDS)
- These use unofficial opcode $89, which is a two-byte NOP on 6502 and BIT #imm on 65C02. (Puzznic tasvideos discussion) The instruction in Puzznic is 89 00; emulating $89 as a single-byte NOP will trigger a BRK that causes the screen to shake.
- Does a JSR while the stack pointer is 0, so that half of the return address ends up at $0100 and the other half at $01FF.
- Super Mario Bros.
- This is probably the hardest game to emulate among the most popular NROM games, which are generally the first targets against which an emulator author tests his or her work. It relies on JMP indirect, correct palette mirroring (otherwise the sky will be black; see PPU palettes), sprite 0 detection (otherwise the game will freeze on the title screen), the 1-byte delay when reading from CHR ROM through PPUDATA (see The PPUDATA read buffer), and proper behavior of the nametable selection bits of PPUSTATUS and PPUADDR. In addition, there are several bad dumps floating around, some of which were ripped from pirate multicarts whose cheat menus leave several key parameters in RAM. If you're looking for a good first game for your new emulator, try anything made in 1984 or earlier, such as Donkey Kong.
- Super Mario Bros. 3, Double Action 53, and Haunted: Halloween '86: The Curse of Possum Hollow
- This relies on an interaction between the sprite priority bit and the OAM index to put sprites behind the background. SMB3 uses it for powerups sprouting from blocks. RHDE: Furniture Fight in DA53 uses it for characters behind furniture. HH86 uses it when Donny or Tami passes behind a telephone pole or steps into polluted water.
- Teenage Mutant Ninja Turtles
- Uses Y scroll values greater than 239, causing the PPU to read the attribute table as nametable data before looping back to the same nametable instead of rolling to the next nametable down.
- Time Lord
- This is sensitive to the power-on state of the NES. The Vblank flag in PPUSTATUS must be set for the first time within 240 scanlines, otherwise there will be a frame IRQ which is never acknowledged, which will mess up the DMC IRQs used elsewhere and cause the game to crash.
- Wizards and Warriors 3
- It writes new tile graphics for the sprites at the screen split after the sprites have been drawn, but before the frame has ended. Emulators which draw the sprites all at once using graphics data from the end of the frame will have glitches in the main character's sprite.
- The Young Indiana Jones Chronicles and Zelda II: The Adventure of Link
- These accesses PPUDATA during rendering to perform a glitchy y scroll. Young Indy uses it to make the screen shake when cannon balls hit the ground, and Zelda II uses it to skip scanlines on the title screen. See the notes on accessing PPUDATA during rendering on PPU scrolling page.
If a scroll split doesn't work, and a garbage sprite shows up around the intended split point, then the game is probably trying to use a sprite 0 hit, but either the wrong tile data is loaded or the background is scrolled to a position that doesn't overlap correctly. This could be a problem with nametable mirroring, with CHR bankswitching in mappers that support it, or with the CPU and PPU timing of whatever happened above the split. Battletoads, for one, uses 1-screen mirroring and requires exact timing to get the background scroll position dead-on.
- Game bugs: These games have glitches on NES hardware, so don't go "fixing" them while breaking your emulator.
- Sprite overflow games
- Unofficial opcode games