Your controller is configured once and for all with the Recalbox configurator, and that configuration serves every emulator. Still, some games or machines call for a different layout: swapped buttons, a trigger somewhere else, an extra button to reach. That is what RetroArch remaps are for.
This page covers Libretro cores (the vast majority of Recalbox emulators). Standalone emulators have their own settings, described on their system page in the Emulators section. The special case of the N64 is covered in N64 controller configuration.
HOTKEY + B (see RetroArch).Port 1 Controls (player 1's controls).| Option | Scope of the remap |
|---|---|
Save Core Remap File |
every game run with this core |
Save Content Directory Remap File |
every game in the current folder |
Save Game Remap File |
this game only |
Keep a keyboard within reach: while remapping, it is easy to end up with no confirm button left. In the RetroArch menu,
Wconfirms andXgoes back.
📷 Illustrations to be recovered from the old wiki:
controllerconfig1.pngtocontrollerconfig5.png(controls menu and saving options).
The files produced use the .rmp extension and live in:
/recalbox/share/system/.config/retroarch/config/remaps/
They are sorted per core and kept from one launch to the next: unlike the rest of the RetroArch configuration, which Recalbox regenerates every time a game starts, remaps are never overwritten. To cancel a remap, simply delete the matching .rmp file.
A RetroArch remap is not always the right tool. Depending on what you need:
.retroarch.cfg configuration override, whose useful keys are listed in RetroArch overrides;.recalbox.conf override;CORE OPTIONS menu in game, or a .core.cfg override;To find out a button or axis number, use the tools described in Testing a controller.