Nintendo 64

• Accepted ROM formats: .z64 .n64 .ndd .v64 .zip .7z
• Folders: /userdata/roms/n64 /userdata/roms/n64dd

The N64 emulators don't need a BIOS to function.

However, if intending on playing N64DD games specifically, the following BIOS file is required:

MD5 checksum	Share file path	Description
	bios/Mupen64plus/IPL.n64	N64 Dynamic Disk Initial Program Loader for Mupen64Plus
8d3d9f294b6e174bc7b1d2fd1c727530	bios/64DD_IPL.bin	N64 Dynamic Disk Initial Program Loader for Parallel-N64

Place your Nintendo 64 and N64DD ROMs in /userdata/roms/n64/.

File extensions may not necessarily reflect their true contents, but here are the generally accepted formats:

There is no practical difference as to which format to use for loading the ROMs in Batocera.

RetroArch has its own page.

Mupen64Plus-Next is a N64 emulation library for the libretro API, based on Mupen64Plus. It is also the successor of the old Mupen64Plus libretro core. It's still experimental, but incorporates Retroarch's features, such as input remapping from its Quick Menu ([HOTKEY] + ).

This is the only emulator in Batocera capable of playing N64DD games.

Standardized features for this core: n64.autosave, n64.cheevos

Other configuration settings must be configured from RetroArch's Quick Menu ([HOTKEY] + ).

A low level emulator that incorporates the Angrylion RDP renderer and Vulkan APIs for hardware accelerated emulation. It is more accurate but lacks some enhancement options.

Standardized features for this core: n64.autosave, n64.cheevos

Other configuration settings must be configured from RetroArch's Quick Menu ([HOTKEY] + ).

A standalone N64 emulator. Can utilize multiple plugins for various aspects of its emulation. For Batocera's purposes, each “core” can also be a different video plugin of the same emulator.

• “Mupen64Plus: GLide64mk2” for the enhanced GLide64mk2 video plugin.
• “Mupen64Plus: GLideN64” for the GLideN64 video plugin. Allows the use of hi-res texture packs.
• “Mupen64Plus: Rice” for the Rice video plugin. Allows use of hi-res texture packs.

Standardized features available to all cores of this emulator: n64.videomode, n64.videomode, n64.bezel, n64.bezel_stretch, n64.hud, n64.hud_corner, n64.bezel.tattoo, n64.bezel.tattoo_corner, n64.bezel.tattoo_file, n64.bezel.resize_tattoo

Mupen64Plus standalone cannot ordinarily be configured by altering its CFG file in userdata, as that gets overwritten every launch. If you're feeling adventurous, you can edit the /usr/share/batocera/configgen/configgen-defaults-arch.yml and utilize Batocera's overlay feature to keep the settings. Support cannot be provided should you do this, however.

Hi-res texture packs replace the textures in a game with other (typically higher resolution) textures. Support for this has been baked into Mupen64 ever since textures could be extracted from the game itself and naturally Batocera supports their use. The “MUPEN64PLUS / GLIDE64MK2”, “MUPEN64PLUS / RICE” and “LIBRETRO / MUPEN64PLUS-NEXT” emulators support this feature.

The author of the texture pack will usually include instructions on how to install them on standalone Mupen64Plus, but in case they don't here are the general steps:

1. Grab your texture pack and put it in /userdata/system/.local/share/mupen64plus/hires_texture/ (for .htc that would be …/mupen64plus/cache/ instead).

   Bug: For some reason this path is actually /userdata/bios/mupen64plus/cache/ instead.

2. Go to ADVANCED GAME OPTIONS in EmulationStation and enable HIRES TEXTURES. This something you can enable on a game per game basis, when you have the corresponding texture pack.
3. HD bing bing wahoos!

Texture packs can be very heavy (several hundreds of MB) and have an impact on the emulation performance if your system is on the lower side of the spectrum.

Some good places to start searching for N64 texture replacements:

• Batocera Nation's download page (scroll down to "HD Texture Packs for Nintendo 64"). These packs are already in a ready-to-go format.
• The "Completed Projects" page on the Emutalk forum. Most packs include installation instructions written by the author. Do note that this comes from the perspective of using the standalone emulators, and not all texture packs may support their libretro equivalents.
• Emulation King's N64 section (scroll down to "N64 Texture Packs") is another good, organised resource, however it usually excludes the author's installation instructions on the website itself. A lot of texture packs do feature readmes on how to use them, though.
• You may find some on the romhacking.net forum, however it's not organized per platform.
• The Texture Packs subreddit is a good place to discuss and share texture packs.
• The Game Upscale subreddit is similar but focuses more on upscaling the existing content with sophisticated AI instead of redrawing it or doing it in a different style. You can browse for just the "finished" projects by using its tag.

You might also want to look into 60 FPS patches/codes for your game while you're at it. Batocera cannot provide support for such hacks if something goes wrong, though, so the first step you should do if something goes wrong is to try it without the patch/code!

As of V38 many N64 style controllers are already mapped for you out of the box. If your controller is not refer to the information below to map inputs according to your controller type.

For V37 and older if using a N64 style controller you'll have to manually map inputs in ES and then remap in Retroarch and save a core remap and/or manually edit the Mupen64Plus input.xml file.

Remapping the controls as necessary in RetroArch's Quick Menu:

←-

Here are the default Nintendo 64's controls shown on a Batocera Retropad for libretro cores:

Here are the default Nintendo 64's controls shown on a Batocera Retropad for Mupen64Plus:

If instead you'd like to change the way that Mupen64Plus handles the inputs sent from ES/Batocera, you can change its remapping configuration.

Unlike with the libretro core, remaps for standalone Mupen64Plus can be configured by editing userdata/system/configs/mupen64/input.xml. Back up this file before making edits to it. When you open it, you'll see the bindings like so:

<inputList>
<input name="AnalogDeadzone" value="0,0" />
<input name="AnalogPeak"     value="32768,32768" />
<input name="l3"             value="Mempak switch" />
<input name="r3"             value="Rumblepak switch" />
<input name="a"        	     value="C Button R" />
<input name="b"        	     value="A Button" />
<input name="x"        	     value="C Button U" />
...

The input names on the left are the virtual Retropad Batocera uses to convert your controller inputs. You don't typically need to edit these.

The values on the right are the controller signal sent to the game. Feel free to switch these around with each other.

Turn off any upscaling settings such as increasing the rendering resolution. By default, Batocera will not be using any upscaling settings.

This issue affects Batocera v35 on RK3326-based images such as the Odroid Go Advance.

If the Quick Menu has missing text and RetroArch notifications look like multi-colored boxes like this:

Then try going to ADVANCED SYSTEM OPTIONS → GRAPHICS API and set it to “OPENGL”.

For further troubleshooting, refer to the generic support pages.