Display of systems

Display operation
The display of systems in the Recalbox menu is managed by the file "es_systems.cfg". This file is located in the folder:
./recalbox/share_init/system/.emulationstation/es_systems.cfg
It contains the names of the different systems that are supported by your version of Recalbox. It is constructed as follows:
1
<?xml version="1.0"?>
2
<systemList>
3
  <system>
4
    <fullname>Panasonic 3DO</fullname>
5
    <name>3do</name>
6
    <path>/recalbox/share/roms/3do</path>
7
    <extension>.iso .ISO .cue .CUE .chd .CHD</extension>
8
    <command>python /usr/lib/python2.7/site-packages/configgen/emulatorlauncher.pyc %CONTROLLERSCONFIG% -system %SYSTEM% -rom %ROM% -emulator %EMULATOR% -core %CORE% -ratio %RATIO% %NETPLAY%</command>
9
    <platform>3do</platform>
10
    <theme>3do</theme>
11
    <emulators>
12
      <emulator name="libretro">
13
        <cores>
14
          <core>4do</core>
15
        </cores>
16
      </emulator>
17
    </emulators>
18
  </system>
19
  <system>
20
      [. . .]
21
  </system>
22
  [. . .]
23
</systemList>
Copied!
The display of the systems respects the order in which they are listed in this file. It also contains the configuration of these systems.
Change the display order
WARNING : 
DO NOT MODIFY the original "es_systems.cfg" file (which is in the "share_init" directory). If a future change caused the slightest problem, there remains the only source to recover your Recalbox and make it work properly again.
Should you modify the display order, it MUST BE DONE ONLY  
via the file "es_systems.cfg" present in the following directory:
./recalbox/share/system/.emulationstation/es_systems.cfg
By default, this file does not exist. Either copy the original file or create a new file. Once the new file is created, it is possible to organize the systems in the order you want. The system configuration will always be taken from the original "es_systems.cfg", but the order of the systems will be that defined by the new file. 
If, in the new file, a system is absent or incorrectly specified, priority is given to the original file. For the new file, there are only 2 entry keys that are required: "fullname" and "platform", all the others are optional. The file must be constructed as follows:
1
<?xml version="1.0"?>
2
<systemList>
3
  <system>
4
    <fullname>Nintendo Entertainment System</fullname>
5
    <platform>nes</platform>
6
  </system>
7
  <system>
8
    <fullname>Family Computer Disk System</fullname>
9
    <platform>fds</platform>
10
  </system>
11
  <system>
12
    <fullname>Super Nintendo Entertainment System</fullname>
13
    <platform>snes</platform>
14
  </system>
15
  <system>
16
    <fullname>Satellaview</fullname>
17
    <platform>satellaview</platform>
18
  </system> 
19
    [. . .]
20
  </system>
21
  [. . .]
22
</systemList>
Copied!
Add a "Custom" system
WARNING: 
DO NOT MODIFY the original "es_systems.cfg" file (which is in the "share_init" directory). If a future change caused the slightest problem, there remains the only source to recover your Recalbox and make it work properly again.
This manipulation does not add a new emulator to Recalbox but adds a new system entry in the selection menu. 
It is possible to combine the modification of the display of the systems and the addition of one or more custom systems.
As for the modification of the order of the systems, the addition of a "custom" system must be done only from the file "es_systems.cfg" present in the following directory:
./recalbox/share/system/.emulationstation/es_systems.cfg
By default, this file does not exist. Either copy the original file or create a new file. Once the new file is created, it is possible to organize the systems in the order you want. 
If a system is incorrectly entered in the new file, priority is given to the original file. For the new file, all entry keys are required. In order to create a new system, the simplest is to start from an existing system (and corresponding to the roms that we want to include) and modify only what is necessary:
"fullname": Used to name the new system.
"path": Used to indicate the directory containing the roms of the new system.
"theme": Used to indicate which theme to use. You must first create this new theme (logo, background, ...)
All other entries must not be changed.
Here is an example of addition for a SNES-based system to include only translated roms:
1
<?xml version="1.0"?>
2
<systemList>
3
  <system>
4
    <fullname>Super Nintendo Fan Trad</fullname>
5
    <name>snes</name>
6
    <path>/recalbox/share/roms/snestrad</path>
7
    <extension>.smc .sfc .SMC .SFC .mgd .MGD .zip .ZIP .7z .7Z</extension>
8
    <command>python /usr/lib/python2.7/site-packages/configgen/emulatorlauncher.pyc %CONTROLLERSCONFIG% -system %SYSTEM% -rom %ROM% -emulator %EMULATOR% -core %CORE% -ratio %RATIO% %NETPLAY%</command>
9
    <platform>snes</platform>
10
    <theme>snestrad</theme>
11
    <emulators>
12
      <emulator name="libretro">
13
        <cores>
14
          <core>snes9x2005</core>
15
          <core>snes9x2010</core>
16
          <core>snes9x2002</core>
17
        </cores>
18
      </emulator>
19
    </emulators>
20
  </system>
21
</systemList>
Copied!
Configuration
Configuration overload
Last modified 1yr ago
Copy link
Contents
Display operation
Change the display order
Add a "Custom" system