Hello,

 

I have troubles with the Eaglesoft Citation CX2.0: during descent, the MFD freeze and the frame is reduced significantly.

Eaglesoft doesn't reproduce the problem and is not able to fix it.

 

 

I would to know if someone has a workaround ?

I love so much this plane but it's not flyable like this.

 

Thanks,

 

Vincent

There are many who have this problem but it will not be fixed any time soon.

Shame really as it was my favourite Addon but the gauge programmer has now moved on to other things as far as I can make out.

      

Posted 02 December 2013 - 06:06 PM

 

"Dunno if the Navigraph database is the issue or not but I've been keeping mine up to date and no issues in the past 4 months or so."

 

From our forum: Chris, this is the only lead we've considered because as you've shown, no issues in 4 months. B)

With all due respect Ron, none of my other addons that use Navigraph data have their displays freeze, only the CX

With all due respect Mad Dog the Navigraph DB for the CX2.0 is built specifically for Eaglesoft Products and contains specific tables the others may or may NOT contain.

At any rate we have the only clue in that a user reports NO freeze in over 4 months by keeping the Eaglesoft specific/Navigraph DB updated.

We are of course still unable to duplicate the issue ourselves but the above seems to be a probable solution.... B)

With all due respect Mad Dog the Navigraph DB for the CX2.0 is built specifically for Eaglesoft Products and contains specific tables the others may or may NOT contain.

At any rate we have the only clue in that a user reports NO freeze in over 4 months by keeping the Eaglesoft specific/Navigraph DB updated.

We are of course still unable to duplicate the issue ourselves but the above seems to be a probable solution.... B)

The Aerosoft navdata for the Eaglesoft CX is supposed to be compatible, but I've had definite issues with it, ranging from approaches being improperly formatted in the FMS, to program freezes. However, the Navigraph CX database always works perfectly.

 

I have no problems with the Aerosoft subscription data in any of my other add-ons, but there is definitely something amiss in their version of the CX DB.

 

 

Sent from my iPad using Tapatalk HD

Posted Today, 09:44 PM

N400QW, on 06 Dec 2013 - 7:00 PM, said:

With all due respect Mad Dog the Navigraph DB for the CX2.0 is built specifically for Eaglesoft Products and contains specific tables the others may or may NOT contain.
At any rate we have the only clue in that a user reports NO freeze in over 4 months by keeping the Eaglesoft specific/Navigraph DB updated.
We are of course still unable to duplicate the issue ourselves but the above seems to be a probable solution.... B)

 

The Aerosoft navdata for the Eaglesoft CX is supposed to be compatible, but I've had definite issues with it, ranging from approaches being improperly formatted in the FMS, to program freezes. However, the Navigraph CX database always works perfectly.

 

NOTE TO ALL! Navigraph built a DB to specific Eaglesoft needs and their installer places updates to a specific location via registry and as does our installer.

Eaglesoft does Not use the generic Navigraph DB nor does it use the Aerosoft DB! Those who use any other than the specific Eaglesoft DB from Navigraph do so to their detriment.

Why folks would assume that the other DBs will "fill the bill" is beyond us.... :blush:

 

 

 

 

 

 

 

Why folks would assume that the other DBs will "fill the bill" is beyond us....

 

Ron

 

Perhaps you need to have a word with Aerosoft to stop them supplying their Eaglesoft navdata if it is not compatible.

 

Did they not speak to Eaglesoft before selling this stuff for your products ?

 

From their Navdata pro site:

 

The following add-ons are supported by NavDataPro:

• Aerosoft AirbusX Extended/Standard (FSX; Prepar3D)
• FlightSim Commander (FSX; Prepar3D)
• FS Navigator (FS2004)
• aeroSystem 737 Avionics
• AivlaSoft Electronic Flight Bag
• CaptainSim 757/767 (FSX; Prepar3D; FS2004)
• Digital Aviation Piper Cheyenne (FSX; Prepar3D; FS2004)
• Eurowings Professional (FS2004)
• EADT KLN 90B (X-Plane)
• Eaglesoft Cessna Citation (FSX; Prepar3D; FS2004)
• Flight1 ATR 72, BN2-Islander, C182T, Fokker, Mustang, Super 80 Professional (FSX; Prepar3D; FS2004)
• FSBuild 2.4
• FsXPand - Flyware (FSX; Prepar3D; FS2004)
• iFly Boeing 737 (FSX; Prepar3D; FS2004)
• Integrated Simavionics (FSX; Prepar3D; FS2004)
• JRollon Planes CRJ200 (X-Plane)
• Level-D 767 (FSX; Prepar3D; FS2004)
• PMDG alle Produkte (FSX; Prepar3D; FS2004)
• Pointsoft PRO-ATC/X
• Prosim 737
• PSS Boeing 777; A330; A340 (FS2004)
• QualityWings 757 (FSX; Prepar3D; FS2004)
• QualityWings Jumbolino (FSX; Prepar3D; FS2004)
• Sim-Avionics Flightdeck Avionics
• TuneVNAV Descent Pro3
• vasFMC
• X-FMC (X-Plane)
• Wilco/Feelthere 737/777 Airbus, Citation X, Embraer E-Jets v.2, Legacy (FSX; Prepar3D; FS2004)
• Ideal Flight 10
• AivlaSoft Electronic Flight (FSX; Prepar3D)
• 777 Worldliner Professional/Extended (X-Plane)
• Boeing 757 Professional (X-Plane)
• JARDesign A320neo (X-Plane)
• JeeHellWare
• FJCC Universal FMC (X-Plane)

"Did they not speak to Eaglesoft before selling this stuff for your products ?"

 

From their Navdata pro site:

 

The following add-ons are supported by NavDataPro:

• Aerosoft AirbusX Extended/Standard (FSX; Prepar3D)
• FlightSim Commander (FSX; Prepar3D)
• FS Navigator (FS2004)
• aeroSystem 737 Avionics
• AivlaSoft Electronic Flight Bag
• CaptainSim 757/767 (FSX; Prepar3D; FS2004)
• Digital Aviation Piper Cheyenne (FSX; Prepar3D; FS2004)
• Eurowings Professional (FS2004)
• EADT KLN 90B (X-Plane)
• Eaglesoft Cessna Citation (FSX; Prepar3D; FS2004)

 

 

As a matter of fact NO ONE from Aerosoft contacted us regarding any of this and we certainly have NOT TESTED nor do we endorse any other DB than the aforementioned Navigraph DB specific to Eaglesoft Development Group.

Aerosoft probably didn't contact any developer regarding their database formats.  I'm willing to bet that all they did was review the database format and contents and then fill it with their own data based on what they thought the contents were.

 

I can assure you that Aerosoft didn't get it 'right' for the Eaglesoft product.

Great,

Now that we have the only man in the world who can fix this issue joining the thread, can we hope for some work to finally sort this problem for those of us that love the CX but still have these issues.

From our newly updated forum threads on this subject:

 

Does Eaglesoft use other than Navigraph Navigation Database specific build for Eaglesoft Aircraft?

No. All Eaglesoft FS9 or FSX Corporate and General Aviation Aircraft use ONLY Navigraph specific for Eaglesoft Navdata Database for its Navigation!
ALL others are neither tested or supported by Eaglesoft Development Group!

 

 

Note: Ed will NOT be doing anything regarding support for Aerosoft DB with Eaglesoft Aircraft. That is the sole responsibility of that developer. NOT OURS!

fwiw, I used the nav data that came with the airplane and no other.  This was years ago and the exact problem being described by the o.p was popping up with quite a bit of regularity.  So if the problem hunt is going in the direction of aftermarket navdata being the culprit, this might be something to consider.

 

Seconds after I posted the above, it occurred to me that it might not have been the last airplane installed that shared the navdata.  I might have subsequently installed something like (F1 Mustang?) or some plane that overwrote the original Navdata that came with the Citation X, so maybe what I wrote above isn't entirely true, now that I think of it.  In no case, however, did I use any Aerosoft data.

During the installation, it appears that the Aerosoft DB installer uses the same DB for the CX as they do for FeelThere aircraft. (E-jets etc.)

 

I noted long ago that the Eaglesoft and FeelThere databases EXTERNALLY appear to be the same. They are both the same size, and appear to both be generated by Microsoft Access, but that doesn't mean they are INTERNALLY the same. As Ron mentioned, Eaglesoft uses tables specific to their product, that may not be present in the FeelThere version, or may not be formatted the same.

 

The responsibility for fixing the incompatibility rests on Aerosoft's shoulders. I would think that if they would reach out privately to Eaglesoft for help on making their database fully CX compliant, that ESDG would provide them with whatever information they need.

 

But, I agree with Ed, that it is not Eaglesoft's responsibility to chase after Aerosoft and try to get them to fix the problem.

 

Navigraph site has a specific build for Eaglesoft Development Group.  That is the version used for updates to airac cycles.

That Navigraph/Eaglesoft build uses a specific installer path designated by Eaglesoft and other devs may or may NOT use such paths.

NO other dev has contacted us regarding any of the above so it's a fair guess that F1 does NOT use the same path or data as does Eaglesoft.

 

This has now become one of our main concerns in that folks may be using wrong DB and we will not support such!

 

"The responsibility for fixing the incompatibility rests on Aerosoft's shoulders. I would think that if they would reach out privately to Eaglesoft for help on making their database fully CX compliant, that ESDG would provide them with whatever information they need."

 

To date they've not contacted us and by now we are not amenable to working with them on this issue.

"But, I agree with Ed, that it is not Eaglesoft's responsibility to chase after Aerosoft and try to get them to fix the problem."

 

Going to market with something they've assumed as compatible is on Aerosoft, NOT on Eaglesoft.