1. When you select a speed percentage (any value from 10% to 200%), Dolphin writes that value as a "standard" FP number with 8 digits after the decimal point (e.g. 1.00000000) to the .ini
But if you select "Unlimited" (framelimiter OFF), a FP number with *9* digits after the decimal point (0.000000000) is written to the .ini file. Is this by design?
2. What happened to the 'GCAdapter' option in the .ini and the ability to completely disable the feature if you don't use it? Is it always enabled now?
3. If Dolphin.ini is made read-only, a temporary file named 'Dolphin.ini.xxx' is created, so the settings can still be modified. The same applies for the other .ini files. And it works nicely.
But there's one exception: the GFX.ini file. A temp file 'GFX.ini.xxx' is created with the modified settings, but Dolphin *fails* to read from this file (it reads from the read-only GFX.ini instead). Is this a bug or a 'feature' ?
4. Isn't it better to store the AF value in the GFX.ini as samples, similar to the AA seting (1,2,4,8,16 instead of 0,1,2,3,4 as it is now)?
But if you select "Unlimited" (framelimiter OFF), a FP number with *9* digits after the decimal point (0.000000000) is written to the .ini file. Is this by design?
2. What happened to the 'GCAdapter' option in the .ini and the ability to completely disable the feature if you don't use it? Is it always enabled now?
3. If Dolphin.ini is made read-only, a temporary file named 'Dolphin.ini.xxx' is created, so the settings can still be modified. The same applies for the other .ini files. And it works nicely.
But there's one exception: the GFX.ini file. A temp file 'GFX.ini.xxx' is created with the modified settings, but Dolphin *fails* to read from this file (it reads from the read-only GFX.ini instead). Is this a bug or a 'feature' ?
4. Isn't it better to store the AF value in the GFX.ini as samples, similar to the AA seting (1,2,4,8,16 instead of 0,1,2,3,4 as it is now)?