Support is a two way street; no one can be helped who refuses to use the proper venue for support, and is unwilling to engage in a diagnostic dialogue.

 

I used the "proper venue" and got nowhere because all I ever got in the way of support was to be told that Eaglesoft could not reproduce the error.

 

But the problem still exists on my system or rather did as I deleted the CX a long time ago after wasting to much of this short lifetime trying to get it to not lock up @ 70nm from the destination.

By far my favorite addon and not getting to complete a flight with it pretty much had me giving up on Flight simulation altogether.

Thankfully P3Dv2.2 came along and a fresh start.

Great addon and risk free with the 30 day money back guarantee, just wished it would work properly on my rig.

Just to let people know, as it has been said, the problem seems to be the Navdata incompatibility with other add-ons that seem to share the Navigraph database with Eaglesoft, but is not more than just that: appearance.

Seeing that the database looked like the same, I overwrote the Eaglesoft with the one I had from Wilco Airbus, where I added a fictional airport that I built myself, as well as some airports in remote China and Himalayas that lack in the default Navigraph database, and whenever I was flying and deleted a waypoint on the Citation X FMS to fly direct to another one, the MFD froze. I then installed the Navigraph database for Eaglesoft itself yesterday night and so far it went perfectly. Today I'll try to add those missing airports and my private/fictional one to the Eaglesoft database and see how it goes.

You can't just 'add an airport'. The database isn't a free-flow do-as-you-please design. There are multiple tables that interact and you're really playing with fire.

 

In short, the database format was chosen so people would be less likely to do what you're doing.

Yup! I know that. First time I went to add them to te Wilco database I opened the MS Access file and got mad at it  :blink: "what's this?". Well, but after all I managed to understand how it worked and added them with no problem. At least for Wilco Airbus.

 

 

Yup! I know that. First time I went to add them to te Wilco database I opened the MS Access file and got mad at it :blink: "what's this?". Well, but after all I managed to understand how it worked and added them with no problem. At least for Wilco Airbus.

 

So, is the body of evidence pointing to bad data from Navigraph that the Citation X is having trouble with?

Greg, no point in idle speculation as we can't verify what users are doing locally and what they may assume will work...
The success stories are still present in our forums and you can reread at your leisure. B)