Skip to content

Nintendo 64
RetroBat system n64
Games go in roms\n64
BIOS None
Tested rows Platforms lists each emulator and whether it passed

Which emulator to use

Leave RetroBat on its default, RetroArch with the Mupen64Plus-Next core. Every emulator RetroBat offers for the Nintendo 64 passed RomMBat's tests, so any of them is safe to pick, with the Controller Pak setting below.

BIOS

The Nintendo 64 needs none, and RetroBat lists none. Every emulator starts a game without one.

Saves

A save follows you to another emulator only where the two read the same file (Changing emulator). On the Nintendo 64:

  • RetroArch's Mupen64Plus-Next and ParaLLEl N64 cores share one save.
  • Rosalie's Mupen GUI (mupen64) and simple64 share another.

The rest each keep their own, apart from BizHawk's two cores, which clash (below).

The Controller Pak

Four emulators start with no Controller Pak plugged in: RetroArch's ParaLLEl N64 core, Rosalie's Mupen GUI, and BizHawk's Ares64 and Mupen64Plus cores. A game that saves to the pak, such as Mario Kart 64's ghosts, saves nothing there until you plug one in. Set P1 Controller Extension to Memory, or Memory Pack, in the system's settings (Game settings, then Per system advanced configuration). RomMBat syncs the pak with the game's save.

Known issues

  • Switching between BizHawk's two cores loses the save on this device. Ares64 and Mupen64Plus write the same file in different formats, and each replaces the other's. The copy RomM holds from before the switch is what remains of it.
  • No game that saves to FlashRAM, one of the kinds of cartridge save, has been tested on any emulator. RetroArch's two cores and BizHawk's Mupen64Plus keep it in the one file they sync; on the other emulators its save may not sync.