The input string '1.25' was not in a correct format

[gsnde]

Hi Arno. I have re-staged my computer and reinstalled MCX. The decimal delimiter is set to a point. The current version keeps telling me constantly what is mentioned in the title.

Any idea what I am doing wrong?

Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.FormatException: The input string '1,25' was not in a correct format.
at System.Number.ThrowFormatException[TChar](ReadOnlySpan`1 value)
at System.Convert.ToSingle(String value)
at ASToFra.Utils.FormMemory.GetStateDict(String formState)
at ASToFra.Utils.FormMemory.FormMemory_FormClosing(Object sender, FormClosingEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(HWND hWnd, MessageId msg, WPARAM wparam, LPARAM lparam)

 

[arno]

Can you try to clear your settings (see the manual for where they are stored).

 

[arno]

I had a look at the code, this error must happen when the display scaling is read. The error seems to indicate that a value of 1,25 is stored (notice the comma). Could it be that you use MCX before with the decimal character still set to comma and now you have changed it to dot? I think that is what is causing this error.

Clearing the settings should solve this. I could probably make the code more robust for this, but not sure how often this situation will happen.

 

[gsnde]

Exactly that happened, Arno. No problem to clear the settings. Thanks for finding this out so fast.

 

[DragonflightDesign]

Hi Arno

I'm not sure if this will help, but I ran into a similar problem recently updating P3D3 when parsing latitude and longitude (doubles) on different localisations. What I did was to clone the user's localisation and then force the decimal separator to be a point (chr(46)) on the application thread only.

        Dim data As String = Nothing
(...)
        ' Force the decimal separator to be a period on this thread
        data = CultureInfo.CurrentCulture.Name
        If Microsoft.VisualBasic.Left(LCase(data), 3) <> "en-" Then
            Dim cinfo As CultureInfo = Thread.CurrentThread.CurrentCulture.Clone()
            cinfo.NumberFormat.NumberDecimalSeparator = "."
            Thread.CurrentThread.CurrentCulture = cinfo
        End If

For me, this meant that any doubles that were stored always had a decimal point as the separator.

 

[arno]

Thanks, I'm not sure that forcing the dot is a good solution in general. Now that there are more users of MCX that use MSFS only it would make sense that they can just run with the comma as decimal character. It's only XtoMDL that has the bug that it needs the dot to be set.