You are not logged in.

#1 Yesterday 18:15:53

kargi
Member
Registered: 2024-05-11
Posts: 7

Installing libretro does not add cores to Retroarch

I've installed the libretro and ensured the cores are present on my system, but Retroarch refuses to detect any of the cores installed by the package. I've also made sure that I'm using a fresh configuration file, but the problem persists. I will note that my ~/.config/retroarch/cores directory contains no cores.

Last edited by kargi (Yesterday 19:50:32)


smile

Offline

#2 Yesterday 20:37:31

FelixYoung
Member
Registered: Yesterday
Posts: 1

Re: Installing libretro does not add cores to Retroarch

The empty folder is the one RetroArch is watching. The packages drop cores in /usr/lib/libretro, not in ~/.config/retroarch/cores. In Settings, Directory, set Cores to /usr/lib/libretro. A fresh config keeps pointing at the home directory, so it stays empty even when the cores are installed.

Offline

#3 Yesterday 22:42:42

kargi
Member
Registered: 2024-05-11
Posts: 7

Re: Installing libretro does not add cores to Retroarch

FelixYoung wrote:

The empty folder is the one RetroArch is watching. The packages drop cores in /usr/lib/libretro, not in ~/.config/retroarch/cores. In Settings, Directory, set Cores to /usr/lib/libretro. A fresh config keeps pointing at the home directory, so it stays empty even when the cores are installed.

This does fix the problem, but why then does Arch's build of retroarch default to the ~/.config/retroarch/cores directory? This feels more like a workaround to a problem than a fix.

Last edited by kargi (Yesterday 22:43:56)


smile

Offline

#4 Today 00:02:52

GaKu999
Member
From: US/Eastern
Registered: 2020-06-21
Posts: 703

Re: Installing libretro does not add cores to Retroarch

kargi wrote:
FelixYoung wrote:

The empty folder is the one RetroArch is watching. The packages drop cores in /usr/lib/libretro, not in ~/.config/retroarch/cores. In Settings, Directory, set Cores to /usr/lib/libretro. A fresh config keeps pointing at the home directory, so it stays empty even when the cores are installed.

This does fix the problem, but why then does Arch's build of retroarch default to the ~/.config/retroarch/cores directory? This feels more like a workaround to a problem than a fix.

Arch's philosophy is usually 'stay close to upstream when sane', and the upstream default for retroarch is that it manages cores and everything on its data dir. Cores on the system is an user choice so it isn't hardcoded.

EDIT: Typo, phone be dumb.
PS: https://wiki.archlinux.org/title/RetroA … figuration

Last edited by GaKu999 (Today 00:06:22)


What's up doc?

Offline

Board footer

Powered by FluxBB