(11-21-2014, 11:33 PM)Dogway Wrote: What good reason, can you elaborate?
It is very painful to have so many files (with crypting filenames) and different bunch of settings that some are considered default, and some local, (whatever that means), not to say those that are outdated, deprecated or even with shared sections (SyncGPU belonging to [CORE]).
"Anisotropic working" means it does work but it won't be reflected on the graphics setting?
What about
[Video_Hacks]
EFBAccessEnable = False
It isn't reflected on the graphics settings either, as the backend does... My concern is not about changing settings "on the fly", but rather reflecting them.
Please, elaborate further because current behaviour is very very confusing.
Gameinis shouldn't affect the general settings, and in order to do so they don't show up in the graphic settings gui. That is because a lot of graphic settings can be changed on the fly. General settings cannot be changed on the fly and therefore there is no issue just to display them in the gui in a per game running basis without the capability to change them. For example the control settings that can also be changed on the fly have an issue with dolphin and gameinis, if you set a specific control profile and just open and close the key configuration while running the said game, the per game profile you loaded will also become your general profile. Something similar would happen with graphic settings too, if they didn't revert to the general settings when you open the window, afterwards just by closing it your per game settings would become the new general settings. It is just that on the fly settings change is too important to drop just for gameinis, and therefore things became complicated.
To simplify the above if no settings were configurable while a game is running there would be no such issue between general and per game settings. Things would be a lot more simple but the lack of configuration ability while ingame is not desirable either.