[Misc.] A few quirks in the latest dev. builds

[kirbypuff]

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)?

[JosJuice]

(01-10-2016, 07:09 AM)kirbypuff Wrote: The latest development builds of Dolphin have a funny issue:

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. O_0

...okay? Is that a problem?

(01-10-2016, 07:09 AM)kirbypuff Wrote: P.S. 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?

You now select the adapter in the controller type dropdown instead. https://wiki.dolphin-emu.org/index.php?title=How_to_use_the_Official_GameCube_Controller_Adapter_for_Wii_U_in_Dolphin#Dolphin_4.0-8601_and_Newer

[DJBarry004]

Now that you are talking about latest dev issues, i found out that 4.0-8591 doesn´t want to work. It simply won´t open.

My specs are on profile. Any solution to this? I really want to try the latest improvements.

[JosJuice]

(01-11-2016, 07:21 AM)DJBarry004 Wrote: Now that you are talking about latest dev issues, i found out that 4.0-8591 doesn´t want to work. It simply won´t open.

My specs are on profile. Any solution to this? I really want to try the latest improvements.

Is 4.0-8591 the version where it started happening? If not, please bisect.

[DJBarry004]

Will really take a lot of time for that since the last working version I have is 4.0-8044... Oh well...

[degasus]

(01-10-2016, 07:09 AM)kirbypuff Wrote: 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)?

Oh, I didn't know that we create/read any ini.xxx file. I'll checkthe code for it later.

About the AF values. Yes, you're right, they should be stored as samples itself. But it is not as bad as it was with MSAA samples. We don't iterate over all supported AF configurations, it's directly 2**this_ini_value.

[JosJuice]

(01-10-2016, 07:09 AM)kirbypuff Wrote: 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)?

Please don't edit posts when you want to say something new after people have replied. It makes your new questions much harder to keep track of

[kirbypuff]

(01-11-2016, 07:21 AM)DJBarry004 Wrote: Now that you are talking about latest dev issues, i found out that 4.0-8591 doesn´t want to work. It simply won´t open. Any solution to this?

Try 4.0-8680. Works like a charm, not a single crash or freeze (unlike the latest Ishiiruka build which crashes all the time).

[Helios]

(01-11-2016, 07:58 AM)DJBarry004 Wrote: Will really take a lot of time for that since the last working version I have is 4.0-8044... Oh well...

https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds

[DJBarry004]

@helios747: Your tool doesn´t want to open. Like latest dev builds... :/

@kirbypuff: That build you gave me won´t open either. I don´t know what´s going on with my PC, honestly.

Did some manual bisecting, the last working dev build so far that i have found is 4.0-8299. I´m trying with 4.0-8313 right now.

UPDATE: 4.0-8313 also works perfectly. Will continue bisecting.

UPDATE 2: Downloaded 4.0-8398, opens and works with no problem. Whatever bug is causing latest dev to not open, it must have appeared between 8398 and 8435 (which doesn´t open). Any thoughts of this so far?