(03-28-2018, 02:34 AM)Infinite Josh Wrote: 1. Are commands like --config=<System>.<Section>.<Key>=<Value> that are run from Dolphin shortcuts entirely dependant on the new configuration making them functional, or can these commands already do whatever we want?
That only works with settings that are implemented in the new config system.
(03-28-2018, 02:34 AM)Infinite Josh Wrote: If the former, do you have any tips for where I should be looking on that Git page to ascertain whether the ability has been implemented for using commands to set something like FullscreenDisplayRes?
Open the .cpp files in the folder you linked to and look at all the statements that start with "const ConfigInfo". Those statements will tell you the names of all settings in the new config system.
(03-28-2018, 02:34 AM)Infinite Josh Wrote: Whether it's the former or latter, should a shortcut with --config=Dolphin.Display.FullscreenDisplayRes=1440x1080 at the end of the target line properly change the fullscreen resolution? That hasn't worked for me but I don't know if it's because of syntax or the feature just not existing.
Something like that should work once the setting gets moved to the new config system.
(03-28-2018, 02:34 AM)Infinite Josh Wrote: 2. Is the functionality of the [game].ini text somehow linked to the recent changes to the Core / Config section, or are the two systems mostly unrelated at this point?
All settings that are implemented in the new config system are automatically usable in game INIs. There are also some settings that can be used in game INIs even though they aren't implemented in the new config system.