I checked the open issues thread, and found some FMC related issues, but wanted to run this by the group to see if my CTD is related.  I was about 6 hours into an 8 hour flight: KMIA-SBGR when I opened the FMC to add a waypoint to my flight plan.  I simply typed the name of the waypoint in, and clicked the appropriate button on the left side of FMC to insert the waypoint.  I got the hourglass for about 10 seconds, and then a CTD referencing PMDG_777X.DLL.   

 

I've seen some references to CTDs when making alterations during approach, but not directly enroute.

 

Has anyone else had a CTD when altering the flightplan during a flight?

 

Thanks,

 

John

I have had this happen making changes to the flight plan or making other FMC data requests both en route and on approach. I don't think the flight phase is important, but the approach phase is more likely to need FMC changes. The problem that I've seen occurs as you are altering the flight plan or asking for data from the FMC in some way. Any time you enter a waypoint, navaid, etc it will have to search the database to look for it. That could cause a CTD or FSX "not responding" if resources are at the limit.

 

I always have autosave running in case it happens so I can recover the flight and continue.

Yes, I've also had this once so far. The reason for the crash was not even altering the route, but just using the FMC to look up some navaid in the database.

It happened right in the middle of the Atlantic, so no heavy scenery involved. It appears that for the navaid lookup, the FMC had to load quite some data which made it cross the red line in terms of resource consumption.

 

I'm really looking forward to SP1 and the optimizations that will be included. For now, I'll leave the FMC alone when enroute, except for some direct-to's and other absolutely necessary actions. Doing so, I can fly Frankfurt-Hongkong without a hitch.

Yes, I've also had this once so far. The reason for the crash was not even altering the route, but just using the FMC to look up some navaid in the database.

It happened right in the middle of the Atlantic, so no heavy scenery involved. It appears that for the navaid lookup, the FMC had to load quite some data which made it cross the red line in terms of resource consumption.

 

I'm really looking forward to SP1 and the optimizations that will be included. For now, I'll leave the FMC alone when enroute, except for some direct-to's and other absolutely necessary actions. Doing so, I can fly Frankfurt-Hongkong without a hitch.

 

This is what I was thinking as well.  If I recall properly, the NGX had similar FMC issues prior to the service packs.  I'm looking forward to these things being worked out.

 

John

Hi, everyone,

 

Maybe the following advice from the pinned PMDG Issue Tracking thread would apply to your situation, since I believe ARPT_RNWY.DAT is a cache for the FMC's navigation data.  Restarting the T7 regenerates this file.  Just to be on the safe side you can always rename it rather than deleting it.

 

Mike

- Fixed a CTD on load that results from errors in the runways.csv or ARPT_RWY.dat files.

• If you're getting a CTD upon selecting the airplane or pressing Fly Now, please try deleting these two files. runways.csv is in the root FSX folder, and ARPT_RWY.dat is in the FSX\PMDG\NAVDATA folder. runways.csv can be remade using Pete Dowson's MakeRunways.exe tool, found at his website.