codelegend.com

Hi Nick,
Could you copy/paste the [Reference Speeds] section complete? So I can look at all the characters.

Adjusting other aircraft.cfg files to look like this:

cruise_speed = 150.

continue to be read perfectly, so at the moment I'm not entirely sure what is the actual problem in your .cfg at the moment as I have been unable to reproduce. The file is read equally well in other languages so it is not a problem of the decimal period but maybe something nearby.

Hi Nick,

Well, a bit of a mystery the aircraft.cfg. Because it is Windows itself that delivers the content of that value on the right of the equal sign.

So it was windows itself that could not, read those values, for whatever reason I can't think of other than some kind of oddness in the date/time/number setup in your system. And so reading the decimal gave the problem but I can't reproduce it on my dev system.

It might be worth going over those language items in control panel and resetting those just to be sure. There are known problems with International settings that can appear to affect IF but are just messing with .ini file translations of numbers.

The first PC Flight1 tried IF on originally, had a translation fault that did a similar thing reading the config. It turned out to be their PC. And I think it is the result of installing some tool that messes with the system in that way causes it. Since later versions of Windows seemed to cure it, problems of the sort have not been seen for several years now.

Another thing can happen but it is unlikely.

The system can have installed settings by installing another app that does not work internationally, that affect application behaviour in other apps. Making these settings incorrectly can result in apps other than the intended app to be 'helped out' and Windows expects to read the other character. But IF would report 100 knots if it can't read it, and fails if Windows can't read it. So there are ways and means but I've not worked out what it is.

Yes, it may have to do that in Windows I have set Region: Greece and Regional format: Greek.

It could affect the decimal sign recognition, but only when it's now followed by a zero (?)

Yes, it is an odd one and doesn't affect all PCs. In those files they are always decimal periods, US format. So with FP numbers in other languages using a decimal comma, the OS decides to change the dot to a comma for some sessions and can't read the ini-file entry. It affects certain types of Windows licences. I remember the solution was to set to US date/time/number and reboot, then set up Greek and reboot. Then try it out.

...I came across some notes. One PC had FSX installed and it couldn't read any aircraft.cfg's. It was a US OS installed machine then changed to Netherlands. FSX was removed, US format set and rebooted, Then Netherlands was set and FSX installed and then it worked. It was curious because it was thought that to cure it that FSX need only be installed while in US format but didn't work. So if your thing is similar then it might affect apps you installed only at a certain time which means that Windows expects different characters and can't read them.