WOW!In my opinion, this is a great add on aircraft.I have been stuck on the Gulfstream V and Falcon 50 as carry overs from FS2002 as far as BizJets are concerned for a long time, but it is time for them to move over and let another bird enter the nest in my hanger.I understand there are some problems in FS2002 (Says so with a warning on the download site), but in FS9 I am very impressed. I have tried only the deluxe version and don't see how the lesser options could be much better on frame rates although several are included in the download.About the only thing for what I would wish would be a fully functional FMC (Theirs is partial). Of course, the Gulfstream and Falcon have none at all. (Of course they were freeware too and prize birds).Highly recommend you take a peek if you are operating with FS9.RTH

Hi,I agree, looks great and they Eaglesoft team has anounced a fully functional FMC as a payware addon. So I consider to buy it. But I read about an issue about decimal points while trying to set the radios. I use german number settings on WinXP ('.' = group separator, ',' = decimal separator) and I can't change this due to requirements of other software. I've posted a question about this in the Eaglesoft forum - but no answer.Regards, Tom.

>Hi,>I agree, looks great and they Eaglesoft team has anounced a>fully functional FMC as a payware addon. So I consider to buy>it. But I read about an issue about decimal points while>trying to set the radios. I use german number settings on>WinXP ('.' = group separator, ',' = decimal separator) and I>can't change this due to requirements of other software. I've>posted a question about this in the Eaglesoft forum - but no>answer.Actually, there is an answer there; we're working on trying to find a workable solution. Note that this "decimal separator issue" isn't unique to Eaglesoft products. It is an FS issue and affects all a/c, even the defaults. If you ask MS for the "solution," they'll tell you to change your system settings... :)

The CX model was created by Eaglesoft Development Group Team Members.Flight One is our Publisher:-)The CX model works well in FS2002:-)The CX Ultralight Model is the only version of four CX Models that work in Win98 or Win ME.We have dropped support for Win98 or Win ME and encourge users with the above operating systems to pass on purchasing the CX until they update their systems:-)

Ron,sorry, but I'm a bit confused. Your are probably right in all points you stated but how are these related to my question?I'm running an English version of FS9 on a German Windows XP Professional with German language and number settings. I have no problems with any other a/c (stock a/c, CS 727, PSS A340, PMDG 737 1.3, PMDG B1900). So my simple question before buying the CX is thw following: Is the CX comptible with the specs mentioned, especially am I able to tune the radios properly without any additional tweaking?Thanks, Tom.

>Ron,>sorry, but I'm a bit confused. Your are probably right in all>points you stated but how are these related to my question?>>I'm running an English version of FS9 on a German Windows XP>Professional with German language and number settings. I have>no problems with any other a/c (stock a/c, CS 727, PSS A340,>PMDG 737 1.3, PMDG B1900). So my simple question before buying>the CX is thw following: Is the CX comptible with the specs>mentioned, especially am I able to tune the radios properly>without any additional tweaking?>>Thanks, Tom.I have no experience re: the German version of XP but it would seem that if you have no tuning problems with default aircraft you will not with the CX:-) Nothing special about our tuning methods since we used default tuning variables for the CX:-)As mentioned the seperator issue is an OS/FS anomaly and not any specific aircraft:-)

Ron is right: if this works with others, it should work too. Note that the decimal point/coma incompatibilities are to my knowledge, solely due the compiler / program design involved, not the OS. The OS reports the decimal point choosen by the user to the string / values handling OS code. If the compiler uses these OS handling code, instead of say "C" related handling code, you are in for troubles (example if this speaks for you: using the OS based API to convert a char * to an int, instead of using the C API). This is VERY OFTEN exhibited with Visual Basic programs for example.Hope this helps!