I am trying to configure the retroarch.cfg, but I am a little bit confused about that.
In the program dir there is a retroarch.cfg and a retroarch-phoenix.cfg, if I delete both of them there will also be a phoenix.cfg created under %AppData%.
What setting has to be edited in what file? Because I have only configured everthing in the retroarch.cfg.
I believe the one in the program directory will override the one in %AppData%. You can also manually specify a cfg path using the ‘-c’ command line switch.
For Windows, RetroArch config file is searched for in this order:
Same goes for Phoenix. It’ll first look for retroarch-phoenix.cfg in same folder. If not found, it’ll try %APPDATA%. This is done to allow “portable” folders. Phoenix has to create config files for both itself and RetroArch if it cannot find their configs. They’ll be created in %APPDATA% by default.
retroarch-phoenix.cfg are settings related to Phoenix itself, like last used config file, and some GUI things.
Hmm. Why is the phoenix.cfg named in two differend ways (retroarch-phoenix.cfg and phoenix.cfg).
Edit: Ok. In the program dir it has to be named retroarch-phoenix.cfg in %AppData% it has to be named phoenix.cfg instead.
Not intentional. But to avoid breaking on new versions, it’s not going to change unless a very good reason comes up.
I see.
I made all my settings in the skeleton file, but as you said I have to put some of these settings into the retroarch-phoenix.cfg. but which of them 
Maybe it would be better that I use the phoenix GUI to configure RetroArch.
I am trying to configure a portable installation of my RetroArch installation. As described here.
Relative paths in config should work, but I’ve never tested it on Windows. It will depend on what the working directory is when you launch retroarch I guess.
If it turns out to be necessary, I can add a “metapath” later on which could refer to absolute path of where retroarch was launched. E.g. “:/foo.cfg”
I added relative-to-retroarch-path config paths.
E.g if retroarch.exe resides in C:/foo/retroarch.exe, a config path of “:/bar.cfg” will resolve to C:/foo/bar.cfg. Should come in handy. It works for *nix as well, but it’s not as useful there as the binary is generally placed in /usr somewhere …
Sounds great. Thx.