Specific retroarch emulator settings are being over written after i quit the game.

herb_fargus

@Floob don't forget to make a visual flowchart ;)

dankcushions

the 'proper' way of doing this is to edit these files using the retropie config editor:
https://github.com/retropie/retropie-setup/wiki/Configuration-Editor

can't go wrong with that!

mediamogul

This is the type of complexity that only a puppet show can fully illustrate. Too bad the price of felt and googly eyes has skyrocketed in recent years. I blame trade relations.

Floob

First attempt. Plenty of room for correction and improvement.

alt text

herb_fargus

@Floob oo very fancy you work fast. You using draw.io?

Floob

@herb_fargus Yep!! Its great isnt it! :)

mediamogul

@Floob

Very illuminating. Jim Henson himself couldn't have done better.

Concat

You rock Floob. Fast indeed.

Other things that (could) affect the config structure:

Core Remap files
Configuration Per Core = ON
User per-game Core Options = ON
Load Override Files Automatically = ON

It sounds to me like RetroPie has it's own way of managing at least the last three items, so there could be conflicts and unexpected results.

meleu

I think the new users must know that editing configs using RGUI on RetroPie is contraindicated. But maybe it's is only my personal opinion... So I'm not sure if this should be written on the wiki.

Floob

@Concat Thanks.
The core remap is largely covered here

Buzz added "auto_remaps_enable" to be true in the global retroarch.cfg to support it. But yes, I could add details of the file and directory it creates.

Yes, the last 3 are largely dealt with by RetroPie/RetroArch config setup really, so I wouldnt tweak those in RGUI myself.

dankcushions

@Concat said in Specific retroarch emulator settings are being over written after i quit the game.:

You rock Floob. Fast indeed.

Other things that (could) affect the config structure:

Core Remap files

this is as per usual retroarch.

Configuration Per Core = ON

retropie doesn't use this really i think?

User per-game Core Options = ON

this isn't to do with retroarch.cfgs - this is just how the retroarch-core-options.cfg is made up. i could go into more detail, but it functions exactly the same as vanilla retroarch, so just google that :)

Load Override Files Automatically = ON

i believe this is just per game.cfgs (eg zelda.zip.cfg in your nes rom dir). this works as per vanilla retroarch.

retropie doesn't really do anything special with configs. it's just using the standard --config and --appendconfig commandline arguments to invoke global and per-core configs. see https://github.com/libretro/RetroArch/wiki/Using-the-command-line

(i think the unique thing it does it creating temporary cfgs via the runcommand, but that's only for framebuffer and stuff like that i believe)

hakan1708

Thanks everybody for great info. Chart is awesome. King of the charts, but that would be great if we had the emperor of the charts. What is that? That is the chart that you will either need a big commercial printer to see everything or a small printer and a nice microscope. This chart will explain every step in detail (including every option and what happens when you change them). While explaining the changes in the file, chart will start to grow arms, long fingers, scary nails and it becomes a monster. Monster will try to kill you but if you survive, you will rule over him, and it will be your servant forever. Finally your Retropie Kingdom will have some peace that it's been longing for.

naddel81

just wanted to adjust screen aspect ratio on the different cores (gbc/gba/nes) but even when I select save config (to retroarch.cfg) it is completely ignored on the next boot of the same game. so in my opinion the "save settings" option is totally broken and the "configuration editor" is not a proper replacement for an ingame emulator function that is supposed to work in real time without additional config tools.

why doesn't it work as it was intended?

edit: guess I am not the only one that finds this troubling:

http://libretro.com/forums/showthread.php?t=4773

I can't believe that this basic function doesn't work after all those years of retroarch.

FAB2TB

@Floob @meleu Thanks for your video and explanations on this topic, it works but I still have one big problem which is every retroarch.cfg files are never reloaded with what I saved into them when I shutdown and reboot my Pi3, Retropie 4.0.2 and emulation station ...it always reload original retroarch.cfg skeleton files without the modifications I made (for eg. uncommented lines in the /all dir or added lines in the /{system} dir) .
Also selected the option "save on exit" as explained but changed nothing...event "save on exit" is no more ON after shuting down and restart everything. Did you faced the same problem once, any advice to help me?

meleu

@FAB2TB I don't know how you are changing your configs, but RetroPie-Setup turns off the "save config on exit" if you turn it on using the RGUI started from RetroPie menu.
Look this post: https://retropie.org.uk/forum/post/22636

FAB2TB

@meleu I've tried several ways to change the /all/retroarch.cfg but none of them managed to keep my modifications after a reboot of the Pi. What I just did after you answered to try once again is using the configuration editor from the Retropie menu: changed config_save_on_exit = "true" and also changed few other things like switching player1/player2 index :

input_player1_joypad_index = 1
input_player2_joypad_index = 0

finally pressed TAB then OK to save it, then edited /all/retroarch,cfg using winSCP to check if my modifications were saved which was perfect. Then QUIT Emulation station and reboot the Pi and guess what...the original skeleton of retroarch.cfg is back again in place of the one I ve just modified! I really appreciate any help coz it start to make me crazy

meleu

@FAB2TB
Please, create another thread with your specific issue.
I suggest you this title: "RetroArch configs using RetroPie-Setup configeditor don't persist after reboot".

Don't forget to describe your environment (read-this-first form) and detail the steps to reproduce your problem.