Steam version of RetroArch can't detect other drives (Linux)

[Thespeedy905]

Hello,

As title states, it can't seem to detect other drives when I want to load content, it can only detect the root directory (/), and where the Steam Version of Retro Arch is installed at (aka if I look at the /mnt directory, only one drive is present, even though I have two data drives). This is my first time running the program, as I've used stand-alone emulator apps in the past.

I've noticed from a Reddit post that was asked about this issue around 2 years ago and it was solved by installing a snap addon of the package.

A couple of things:
1. I am on Arch Linux, and would like to use the Steam version of RA. I know this would probably be solved by installing the arch package of RA, but would like to use the Steam version.
2. I've enabled the option to show hidden files/directories and other extensions.
3. I could also just move the Installation folder to the drive where my ROMS are located, but I want to be able to spread out as much of the space as I can. (i.e programs installed on one drive, and data on the other). I currently have 2 data drives, and one root drive.

I'm not sure if this is a bug, or if i'm just being too needy about this, but any help would be appreciated. Thanks.

[skookiesprite]

It's not just you; it's a bug (and one that has come and gone twice for me since RA playtest released on steam, though I can't figure out what fixed it). It's a huge problem for me: RA suddenly refuses to recognize my zfs array (where I keep all my files and games for emulation)... So you are not alone doood! Super hoping they fix it again now that they've pulled the trigger on the post "same dir structure for all" patch. Cheers!

[Valkhades]

Heh, was fine just some days ago even with the usual messiness of the UI, but geez, better just ♥♥♥♥ up everything now.

It does not load assets, them complains that has no assets, ask to update if possible (is not possible, removed because stupid reasons), cant redirect folders to cores, cant redirect folders to roms... The list goes on.

And with the horrible UI that has "a learning curve" (reminder that if you program an UI with learning curve, you are doing it terrible wrong, and that's a no contest ever in any real job on the area.), this is now a waste of space on the HD.

[nickbieter]

I'm having the same issue; furthermore, it isn't detecting the steam controller or the logitech f310 i have

[Thespeedy905]

Alright so its not just me then. Thanks yall. I'll just use the arch version in the meantime.

[ageres]

The same for me (Arch Linux too). It can access only my home folder and its Steam folder. Besides ROMs, I tried to make RetroArch to use my installed cores in /usr (that's what I did when RA was as AppImage), no success. I tried editing cfg, I tried symbolic links, still nothing.

[EarthwormDan]

well i'm glad its not just me who lost access to ROMs stored on a secondary drive, does anyone have a fix yet?

[Mats]

I have pushed out a fix on the nightly beta/branch which should make everything in /mnt work and hopefully home for users having issues with that on some distros. Tell me if it works and I will update the stable branch to it.

Originally posted by nickbieter:

I'm having the same issue; furthermore, it isn't detecting the steam controller or the logitech f310 i have

Currently RetroArch seems to to default to the x input and xinput drivers for input and controllers. Change both to sdl2 and restart RA and it should hopefully be fixed. I am already looking into getting the default changed as this should work out of the box.

[EarthwormDan]

the nightly branch didn't seem to make a difference here, the only drive visible in /media is the one RetroArch is installed on, but there are two other drives containing ROMs etc that are still not visible. Running on Ubuntu 20.04

[Mats]

Originally posted by EarthwormDan:

the nightly branch didn't seem to make a difference here, the only drive visible in /media is the one RetroArch is installed on, but there are two other drives containing ROMs etc that are still not visible. Running on Ubuntu 20.04

oh i forgot to add /media by default
Could you try to create a file named "mounts" in the RetroArch directory add write /media in it and see if it fixes it?

[EarthwormDan]

Originally posted by Mats:

Originally posted by EarthwormDan:

the nightly branch didn't seem to make a difference here, the only drive visible in /media is the one RetroArch is installed on, but there are two other drives containing ROMs etc that are still not visible. Running on Ubuntu 20.04

oh i forgot to add /media by default
Could you try to create a file named "mounts" in the RetroArch directory add write /media in it and see if it fixes it?

Ah now it's working just fine, re-adding ROMs right now. Thankyou for such a speedy fix!

[Mats]

Originally posted by EarthwormDan:

Originally posted by Mats:

oh i forgot to add /media by default
Could you try to create a file named "mounts" in the RetroArch directory add write /media in it and see if it fixes it?

Ah now it's working just fine, re-adding ROMs right now. Thankyou for such a speedy fix!

I added it to the automatic mounts so it should work out of the box as soon as the next nightly build finishes.

[Thespeedy905]

Originally posted by Mats:

Originally posted by EarthwormDan:

Ah now it's working just fine, re-adding ROMs right now. Thankyou for such a speedy fix!

I added it to the automatic mounts so it should work out of the box as soon as the next nightly build finishes.

Hello, so i'm retrying the Steam version of RA, and while i got most of it working, while i can load up a core (downloaded from build.retro), when i want to load content, it somehow can't detect the core, it thinks that i have no cores installed, but when i try to install the core through the GUI, it gives me a notification that the core is already installed.

I am on the nightly build of the steam version

[Thespeedy905]

Originally posted by sp33dy905:

Originally posted by Mats:

I added it to the automatic mounts so it should work out of the box as soon as the next nightly build finishes.

Hello, so i'm retrying the Steam version of RA, and while i got most of it working, while i can load up a core (downloaded from build.retro), when i want to load content, it somehow can't detect the core, it thinks that i have no cores installed, but when i try to install the core through the GUI, it gives me a notification that the core is already installed.

I am on the nightly build of the steam version

got it fixed. replace all the core and info files from build.libretro

[Mats]

Originally posted by sp33dy905:

Originally posted by sp33dy905:

Hello, so i'm retrying the Steam version of RA, and while i got most of it working, while i can load up a core (downloaded from build.retro), when i want to load content, it somehow can't detect the core, it thinks that i have no cores installed, but when i try to install the core through the GUI, it gives me a notification that the core is already installed.

I am on the nightly build of the steam version

got it fixed. replace all the core and info files from build.libretro

I have been trying to figure this out with some others which suffer from the same issue, somehow their Steam client seem to be unable to download the core DLCs. If you check the list of DLCs in the Steam Client I assume they all have no size listed for you?

[Thespeedy905]

Originally posted by Mats:

Originally posted by sp33dy905:

got it fixed. replace all the core and info files from build.libretro

I have been trying to figure this out with some others which suffer from the same issue, somehow their Steam client seem to be unable to download the core DLCs. If you check the list of DLCs in the Steam Client I assume they all have no size listed for you?

Did a reinstall of RA, i've decided to grab the mGBA core from the Steam store and grab another core from the libretro website (PPSSPP). Somehow, both cores showed up fine. Either:
1. Fresh reinstall fixed it
or
2. It wants a core installed from the Steam Store first before I can add other cores.

Not really sure if this answers your question.