errors saving config in retroarch, needing help with settings

hoeveler

@mitu Hi, it's possible it logged that error 3 times because I was trying again so I could write down the exact path in the error message. Interestingly, I went into the Retroarch GUI from the Retropie menu in ES, then went to Main Menu > Configuration File, then "Reset to Defaults", and then "Save Current Configuration" and it WORKED, no error, saved to "/opt/retropie/configs/all/retroarch.cfg"
Then I went to Settings > User Interface and changed the menu to xmb (SOOO much easier to read and navigate!) and then saved the configuration again. Now I'm not getting the saving config errors.
But... I know I can look this up but I don't want to screw anything up by using the wrong command... could you please post the command-line commands I can run (chmod?) to correct the config files and folders recursively? Thanks!

mitu

I don't recommend the 'save config on exit' option nor the reset to defaults, since some settings are not applicable to each system, but if you're a previous RetroArch user, that may work for you.

But... I know I can look this up but I don't want to screw anything up by using the wrong command... could you please post the command-line commands I can run (chmod?) to correct the config files and folders recursively? Thanks!

You can run chown -R pi:pi /opt/retropie/configs and it will change the owner of any file/folder to the pi user.

hoeveler

@mitu Thanks again - can you recommend a walkthrough of the settings in Retroarch as it pertains to a RetroPie setup? It's very hard to find good tutorials, either video or text. Lots of info but all of it very scattered, hard to follow and hard to find specific to RetroPie and RaspPi.

hoeveler

@mitu said

You can run chown -R pi:pi /opt/retropie/configs and it will change the owner of any file/folder to the pi user.

that worked with the exception of two errors:

chown: changing ownership of '/opt/retropie/configs/all/attractmode/attract.cfg.bak': Operation not permitted
chown: changing ownership of '/opt/retropie/configs/all/emulationstation/es_systems.cfg': Operation not permitted

(so I used sudo su and it worked. Then reboot and no more using su! LOL)

dankcushions

@hoeveler have you seen the official docs? https://retropie.org.uk/docs/RetroArch-Configuration/

these are really the only recommended guides. appreciate they may be complex and hard to follow, but it’s a complex and hard to follow system :) i would again really recommend not using the retroarch menu to reset settings or save over the configs as the hierarchy quickly breaks down. follow only the instructions on that link (though i fancy it may be too late)

dankcushions

This post is deleted!

hoeveler

@dankcushions Yes, I have read and re-read the docs several times, but there's nothing there that walks through the Retroarch MENUS, plain and simple.
Again, all I really wanted to do was to follow the docs to get my trackball and spinner working for specific games. I feel like the docs take an "all or nothing" approach to adding spinner and trackball support via mouse input. It doesn't really detail very well how to add it PER ROM.
Where it talks about the:
3 main ways to configure input for RetroArch:
Autoconfigurations - made in EmulationStation
(this won't work because it's not part of this "retropad" concept)
Hardcoded Configurations - made by editing retroarch.cfg file(s)
(this won't work because it takes the "all or nothing" approach mentioned above)
Core Input Remapping - an easy way to do specific control configurations for specific cores, made in the RetroArch RGUI
(and here is where I find myself, desparately trying to re-find the place where you can save out a rom.cfg file but getting warned because I'm treading too deep into Retroarch menus)
SOMEWHERE buried deep within the docs is a couple lines about how to save out and edit the config PER ROM. I feel like I read it once and now can't find it again. This really shouldn't be this hard, and I would argue that ES really needs to just add an option to add the spinner and the trackball in the inputs there to make it JUST as easy as the gamepads and joysticks and buttons are.

dankcushions

@hoeveler said in errors saving config in retroarch, needing help with settings:

@dankcushions Yes, I have read and re-read the docs several times, but there's nothing there that walks through the Retroarch MENUS, plain and simple.

there’s sections to walk through the retroarch menu in the above doc, where appropriate, but note that for the retropie config hierarchy to maintain integrity it’s not always possible to do it via retroarch menus.

Again, all I really wanted to do was to follow the docs to get my trackball and spinner working for specific games. I feel like the docs take an "all or nothing" approach to adding spinner and trackball support via mouse input. It doesn't really detail very well how to add it PER ROM.

i don’t use a spinner/trackball but i presume to add it to a particular rom you would follow the guide here, but when it refers to updating cfg files, you’d instead create and update the per game rom cfg as per here - just add the relevant line(s) to that. also note that when the spinners doc talks about setting core options it links to here where it links to the core options doc which explains how to set them per rom/game

This really shouldn't be this hard

if you can think of a better way to document please update the docs :)

hoeveler

@dankcushions Thanks for the help. I forgot that the docs are in github, so I think I will throw my hat in the ring to writeup a step-by-step guide specifically for lr-mame2003 / lr-mame2003-plus. My problem is simply because of my own ignorance, I'm wading through a bunch of information about capabilities and code examples from 4-5 different sections of the docs, spread out over 3-4 different cores, but as a new user it's hard to understand exactly HOW to do it.
Another part of my confusion has been the mental model of how everything works together. With so many layers to how inputs go through the system (Pi > ES > Retroarch > MAME), and because the menus in Retroarch look a lot like the menus in MAME, at first I was having a hard time knowing where I was.

mitu

@hoeveler said in errors saving config in retroarch, needing help with settings:

that worked with the exception of two errors:
...

Not sure how permissions got changed there, on Linux (RetroPie included) you should not use sudo / su / the root account except for system related functions. The excessive use of sudo can break permissions and will cause - sometimes subtle - issues. If something doesn't work, magically using sudo is not a solution - most likely you'll end up with garbled permissions and errors caused by it.

For normal RetroPie operations (editing/adding config files for games, adding new games, copying/removing saves, etc.) you don't need any special permissions.

Thanks again - can you recommend a walkthrough of the settings in Retroarch as it pertains to a RetroPie setup?

What is particular to RetroPie are 2 main things:

the config hierarchy explained in the RetroArch controller page. If you're just looking to change the input configuration though, you can safely use the core remaps directly from the Controls menu' and you don't have to edit any configuration files.
the Configuration Editor that can be used to change a few RetroArch parameters globally or per-system. This includes the menu driver (interface) - you can switch here from the RetroPie default to xmb or the more modern ozone UI.

Other than that, the complexity comes mainly from RetroArch's own plethora of knobs and options. My advice would be (adding to @dankcushions's post):

don't enable Save on Exit, but instead save a conf override for the game / core / folder. What works for one system/game may not work for the other.
For the input settings - use the RetroArch's menus to change it using the Controls menu, test it and then save a remap (again, for core/game/folder). Input settings regarding the controller are not saved to the configuration file.
Shaders have their own configuration menu, with separate saving options (they're not saved by saving the configuration file).
if you need to change something globally and that option it's not part of the Configuration Editor, then start RetroArch from the RetroPie system and do the changes, this will be applied globally to all systems and cores. Options related to RetroAchievements, Netplay, Notifications, etc.

hoeveler

@mitu Well, I definitely learn things by breaking things, which is why I love the Pi - I can learn and learn and then re-flash if I get into too much trouble.
Which brings me to my next question - given all that I've learned recently about the right way to do things, but also knowing that this time around I didn't just delete config files at random but have tried to be very careful in what I'm editing - should I (for the 3rd time) reflash retropie to the defaults and start all over again? I mean... things are working fine now with the exception of the lv10: Error finding/creating FileData for "/home/pi/RetroPie/roms/arcade/mame2003-plus", skipping. that we never quite fixed.

mitu

@hoeveler said in errors saving config in retroarch, needing help with settings:

I mean... things are working fine now with the exception of the lv10: Error finding/creating FileData for "/home/pi/RetroPie/roms/arcade/mame2003-plus", skipping. that we never quite fixed.

Is this another permission issue ? Does that folder exist and it's accessible by the pi user ?

hoeveler

@mitu I tried the same pi user chmod command on that but it didn't make the error go away.

mitu

@hoeveler I'd just re-flash the image again, do an update and then proceed from there with the configuration.

hoeveler

@mitu Indeed. I'm doing just that with a brand new 128GB microSD card. AND I'm happy to report that the keyboard timeout issue has gone away since I replaced the 2A 5V power supply with the CanaKit 3.5A 5.1V PSU! :)

hoeveler

@hoeveler NOW what's going on?! I reflashed, updated packages, raspi-config, installed the pimoroni picadeHat (all this via command line, haven't opened ES yet, always hit F4 to quit to command line) but now upon my first use of ES, when I select anything in the retropie menu and it fades out ES UI (like when I'm going to ES themes for example) but the screen is now faded and nothing will bring me back to the ES interface. The only way I can get control is to use the shutdown button on my picade hat, which shows the command line shutdown process. So why is my screen fading out and the system seemingly unresponsive?
EDIT: I just hit F4 and the screen quit out of ES but didn't go to the command line. This is even worse than I had things before I reflashed - is this 128GB card too big now? LOL
Maybe this??
On Debian Jessie add consoleblank=0 to the existing line in /boot/cmdline.txt (with a space before it so it's an additional parameter). This prevents the screenblanker kicking in. With it, runcommand dialog is always displayed.
No, I checked and it's already there... Hmm

Ashpool

@hoeveler not sure whether fsck may identify "fake" Flash Media, but as they seem to have become a major problem during the pandemic and harware-shortage: Have you tried testing the the card with F3 (aka "Fight Flash Fraud or Fight Fake Flash" *nix) or H2testw (windows)?

hoeveler

@Ashpool No! I've never heard of this. I'll check it out.
EDIT: I might have just fixed the issue automatically by running an arcade ROM. Now the retropie menu items work properly. Maybe running a ROM and having that process refresh the HDMI and/or audio outputs fixed something?

hoeveler

@dankcushions @mitu I have another question about how things work... while doing more RTFM ;) I learned that libretro mame 2003 plus actually reads metadata about the game ROMset with regards to controls and labels, etc.
https://docs.libretro.com/library/mame2003_plus/#input-system-controls-and-options
Here it even mentions, "By default, mice/trackballs and analog sticks (the left one, for controllers with 2) are supported in games that would have them, or equivalents. For example, Centipede supports the mouse/trackball, and Afterburner supports the stick."
https://docs.libretro.com/library/mame2003_plus/#mouse-and-trackball-support
So, why doesn't it actually work this way in RetroPie? Why do I have to get into all this manual configuration if these docs SEEM to indicate that this all could be just simple plug-n-play?

dankcushions

@hoeveler i'm afraid mame2003 plus is not something i'm familiar with (although perhaps a similar method is in place for mame2003 vanilla since i stopped working on it years ago)

in any case, you're looking at the libretro docs (not ours), although they seem to have lifted this section from our docs: https://retropie.org.uk/docs/lr-mame2003/#mousetrackballanalog-controller-support which i wrote and are (or at least at the time of writing) correct - if you have analog stick set on your retropad, it's used where appropriate by default. mouse is a little trickier as you may have to point it to the right mouse device (several gamepads/keyboards/etc will add mouse devices to your system), but yes it is used when it's needed.

so yeah i don't know why you're setting things up 'per game' as you would seem to be busywork. just set it up per core in the configuration editor. probably could even add it to your entire retroarch but again i don't use mice/etc so I can't say what ramifications that would have on all cores.