RetroArch is a modular, command-line driven, multi-system emulator that is designed to be fast, lightweight, and portable. It has features few other emulators frontends have, such as real-time rewinding and game-aware shading based on the libretro API.
Install AUR.AUR from the
A GTK+/Qt frontend,AUR, is also available.
Each package from the AUR will install an emulator core to
/usr/lib/libretro/[system].so, thus to use
retroarch with your preferred system simply launch it with the
-L parameter. E.g.
retroarch -L /usr/lib/libretro/libretro-snes9x-next.so ~/path/to/game
.zipfiles using the
retroarch-zipshell wrapper, however, keep in mind that this is not supported within the implementation.
This emulation core can also be defined in the
retroarch.cfg, thus obviating the need to specify it on the command line.
libretro_path = "/usr/lib/libretro/libretro-snes9x-next.so"
There are currently several emulation cores available including snes9x, bsnes, visual boy advance and final burn alpha. See this AUR search for more.
RetroArch provides a skeleton configuration file located at
/etc/retroarch.cfg and is very well commented.
It is capable of supporting split configuration files using the
#include "foo.cfg" directive within the main
retroarch.cfg file. Alternatively, extra configuration files can be appended on the command line which override the default settings in
retroarch.cfg. This can be achieved by using
--appendconfig /path/to/config and is beneficial if different keybinds, video configurations or audio settings are required for the various implementations.
retroarchis capable of loading bsnes xml filters  and cg shaders . They can be defined in
audio_out_rateis equal to your system's default output rate. This is usually 48000.
No keyboard/mouse input
If you are having no keyboard input in an X-less environment, this is due to the fact that the /dev/input nodes are root-only. You can set up a udev rule which makes these accessible to non-root. To
KERNEL=="event*", NAME="input/%k", MODE="666"
Then reload the udev rules with:
sudo udevadm control --reload-rules
Until next reboot (or replugging devices), you can force permissions with
sudo chmod 666 /dev/input/event*.
If your video driver has very bad performance, it is possible to run it on a thread to avoid almost all video driver overhead. Set
video_threaded = true in
Butter smooth VSync behavior in this case is impossible however, and latency might increase slighly. Use only if you cannot obtain full speed or if changing video resolution/refresh rate settings seem to not work.