As both a person who edits the ini database and as a user i found the implementation of gnick working fine for me and practical, coding is something that i can't really judge. This change certainly doesn't help me in any way. At least the ini database hasn't any need to change but that doesn't mean that there won't be any incompatibilities again when the transition to the new system is completed.
Also Neobrain why did you choose to mess with the video options when there are other options that can affect compatibility that haven't been implemented yet?
(04-27-2011, 02:17 AM)Link_to_the_past Wrote: [ -> ]As both a person who edits the ini database and as a user i found the implementation of gnick working fine for me and practical, coding is something that i can't really judge. This change certainly doesn't help me in any way. At least the ini database hasn't any need to change but that doesn't mean that there won't be any incompatibilities again when the transition to the new system is completed.
The new system itself will not cause incompabilities to the current ini database.
However, I plan to do some restructuring of the video configuration dialog, which will change the way some options are specified. BUT I'll add compatibility code for the current way to do it since we're about to release 3.0...
(04-27-2011, 02:17 AM)Link_to_the_past Wrote: [ -> ]Also Neobrain why did you choose to mess with the video options when there are other options that can affect compatibility that haven't been implemented yet?
The removal of the configuration profiles was part of making other non-gfx related settings to be configured per game. The config profile approach just didn't work out for non-gfx related settings, since we can't add a "config profile" combobox at every dialog used in dolphin..
Yeah, why not just having all important settings in the "per-game-settings"/game properties?
The revision 3.0 will take too long to leave? Is it stable at 2.0 or was it?
Configuration profiles settings were better because the dolphin is still not 100% in every game, you have to configure video and sound on many specific games.
At most, I agree that this is the best decision to make at this time regarding this matter.
So sorry for my poor english.
sigh... It's going backwards
To be honest I really see no need to duplicate the settings, dolphin is the only emulator that does this and it's not necessarily needed or all that useful. You'll spend less time configuring settings in the main configuration dialogs than configuring individually for each game especially if you have a lot of games. Also if you overwrite the user and/or the /user/GameConfig directory you will lose your changes. Using basic settings is fine for most games, there may be one or two odd games that require efb to ram, cpu efb access, xfb but those are few and far between. If a game requires any of the more advanced "intensive" settings the time needed to switch them on is quite minimal, hardly an inconvenience.
Sticking the the basic options, disabling cpu efb access, efb to texture, disabling xfb, HLE audio, dual core, idle skipping will give the best performance with most games. Unless a game needs any other option and those games are few and far between eliminating gameini profiles and using a basic configuration tweaked for performance might be the better choice. Just tweak the main configuration depending on the game you want to play if any additional features other than the defaults are needed, much less time spent than configuring each game and just as effective.
I wish the developers never started this nonsense with game profiles, it's kind of confusing and time consuming to have settings in two different places. I've been considering stripping out game profiles in my builds, I really don't like them, need them or see any use in duplicating settings.
(04-27-2011, 10:36 AM)Xtreme2damax Wrote: [ -> ]To be honest I really see no need to duplicate the settings, dolphin is the only emulator that does this and it's not necessarily needed or all that useful. You'll spend less time configuring settings in the main configuration dialogs than configuring individually for each game especially if you have a lot of games. Also if you overwrite the user and/or the /user/GameConfig directory you will lose your changes. Using basic settings is fine for most games, there may be one or two odd games that require efb to ram, cpu efb access, xfb but those are few and far between. If a game requires any of the more advanced "intensive" settings the time needed to switch them on is quite minimal, hardly an inconvenience.
Sticking the the basic options, disabling cpu efb access, efb to texture, disabling xfb, HLE audio, dual core, idle skipping will give the best performance with most games. Unless a game needs any other option and those games are few and far between eliminating gameini profiles and using a basic configuration tweaked for performance might be the better choice. Just tweak the main configuration depending on the game you want to play if any additional features other than the defaults are needed, much less time spent than configuring each game and just as effective.
I wish the developers never started this nonsense with game profiles, it's kind of confusing and time consuming to have settings in two different places. I've been considering stripping out game profiles in my builds, I really don't like them, need them or see any use in duplicating settings.
The way things are now you just need to delete all the game.ini files. They are quite useless after all ...
To me they are. I could remove the ini files, but what about the code that calls/loads the gameconfig ini's?
i vote we remove shuffle2 and neobrain from the project for not adding anything of value. (removing neobrain is just for lolz)
='(
i will be looking forward to a similar implementation in the future.