by Steve Waite » Mon Mar 25, 2019 11:25 pm
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.
software architect at codelegend.com
equipment: i9-9980Xe 64GB 2xRTX2080ti NVLink 2TB M.2 NVMe,
i9-9900X 64GB RTX2080ti 2TB M.2 NVMe, i7-3960X 32GB GTX680 4TB RAID10,
NAS @7TB RAID10 (16TB)