Custom "Speed Limit" value that isn't multiple of 10 is lost when "Config" is saved

[Nintendo Maniac 64]

By manually editing the "EmulationSpeed =" value located in Dolphin.ini , I personally prefer setting Dolphin's "Speed Limit" setting to a value that is not listed in the according drop-down menu (do note that the setting does not appear in Dolphin.ini unless you initially change the "Speed Limit" setting in the GUI to some value other than 100%).

However, as soon as I change any other setting in "Config" (such as checking "Enable Cheats"), the speed limit gets set right back to 100% (which you can verify by looking at the actual Dolphin.ini file) even if you don't actually touch the GUI drop-down menu for the "Speed Limit" setting.

Is there any way that custom "EmulationSpeed"/"Speed Limit" values that aren't in the drop-down menu can be retained even after modifying the "Config" settings?

[AdmiralCurtiss]

This should be fixed in the latest dev build.

[Nintendo Maniac 64]

Yep, seems to work!

Now I can enjoy in-game music at different audio pitches without worrying about it getting set back to default.

(I personally find an emulation speed value of 0.981818... aka the fraction 54/55 with audio stretching disabled to musically sound better, but don't tell any audio engineers/scientists that I said that or I'll instantly get labeled as a "quack"; I also like to combine it with a custom resolution / refresh rate of 58.85Hz or 117.70Hz to prevent the 54/55 speed from causing telecine judder since I currently don't have a VRR-capable display)



EDIT: Though, it does look a bit odd that the GUI's "Speed Limit" settings visually displays whatever the closest 10% value is rather than going blank or saying something like "Custom".

So in my situation where I use a value of 0.981818... it'll display 100% in the GUI which means that, if I want to use actual 100% and not 98.1818...%, I must first select something like 90% and then select 100% (or, alternatively, just manually edit the Dolphin.ini file again).


But perhaps this is just me being nit-picky...