Why did you construct them manually? There is a significant difference between a manually entered waypoint and a pre-defined SID/STAR/IAP waypoint from an ARINC database.UPDATEI just reviewed that approach. The Citation X is not certified to fly those. :(

In the real world it's not certified for an RNP approach... but in the simulation it will nevertheless track the lateral and vertical profiles very well. The problem I have found with many FSX add-ons with FMS emulations is that they cannot accurately follow a horizontal path consisting of multiple, closely-spaced waypoints defining a tightly curved path. For that matter, neither can many (older) FMS systems in real-world aircraft. (It's actually more a lack of capability in the autopilot, rather than the FMS for those R/W planes that cannot accurately fly such procedures.)I constructed the procedure manually, because the Navigraph implementation isn't correct at PSP - the procedure is so complex that it probably exceeds the capability of the automatic data parsing tools they use to import real-world approach procedures from the ARINC source data.Jim Barrett

In the real world it's not certified for an RNP approach... but in the simulation it will nevertheless track the lateral and vertical profiles very well. The problem I have found with many FSX add-ons with FMS emulations is that they cannot accurately follow a horizontal path consisting of multiple, closely-spaced waypoints defining a tightly curved path. For that matter, neither can many (older) FMS systems in real-world aircraft. (It's actually more a lack of capability in the autopilot, rather than the FMS for those R/W planes that cannot accurately fly such procedures.)I constructed the procedure manually, because the Navigraph implementation isn't correct at PSP - the procedure is so complex that it probably exceeds the capability of the automatic data parsing tools they use to import real-world approach procedures from the ARINC source data.Jim Barrett

Excellent points Jim! I too was wondering why you had done so but do agree that is indeed a "Torture Test" for not only the FMS but the FGC as well.At any rate, congrats on the build and the report. These were the goals set from the start and Ed Wilson has certainly done a fine job on this one. :(

In the real world it's not certified for an RNP approach... but in the simulation it will nevertheless track the lateral and vertical profiles very well. The problem I have found with many FSX add-ons with FMS emulations is that they cannot accurately follow a horizontal path consisting of multiple, closely-spaced waypoints defining a tightly curved path. For that matter, neither can many (older) FMS systems in real-world aircraft. (It's actually more a lack of capability in the autopilot, rather than the FMS for those R/W planes that cannot accurately fly such procedures.)I constructed the procedure manually, because the Navigraph implementation isn't correct at PSP - the procedure is so complex that it probably exceeds the capability of the automatic data parsing tools they use to import real-world approach procedures from the ARINC source data.Jim Barrett

Actually, I'll have to confess and state that our FMS doesn't parse the RNP data very well. Because I knew the aircraft wasn't certified to fly RNP approaches so I really didn't bother trying to make it work. The actual physical ARINC data appears to be mostly correct.

I just purchase the FS9 version and am interested in the gauge refresh rate in FSX. Does anyone own both versions? (btw congrats on your affluent status:)). If not, could someone compare the FSX ES CitationX refresh and frame rate against the Eaglesoft Cirrus SR22 for FSX. I have on my wish list Goflight compatibility for both models. Thanks in advance.Bob.. :)

I just purchase the FS9 version and am interested in the gauge refresh rate in FSX. Does anyone own both versions? (btw congrats on your affluent status:)). If not, could someone compare the FSX ES CitationX refresh and frame rate against the Eaglesoft Cirrus SR22 for FSX. I have on my wish list Goflight compatibility for both models. Thanks in advance.Bob.. :)

With full keyboard support... it can't possibly get any more compatible. You assign custom keys in a config file for the aircraft and then tell the Goflight module to send those keys.

We've made no effort for variable gauge refresh rate to accomodate lower end systems.We've had no negative feedback from users with descent hardware/memory.CX2.0 is more efficient than SR22 for a number of valid reasons.Cirrus owners will be pleased to know that we intend to add keyboard shortcut support for the Avidynes sometime in early 2010.What that means is users will be able to configure GoFlight hardware for the Cirrus Series. :(

Is anyone else's CX not following LNAV? It'll reach a waypoint but then just keep flying without turning to the next one in sequence. -Alex

With full keyboard support... it can't possibly get any more compatible. You assign custom keys in a config file for the aircraft and then tell the Goflight module to send those keys.

By compatible, I mean the modules work with the aircraft right out of the box as far as HDG,OBS and ALT which are currently on a pop-up. I spent the whole day (not an eaglesoft problem) trying to get my joystick, FSUIPC and Goflight to talk to each other using mouse macros. The method discussed in the documentation. I have some suggestions from Pete Dowson to try tomorrow so hopefully I'll get the rotary knobs working.Now, hopefully someone can provide feedback concerning VC gauge refresh and frame rate in FSX as compared to either the FS9 version or the ES Cirrus for FSX. Bob..

By compatible, I mean the modules work with the aircraft right out of the box as far as HDG,OBS and ALT which are currently on a pop-up. I spent the whole day (not an eaglesoft problem) trying to get my joystick, FSUIPC and Goflight to talk to each other using mouse macros. The method discussed in the documentation. I have some suggestions from Pete Dowson to try tomorrow so hopefully I'll get the rotary knobs working.Now, hopefully someone can provide feedback concerning VC gauge refresh and frame rate in FSX as compared to either the FS9 version or the ES Cirrus for FSX. Bob..

I have already stated that we have a fully functional keyboard support interface. The only requirement is that you must set up what keys will execute what knob/switch/button function and then you must tell your GoFlight to send the key(s). It is compatible... out of the box... no FSUIPC macros required.

I have already stated that we have a fully functional keyboard support interface. The only requirement is that you must set up what keys will execute what knob/switch/button function and then you must tell your GoFlight to send the key(s). It is compatible... out of the box... no FSUIPC macros required.

I understand. Again, I was following the path of your documentation in which you referenced mouse macros. As far as can tell the GF Config does not accept key sequences for rotary switches. It will work for buttons and switches. We must use mouse macros to map HDG, ALT etc. BTW, you guys (ES folks) seem (whether intentional or not) irritated with questions and comments. I strongly recommend alcohol as a proven edge remover. LOL. Oh.... well, regardless, I still think you guys build excellent planes. Thanks.Bob..

Bob, the docs your refer to were offered as an assist by users, for users, who wish to do all sorts of configurations via FSUIPC, Mouse Macros, Custom GF configurations, etc.All of this has been WIP and the Keyboard Shortcut capabitlity in the latest release allows users to configure their setups to taste.We simply do not have the time or inclination to set everyones custom configurations for them.There are a few users who've accomplished these things in our forums so feel free to ask them questions there. :(

I understand. Again, I was following the path of your documentation in which you referenced mouse macros. As far as can tell the GF Config does not accept key sequences for rotary switches. It will work for buttons and switches. We must use mouse macros to map HDG, ALT etc. BTW, you guys (ES folks) seem (whether intentional or not) irritated with questions and comments. I strongly recommend alcohol as a proven edge remover. LOL. Oh.... well, regardless, I still think you guys build excellent planes. Thanks.Bob..

Absolutely all FS input is available via keyboard. Heading, VOR course, altitude are available to be changed in FS only with keyboard input. FS doesn't have assignable joystick settings for those inputs. I find it difficult to believe that the GoFlight doesn't transmit keypresses when turning a rotary for those values.UPDATEI've reviewed information at GoFlight's web site. They apparently only understand the default FS inputs and nothing more. However, they offer a document that explains how to use FSUIPC to get their equipment to interact with addons such as ours: http://www.goflightinc.com/downloads/docs/NOTVAM2.pdfIt's something you'd have to do with other high-end addons as well.

I understand. Again, I was following the path of your documentation in which you referenced mouse macros. As far as can tell the GF Config does not accept key sequences for rotary switches. It will work for buttons and switches. We must use mouse macros to map HDG, ALT etc.

A careful read of the .pdf file that Ed provided a link for indicates that knob "rotations" are indeed supported. It's a matter of configuration using either the GF Config or the key-mapping facility of a registered FSUIPC, otherwise the example using the PMDG wouldn't work... Also, please understand that none of us owns or have access to any GF hardware, so are completely unable to provide detailed assistance with user configurations. :(

Hope it's ok to hijact the topic and ask if the VC update is going to include an overhaul of textures as well as the addition of more 3D switches and the like?Thanks.

Hope it's ok to hijact the topic and ask if the VC update is going to include an overhaul of textures as well as the addition of more 3D switches and the like?Thanks.

That is our intention but be advised it will still look and feel like a CX. :(