RetroArch

From Linux Gaming
Revision as of 10:39, 12 May 2025 by AngeUshiromiya (talk | contribs) (Created page with "[https://www.retroarch.com RetroArch] is a unified graphical front-end for multiple emulators. == Installation == It can be installed from your package manager, Steam, Flathub and even Snapcraft<ref>https://www.retroarch.com/index.php?page=linux-instructions</ref>. == Usage == === Core installation === RetroArch doesn't come with emulators by default. Called "cores" in RetroArch, they're plugins implementing the Libretro API. To install them, you do it through the onl...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

RetroArch is a unified graphical front-end for multiple emulators.

Installation

It can be installed from your package manager, Steam, Flathub and even Snapcraft[1].

Usage

Core installation

RetroArch doesn't come with emulators by default. Called "cores" in RetroArch, they're plugins implementing the Libretro API. To install them, you do it through the online updater, directly from RetroArch [2]. You can do it manually by downloading the core you want from buildbot.libretro.com and extracting it to ~/.config/retroarch/cores/.

Troubleshooting

  • If your graphics card is old, you might have to check if "Allow Cores to Switch the Video Driver" in "Core" settings is enabled and change the video driver used by RetroArch from glcore to gl in "Video" settings, under the "Output" menu[3].
  • RetroArch didn't enter in proper fullscreen under old versions of GNOME X11[4] and workarounds included devilspie2 scripts[5], running RetroArch with Gamescope[6] and forcing borderless fullscreen windowed mode.
  • To reset all RetroArch settings, go to ~/.config/retroarch/ and delete retroarch.cfg[7].
  • If you're using GNOME with an Nvidia GPU, game frames may flicker[8] and persist after exiting a game until the next reboot if you don't have "Show Window Decorations" enabled in "Video" settings, under the "Windowed Mode" menu (it might be related to buffer-flipping[9][10][11][12], Nvidia G-Sync [13] or unredirection being broken[14][15]).