EmulationStation is the official graphical frontend of the RetroPie project.
EmulationStation is not an emulator, rather it is a polished game launcher that includes:
- Controller and keyboard support
- Custom themes
- Scraper for box art and game metadata
ES was originally developed by Aloshi (code) and Nils Bonenberger (UI) but, since they have moved on to other projects, the RetroPie project keeps its own fork. That fork has made some improvements like video support, faster load times, favourites, and controller integration among others. Any reference for versions in this doc is related to the RetroPie's fork.
Enabling Favorites, All Games, and Last Played systems
Since ES version 2.4.0 you can create a list of your favorite games. You can also have a list of all games, and your last played games. These lists are all optional and in the example below we'll see how to enable them.
Note: In order to use this feature, the theme you're using MUST support it.
Startto access the ES main menu and then select "GAME COLLECTIONS SETTINGS".
- Next, select the first option: "AUTOMATIC GAME COLLECTIONS".
- And then mark those you want to enable.
- After marking those you want, go back to the default ES user interface. Note that now you have more systems, like in the example below:
Adding games to Favorites
It's pretty simple: just move to the game you want to add and press the button you set to be
Y when the cursor is on a game already present in the Favorites, removes it from the list.
Since ES version 2.6.0 you can create a custom list of games. You can group games by any category you want. Examples: shoot'em ups, beat'em ups, Street Fighter, RPGs, Batman, TMNT, Mega Man or any other category you can think.
If the name of the collection you're creating matches an unused theme folder, it will be shown in the main carousel as a new system entry. If there's no matching theme folder for the name you selected, it will be grouped under a new "Collections" carousel system entry.
In the example below we'll create a custom collection to group Mega Man games. Note: You can either choose to create a collection based on an unused theme folder, or if creating from scratch you'll need a keyboard to type the name of your custom collection.
Startto access the ES main menu and then select "GAME COLLECTIONS SETTINGS".
Select the option "CREATE NEW CUSTOM COLLECTION".
- An input box will be shown. Type the name of your custom collection.
- After typing the name and pressing OK, you're now in a mode where the button you set to be
Yadds a game to the collection. Look the message on top of the image below. (Note: while in this mode you can't add games to your favorites).
- Move the cursor to the game you want to add to your collection and press
Y, just like you do to add/remove a game to Favorites. After adding a game you'll see a message on the top of screen, like in the image below.
- After adding the games you want in your collection, you can finish editing the collection by either:
a) going to any game list, pressing
Selectand selecting "FINISH EDITING 'YOUR CUSTOM' COLLECTION", or b) going to "GAME COLLECTIONS SETTINGS" menu and then select "FINISH EDITING 'YOUR CUSTOM' COLLECTION".
- Now go to the "collections system" and you'll see your custom collection.
- Once you "FINISH EDITING 'YOUR CUSTOM' COLLECTION", the
Ybutton recover the behavior of adding/removing games to the favorites list. If you want to put ES on "editing custom collection mode" again, go the custom collection game list, press
Selectand then choose "ADD/REMOVE GAMES TO THIS GAME COLLECTION".
Editing ES Configs
ES uses xml files for its database and caches them on loading and exit, so any edits to the configuration files will need to be changed when ES is closed.
Because of the way the RetroPie-Setup script works custom configurations will need to be copied and edited in specific places, otherwise your custom edits would be overwritten anytime a system was updated from the RetroPie setup script.
Note that any configs in
~/.emulationstation/ are symlinked to
/opt/retropie/configs/all/emulationstation/ which means both paths will work.
There are different configuration files for the different aspects of EmulationStation:
es_systems.cfg defines the systems that show up in ES. The RetroPie-Setup script will automatically generate this config file alphabetically when you install any new systems. ES will check two places for an es_systems.cfg file, in the following order, stopping after it finds one that works:
<?xml version="1.0"?> <systemList> <system> <name>nes</name> <fullname>Nintendo Entertainment System</fullname> <path>/home/pi/RetroPie/roms/nes</path> <extension>.nes .zip .NES .ZIP</extension> <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ nes %ROM%</command> <platform>nes</platform> <theme>nes</theme> </system> </systemList>
More information HERE
Custom es_systems.cfg should be in
cp /etc/emulationstation/es_systems.cfg ~/.emulationstation/es_systems.cfg
Note that anytime you add a new system from the RetroPie-Setup Script you will need to manually copy over the new system to the new location in order to keep parity.
Retropie uses a file called
platforms.cfg to generate the system configurations for
es_systems.cfg you can create a custom platforms.cfg to override the default system for regional variants such as the Sega Genesis instead of Megadrive, Turbografx instead of PC-Engine, and the Magnavox Odyssey instead of the Videopac.
name, extensions, platform (used by es for scraping), and the theme can be overriden, see HERE for the default platforms.cfg
The following is an example of a custom platforms.cfg
megadrive_theme="genesis" megadrive_platform="genesis" pcengine_theme="tg16" pcengine_platform="tg16" videopac_theme="odyssey2" videopac_platform="odyssey2"
Note that with any custom platforms.cfg you create you'll need to update all systems from the setup script to generate a new es_systems.cfg with your changes.
After configuring your controller in ES, your controller configurations will be saved to
RetroPie uses custom generation scripts that will generate controller configurations for many emulators through the initial ES controller configuration, so if you remove or make any edits to this configuration you need to regenerate that hook
Retropie Setup Script >> Manage Packages >> Manage Core Packages >> EmulationStation >> Configuration / Options >> Clear / Reset EmulationStation Input Configuration
There are several scrapers available in RetroPie: the built in EmulationStation scraper, Steven Selph's
scraper and Lars Muldjord's
Skyscraper. More information HERE.
gamelist.xml file for a system defines metadata for a system's games, such as a name, image (like a screenshot or box art), description, release date, and rating.
ES will check three places for a
gamelist.xml in the following order, using the first one it finds:
An example gamelist.xml:
<gameList> <game> <path>/home/pi/ROMs/nes/mm2.nes</path> <name>Mega Man 2</name> <desc>Mega Man 2 is a classic NES game which follows Mega Man as he murders eight robot masters in cold blood.</desc> <image>~/.emulationstation/downloaded_images/nes/Mega Man 2-image.png</image> </game> </gameList>
See more information HERE
If you use the built in ES Scraper your gamelist.xml and images folder will be in
If you use another scraper (Steven Sselph's
scraper or Lars Muldjord's `Skyscraper) you can choose whether your scraped data goes in
[SYSTEM_PATH]/gamelist.xml(the rom folder) or
The RetroPie community has developed many themes for ES. See Themes page HERE.
ES will check two places for a theme in the following order, using the first one it finds:
Themes installed from the RetroPie-Setup script will be installed in
See more information HERE
See here for a tutorial on Creating Your Own EmulationStation Theme
Custom themes should be in
if you want to make custom themes or edit an existing theme:
First make a themes directory if it doesn't exist
add your theme to the themes folder or if you are copying an existing theme to edit, we'll use carbon as an example:
cp -R /etc/emulationstation/themes/carbon ~/.emulationstation/themes/carbon_custom
EmulationStation supports calling external scripts and executables on certain program events.
1. The scripts directory
First, create a new directory called scripts inside the config directory:
Linux (as user
2. Event directories
Inside the scripts folder, create a new directory for the kind of event you want to script:
|Name||When||Arguments (max. 2)|
||on program quit||
||on system reboot (also calls quit first)|
||on system shutdown (also calls quit first)|
||on the change of any configuration option|
||on change of the control settings (also calls config first)|
||on change of the regular (non-control) settings (also calls config first)|
||on change of theme (also calls settings-changed after)||
||before starting a game||
||after finishing a game|
||station is without user input for more than
||see note (*)|
||station returns from sleep (i.e. user input)|
||after screensaver starts|
||after screensaver stops|
(*) sleep/wake use no arguments.
systemSleepTime is usually after
screenSaverTime (both editable in the Screensaver Menu). A value of
0 disables sleep and the screensaver respectively.
3. Script calling
Put your executable scripts or binaries into these new directories. They will be called in alphabetic order when the event happens.
Command Line Arguments
EmulationStation has a few command line arguments that could be helpful to you for various customisation. Let's say you wanted to setup a kiosk but did not want to give access to the builtin scraper function or you didn't want the end user to be able to exit EmulationStation, you can simply edit
/opt/retropie/configs/all/autostart.sh and append the corresponding command line argument.
For example, to disable the Exit option from inside the Quit menu, edit
emulationstation --no-exit #auto
To see a complete list of the supported command line arguments
Because of the development hiatus, there has been some attention towards other front-ends. The following alternate frontends can be installed from experimental packages of the RetroPie Setup-Script but support is currently only preliminary.