The command line seems to be working. it’s still a run around, but at least it works.
[QUOTE=Radius;46892]This. The problem with per-core is that there never was a clear indication of what was happening under the hood. You never knew if your changes would affect global or core.
That’s really not possible unless we make every setting a struct that includes the level it is affecting.[/QUOTE]
Could this be handled by splitting the config into two files, a global and then core-based config? Global would handle things like output res core and config directories and playlists. Core would have core save directories, controller setup, and core options. Core options would always be in the core options file and global settings would always be in the global file. You could start each core with default settings and then update them to your liking, and maybe import core settings from other cores so that you don’t have to redo settings if you don’t want to.