RetroPie Setup Guide – Xbox 360 Controllers – ROMs

RetroPie Setup Guide

If you’re looking for a cheat-sheet to quickly setup a Raspberry Pi 3 Model B as a RetroPie emulation system, you’re in the right spot. Many of the guides you find, including the official RetroPie wiki, are outdated, between 2012-2015 before the release of RetroPie v4. This guide will eventually meet the same fate, but for now, it’s the newest, sweetest, down-and-dirty guide you’ll find. Enjoy!



  1. Parts
  2. Installing OS
  3. Updating OS
  4. Adding ROMs
  5. Configuring System (the long part)
  6. Performance Improvements
  7. Configuring Controllers
  8. ROM Compatibility per Emulator Plugin

Chapter 1 – Parts


Raspberry Pi 3 Model B

  • I highly recommend the Vilros kit, includes power cord, case, and board
    • $50

MicroSD Card

  • I got a 64GB SanDisk Class 10 MicroSD
    • $25 –
  • I recommend a minimum of 16GB, 32GB is the sweet spot for not having to worry about enough space. If you are planning at add countless MAME ROMs or PS1 games, you’ll want as big a MicroSD card you can get.

Official Microsoft Xbox 360 Wireless Receiver

  • Get the official Microsoft OEM version. There are third-party receivers that *can* work fine, but I’ve had bad experiences in the past. The official Microsoft labeled device works the best.
    • $20 –

Official Xbox 360 Wireless Controllers

  • $30/ea, you can find them anywhere. Best Buy Price Matching works too.


  • Any keyboard will work, for running more intense menu commands.

Case with Fan

  • If you are planning on playing N64 games, I highly recommend purchasing a vented Raspberry Pi case with fans so you can overclock the system, which is absolutely necessary for smooth N64 emulation. Below is what I use.

Chapter 2 – Installing OS

You’ll need a way to format the MicroSD card. This is usually done with the included SD Card (full size) adapter, and plugging it into a laptop/desktop/memory-card adapter.

Go download and install Win32DiskImager from Sourceforge. This lets you write a downloaded .IMG file directly to the MicroSD card.


Download RetroPie v4.X

  • The OS is about 600MB. They seem to choose random mirrors for downloads, some go at 30KBps, others at 20MBps, if it’s slow, cancel and re-download.

The image file will be a .img.gz (GZIP) file. Extract the .IMG file inside with 7Zip or WinRar to somewhere on your local PC.

Run Win32DiskImager from Start as Administrator (right-click > Run as Administrator)

Select the MicroSD card drive letter, browse to your extracted .IMG, and write. — This will completely erase the selected device (which should be the MicroSD card). Make sure it’s the right one.

Wait until the write is complete.

retropie write sd win32

Once complete, remove the MicroSD card, and connect it to the Raspberry Pi memory slot. Connect everything together:

  • MicroSD
  • 360 Wireless Receiver
  • Power MicroSD

Then connect the power-adapter to a power-strip/wall-jack.


Chapter 3 – Updating OS

Let the Raspberry Pi boot up and wait until you get to the main interface. You will need a controller input

Configuring Primary Controller for System

We need to define the base controller button definitions via Emulation Station. Start > Configure Input > Are you sure? > Yes

After mapping the buttons per the references below (picture included), we can then make any changes per-system as needed.

Reference 1:

Reference 2:


Note — You are intentionally Mis-Mapping the Xbox 360 Controller Buttons — this is intended.

For example, the Green button on a 360 controller, is being mapped to B for EmulationStation’s RetroArch default config. This is correct, it will make your life easier. From there — the buttons will be remapped again by each core (NES, SNES, Genesis) to match the “feel” of that controller — automatically. As an example, on a NES Controller, the B button is to the left of the A button. The “feel” should be the same — A (360 Button) > B (RetroArch Default Input) > Auto-Remapped to A (NES Controller).

It’s an odd system, but it can work really well as long as you follow the mapping below. Some emulators (looking at you N64 non-RetroArch cores Gles2N64 and Mupen64Plus) will require controller customization, as their mappings cannot load the built in RetroArch input file. (The default RetroArch input file is stored at “/opt/retropie/configs/all/retroarch-joypads/Xbox 360 Wireless Receiver.cfg”



Updating OS Packages

Updating the RetroPie OS and packages can provide a 80% performance improvement in some cases. Absolutely 100% do this step.

  1. Open RetroPie
  2. RetroPie Setup > Update RetroPie-Setup Script > Yes
  3. Update all installed packages > Yes > Would you like to update the underlying OS packages? > Yes
  4. Wait 25 minutes (I timed it)

That was easy enough…


Chapter 4 – Adding ROMs

If you’ve got the ROMs, it’s easy. Just remove them from their ZIP files, and copy them to a network share. If you don’t yet have ROMs, go find a torrent site and get your game on! Generally releases are call “ROM Collections” or “ROM Packs”, so for example go on Google and search for, “N64 ROM collection torrent”.

Hop on your PC, and browse your local network. If you can’t find anything and you’re on Windows, Start > Advanced Sharing > Enable Network Discovery

You can also find your IP on RetroPie by going RetroPie > Show IP

Then browsing to \\192.168.0.X\ or \\retropie


Go into the roms folder, and start copy/pasting in ROMs for each system. They will need to be unzipped, so a NES game would be something like: Super Mario Bros.NES, a N64 title would be Super Mario 64.z64, and a PSX game would be either a Crash Bandicoot.BIN/Crash Bandicoot.CUE combo, or a combined Crash Bandicoot.PBP file.


Chapter 5 – Configuring System (the long part)

Raspberry Pi Config

We are going to configure some core OS settings that have nothing to do with RetroPie. You will likely need a keyboard for this to work, controller buttons can go weird in Raspi-Config.

From the menus, open RetroPie > Raspi-Config

You can also open this by using Putty, SSHing in, and typing “raspi-config”.

  1. This step should not be necessary as of RetroPie v4, but if you find yourself running out of space much earlier than expected:
    1. Expand FileSystem”, this takes the 600MB image you flashed to the MicroSD, and lets you have all of the free space of your 64/128GB MicroSD card.
  2. Boot Options > Wait for Network at Boot > Would you like boot to wait? > NO
    1. This makes the Raspberry Pi boot MUCH faster if a network connection is not available. Otherwise you will sit for 30s while the Raspberry looks for a DHCP server and times out.
  3. Advanced Options > Overscan > Would you like to enable compensation for displays with overscan?
    1. Select No if you have a modern, 1080p or higher HDTV, or are on HDMI.
    2. Select Yes if you have an older TV that zooms in on devices so there are no black bars (but it cuts off detail with HDMI/DVI).

Disable Run Command Editor

Whenever you load a ROM, you have 5 seconds to press any button to load the Run Command Editor. That means if any person presses anything during those 5 seconds, time to pull out a keyboard or reboot the system to try again while everyone gets confused. I highly recommend turning this off if non-technical people or children are playing on the system, or to disable it once your system is dialed-in.

You will want to leave it enabled to select a per-game Emulator Core setting. For example, StarFox64 runs best under GlideN64. If GlideN64 is not your default, the Run Command Editor lets you select that specific game’s default emulator core, which the setting will keep even after you (later) disable Run Command Editor.

  1. Launch Menu > Disabled
  2. Launch Menu Art > Disabled
  3. Launch Menu Joystick Control > Enabled
  4. Select Cancel (should be named Quit or Exit) > A (or Yes).

Upgrade Theme

I personally prefer Tronkyfran (#32 at the bottom of the list), pick whatever you prefer 🙂

RetroPie Setup > Configuration / Tools > esthemes (Emulation Station User Interface themes) > 32 – Install Tronkyfran

Go back to home > Start > UI Settings > Theme Set (at the bottom) > Change from Carbon (default) to Tronkyfran (or whatever you use). Some themes may require a reboot to go into effect.

Scrape for Details

A scraper scans all of the games in your system for metadata like year of release, rating, description, title, cover-arts, etc. Very worth the time to run it, makes the system look MUCH prettier. For running an scrape of 2500 games, it took 3 hours to complete.

Do this after copying over your ROM files.

  1. Plug in a keyboard, hit F4 to close Emulation Station – if it is open, the scraping cannot succeed.
  2. sudo -i
  3. sh /home/pi/RetroPie-Setup/
  4. Configuration Tools > Scraper > Scan All Systems

Change Default N64 Emulator

This file lets you select the default emulator. You have the option to assign different emulators to different ROM files with the Run Command before a system launches. I have personally had better stability and performance with Gles2N64 than GlideN64. Officially, GlideN64 is supposed to be the best current graphical plugin and may one day be the best (isn’t everything linux like that though ;-). At the time of writing this (March 2017) glitchy graphics, stuttering audio, and random buggyness with GlideN64 says otherwise, so I recommend Gles2N64.

  1. sudo -i
  2. nano /opt/retropie/configs/n64/emulators.cfg
  3. Change the following line
    1. (Before) default = “mupen64plus-GLideN64”
    2. (After) default = “mupen64plus-gles2n64”
  4. Ctrl + X (Exit) > Y (Yes to save changes)

Chapter 6 – Performance Improvements

This is surprisingly important. I normally don’t overclock any equipment, ever, but overclocking really does make a massive improvement on your RetroPi setup, it’s the difference between some N64 games working great or being completely unplayable — if you want to play Goldeneye or Perfect Dark and have a good time, you’ll need this step.

These settings are for a Raspberry Pi 3 in a case with minor ventilation, and the cheapo 14mm x 14mm x 4mm heatsinks on top that come with cheap kits. If you’ve installed a large heatsink and fan, you can push the numbers farther. Watch out for the heat, check it with the Putty command:

#Check temperature. Hit Up-Arrow > Enter to keep checking.
vcgencmd measure_temp

The most important setting oddly enough, is the v3d_frequency. This seems to provide more performance improvements than anything else I’ve found. disable_splash=1 just speeds up the boot process.

  1. sudo -i
  2. nano /boot/config.txt
  3. Insert the below code:
  4. #Raspberry Pi - ACTIVE COOLING Only!! (40C idle, up to 55C under heavy load)
  5. #Raspberry Pi - Passive Cooling - Runs Hot (50C idle, up to 80C under heavy load)


This can be a tricky category. Different games run better, and look better, at different resolutions. The higher the resolution, the greater the process/performance demands on the RaspberryPi. In general, I’ve found it best to have the default video mode for any emulator to be 640×480 (CEA1). For example, even the emulator GLes2N64-HighRes, will look more “HD” running at CEA-1 (640×480) than say, CEA-4(1280×720) and run smoother on Jet Force Gemini. For GLes2N64, CEA-1 though a 4:3 resolution is scaled properly to fit a 1080p 16:9 display — it looks really good on many games!

Using the Run Command editor can be helpful for changing specific setting — per-ROM. To do so, you would enable the Run-Command editor in RetroPi Setup.

RetroPie Setup > Configuration/Tools > Run Command > Launch Menu (Enabled).

From here, you can define a default emulator overall, and specific settings per ROM. You rarely need to touch the framebuffer, it’s usually just the emulator choice, and possibly what resolution you want to run at. Again, Using 640×480 rendered on the RetroPie, will be scaled up to your 1080p screen, and can look better than a 1920×1080 rendering by the RetroPie.

Chapter 7 (Optional) – Configuring Controllers

Only needed if your buttons are not matching up between systems, especially on N64.

There are three ways controller configurations are saved in a RetroPie.

  1. From the initial setup configuration file
    1. nano “/opt/retropie/configs/all/retroarch/autoconfig/Xbox 360 Wireless Receiver.cfg”
  2. From the “live” setup configuration file, what you can change via EmulationStation
    1. nano “/opt/retropie/configs/all/retroarch-joypads/Xbox 360 Wireless Receiver.cfg”
  3. From a system-specific configuration file (N64)
    1. nano /opt/retropie/configs/n64/InputAutoCfg.ini

Below is a mapping image that may be helpful. The stock-mapping works perfectly for NES, SNES, Game Boy, (which all use the RetroArch Input File you created through Emulation Station, but goes absolutely bonkers with non-RetroArch cores.

These input mappings were figured out via the RetroCore GUI Configuration Tool (While in a RetroArch game, press Select + X).



Example Code of a default”/opt/retropie/configs/n64/InputAutoCfg.ini” N64 setup (Wrong).

; Xbox 360 Wireless Receiver_START
[Xbox 360 Wireless Receiver]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
Mempak switch = button(11)
Rumblepak switch = button(12)
C Button D = button(0) axis(3+)
C Button L = axis(2-)
Z Trig = button(4)
Start = button(9)
Y Axis = axis(1-,1+)
DPad U = button(15)
C Button U = button(1) axis(3-)
A Button = button(2)
DPad D = button(16)
X Axis = axis(0-,0+)
R Trig = button(5)
DPad R = button(14)
B Button = button(3)
DPad L = button(13)
C Button R = axis(2+)
L Trig = button(6)
; Xbox 360 Wireless Receiver_END

Issues are:

  1. Button (0) [The A button on a 360 controller)], is auto-mapped to C-Button Down AND Right-Stick Down.
  2. Button (1) [The B button on a 360 controller], is auto-mapped to C-Button up AND Right-Stick Up.
  3. Button (2) [The X button on a 360 controller], is auto-mapped to A.
  4. Button (3) [The Y button on a 360 controller], it auto-mapped to B.


If you are using a 360 Wireless controller, feel free to use these mappings. Edit your config file with a command such as:
"nano /opt/retropie/configs/n64/InputAutoCfg.ini"

Use Ctrl+K to delete by line rather than holding down backspace, a bit faster.

Right-Click in Putty to paste in the code box below, for "; Xbox 360 Wireless Receiver_START

Example Code of a modified “/opt/retropie/configs/n64/InputAutoCfg.ini” N64 setup (Correct).


; Xbox 360 Wireless Receiver_START
[Xbox 360 Wireless Receiver]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
Mempak switch = button(11)
Rumblepak switch = button(12)
C Button D = axis(3+)
C Button L = axis(2-)
Z Trig = button(4)
Start = button(9)
Y Axis = axis(1-,1+)
DPad U = button(15)
C Button U = axis(3-)
A Button = button(0)
DPad D = button(16)
X Axis = axis(0-,0+)
R Trig = button(5)
DPad R = button(14)
B Button = button(2)
DPad L = button(13)
C Button R = axis(2+)
L Trig = button(6)
; Xbox 360 Wireless Receiver_END


Chapter 8 – ROM Compatibility for N64

If you are planning to make a few of these systems, you may want to prep one image perfectly and then copy/paste the image to other SD cards with Win32DiskImager.

For that first unit, I’ve always customized each emulator for the most important N64 ROMs. You can define a single ROM to use a specific emulator video-plugin, you can also define the default settings for each plugin. I recommend going lower res for all of the plugins: 720×480 16:9 will give you the best performance for modern widescreen monitors/TVs. You may want to reduce the frame buffer to the native 320×240 size, which is what the N64 used.

For the below list, I have personally tested all three emulators: Gles2N64, Gles2Rice, and GlideN64, to see which is the most stable and has the most playable performance. Some games simply cannot run smoothly on the RetroPie, others it’s a toss-up. You’ll need to enable the Command Editor temporarily when you save these changes. Once done, turn it back off. List below, hope it helps.

Game Name Best Plugin Notes
007 Goldeneye GlideN64 Works fine if overclocked
1080 Snowboarding Gles2N64 Works fine if overclocked
Banjo Kazooie Gles2N64 Graphical Glitches (puzzle pieces)
Bomberman N64 GlideN64 Works ok, some glitches
Conkers Bad Fur Day N/A Too slow on all 🙁
Cruisin’ USA N/A Too slow on all 🙁
Diddy Kong Racing Gles2N64 Works fine
Jet Force Gemini Gles2Rice Work ok, minor stutters
Legend of Zelda – Ocarina Gles or Glide Works fine
Mario Kart 64 Gles2N64 Works fine
Mario Party 1 Gles2N64 Works on all
Mario Tennis Gles2Rice Works ok, minor stutters
Pokemon Snap Gles2N64 Works ok, some glitches
Starfox 64 GlideN64 Works fine
Super Smash Bros Gles2N64 Works fine if overclocked
Wave Race 64 Gles2Rice Works fine if overclocked

That should be enough to get you a fully operational RetroPie. Enjoy, and have fun!


Leave a Reply

Your email address will not be published. Required fields are marked *