scelts/gees

Incorrect speeds in the LOG file

Closed this issue · 14 comments

Airspeed not corresponding to the real airspeed on touchdown, and the indicated crosswinds are the airspeed of the plane
gees

and yes these are very very bad landings

Wow, seems that many of the things are wrong: headwind is not correct too I guess?
Did you edit the Landings.v1.csv file maybe - opened it in excel, changed columns, saved it etc? Anything else you modified or something?

I'm asking cause I have no idea how this happened.

running simulation at half rate/ 2x rate etc? Very low FPS? Anything that's not usual?

i didn't do anything on the csv file, didn't open it, didn't even opened the location of the file in file explorer

i'll retest to see

i tested again and... it didn't record my landing it the TBM930

and there is a red strip that is staying on the left of my screen

that's supposed to be there, you can click to show.
can you give me some more info on anything unusual in your setup? also, if there is a log.txt file in the app folder, please paste it here.

what i find wierd is that only the speeds in the log are messed up

I think I have an idea what is it!
Can you please help me and check the Control Panel -> Clock and Region -> Region -> Additional settings -> Decimal symbol
image

I assume it's a comma (,)

Also please check the Documents\MyMSFS2020Landings-Gees csv file. You'll probably have more columns in values than titles.

Note: https://stackoverflow.com/questions/3135569/how-to-change-symbol-for-decimal-point-in-double-tostring

No need to check, it's 100% this error.... I'm new with all this c# app dev.
I'll fix it in the next version, sorry for this.
The workaround, for now, is to change this setting to dot ( . ), delete the existing log, and restart the app. Or just leave it, I'll push the new version later during the day. But the log is gonna stay bad, so you'll lose the landings you did, sorry.

yeah it's a comma on my pc

No need to check, it's 100% this error.... I'm new with all this c# app dev.
I'll fix it in the next version, sorry for this.
The workaround, for now, is to change this setting to dot ( . ), delete the existing log, and restart the app. Or just leave it, I'll push the new version later during the day. But the log is gonna stay bad, so you'll lose the landings you did, sorry.

don't worry for my landings, these ones were to test your app, and as you can see, they're bad anyway...

Why bad, standard Ryanair landing :)

Thanks for the reporting, it's a really stupid error, but a tough one to catch.

0.3.2 should hopefully fix this.