mgh

Set Windows Explorer to show the file extensions.

Why is that a FSUIPC problem?

In Windows API, the function GetPrivateProfileString() handles .ini files https://msdn.microsoft.com/en-us/library/windows/desktop/ms724353%28v=vs.85%29.aspx

Because it's a false positive. Kaspersky, MalwareBytes, Mcafee, and Microsoft Security Essentials (and others) state it isn't a virus.

If it contains a trojan why are you the only one to have problems?

Also the Working Set isn't the VAS. For example, my FSX shows Working Set = 548K Wbtyes but Virtual Memory Map (VMMap) shows Virtual Memory = 1,095K bytes

In a thread on the Prepar3d forum titled Just so you know… (for devs) Adam Breed of Lockheed Martin said on February 10, 2015 at 07:53 It seems unlikely that Prepar3D is compatible with Windows 10 if it still doesn't have complete Windows 8+ compatibility?

This may be be relevant to Saitek controllers: http://forum.simflight.com/topic/76089-directinput8create-failed-return-80040154/

Pete might perhaps cancel his hoidays if all the eager enthusiations for v2.5 actually paid him large sums of money ?

Pete I admire your restaint in dealing with people who don't how to make a foreign purchase, and also foolish expect any supplier will still be in business in 2 years time in this climate (incidentally, since 1 January 2015 in the EU VAT is based on the customers country and not that of the seller for telecommunications, broadcasting & electronic services - including downloads.)

I should have known better :(

Pete Dawson doesn't support older versions.

You can solve your problem either by truncating/rounding the data in your code before using the data.

I have no where the data comes from. But, if they are based on the same database why are there differences between runways.txt (48.35850925 degrees) and from G5.csv (48.358513 degrees). That's a difference of 0.4167 m. Somehing must have changed them.

As I said previously

There are no mistakes. The data is simply derived differently. runways.txt is clearly not right. As I explained, real word coordinates are not given to 4-decimal places of minutes.

The TQ737 throttle seems to retail at Candian $1,299.95?

I cannot offhand remember the precedence rules for C/C++ but have you tried this: Latitude = latDeg * (10001750.0 * 65536.0 * 65536.0) /(90.0);

They are effectively the same. The calculation in runways.txt is: N48:21:30.6333 = 48 (degrees) + 21 *60 (minutes) + 30.6333 (seconds) = 48.35850925 degrees The calculation In g5.csv = 48.358513 degrees The difference is 48.35850925 - 48.358513 = 0.000003750 degrees which is a difference of 0.4167 m. Anyway, the actual values for the AIP from EDMM are Stand 202A N41 degrees 21.54 minutes or 48.359 degrees and Stand 202B N41 degrees 21.51 minutes or 48.3585 degrees. I don't what the differences are between A and B. The values from runway.tx are suspicious because they are given to a false accuracy of 4 decimal places of seconds. 0.0001 seconds is about 3 millimetre. That suggests they have been re-calculated from an original source

What actual value of altitude does that expression give when it is executed? Read the description of $0570 - it isn't what you think it is. altitude := altitude * 3.28084/(65536.0*65536.0);

It was only in your last post (#8) that you said you were running FSX but have "Saitek Pro flight panels Fs2004 (FsUipc)" Could that be your problem?

I understood you are running FSX but have "Saitek Pro flight panels Fs2004 (FsUipc)"

Does Pro-soft.it sell FSUIPC?

I don't you did download WideFS from http://secure.simmarket.com/pete-dowson-widefs7.phtml. That sites explains how to download the file WideFS.zip, and also how to register it. WideFS.zip includes the documenation - WideFS Technical.pdf and WideFS User Guide.pdf

Practically all models have suspension. The details are given in the [contact_points] section of the aircraft.cfg which show the Static Compression, Ratio of Maximum Compression to Static Compression, and Damping Ratio each item of landing gear..