Hi all, i'm a new guy to these PMDG forums. So sorry if I ask something that has already been asked.

 

I own every pmdg product for FSX and they all run beautifully. They have all been bought from Aerosoft and they are all hardcopy versions.

 

The MD-11X has been running great until recently. I have attempted 4 flights and every time I reach 4,000 feet ASL FSX ctd. The guys over at Aerosoft told me to post here.

 

Any help in solving this ctd issue would be great.

 

thank you

brandon garcia

 

 

Any help in solving this ctd issue would be great.

 

I wish I had an idea for you, but I'm drawing a blank.  I'm sure a few of the other guys will have ideas, but in the mean time, you can get support from PMDG directly by submitting a ticket at support.precisionmanuals.com.

Hey Brandon,

 

Does this happen at every airport you depart from?

Hey Brandon,

 

Does this happen at every airport you depart from?

Hello Rob. It happens at any airport.

 

I will go to PMDG's website and submit a formal request for help. When I submit a ticket, do I include the Aerosoft activation code that is in the DVD-Rom case?

 

brandon garcia

Hello Brandon,

 

take a look at the following posts: 

 

http://forum.avsim.net/topic/412826-md-11-crashes-on-selecting-sid-or-star/

 

 

It is important that your route has no discontinuities and the distance between T/C and T/D is sufficient to allow a normal CRZ phase. 

 

Form your report, it seems that the FMS reaches T/D before T/C. Thats one of the causes for CTDs, because the FMS doesn't sequence properly through CLB, CRZ and DES phases. 

 

 

Jan-Paul

Hi Guys,  Thank you for the responses. Just did a flight without programming the fmc and FSX did not ctd. So the error of t/d and t/c must be the ticket.

 

Thank you guys again and I will post if it happens the next time I fly an actual route.

 

brandon garcia

Hi,

 

What is the route you are trying to fly?

 

I've never seen a CTD climbing out of an airport, but I HAVE seen a CTD related to go-around when the cruise altitude results in a the ToC being after the ToD point. It won't CTD immediately, but you can be assured it will.

 

If you want to use the FMS to fly between two very close airports (e.g. EGLL and EGKK) you need to ensure the cruise altitude is low enough that ToC occurs before ToD. A nice way to check is if the whole distance is e.g. 80 nm, then your cruise alt wants to be no higher than 8000 ft in order to be sure the FMS has some time at cruise altitude.

 

The same CTD can occur if you simply keep climbing (the FMS continually computes the ToC/ToD point) or select a very high altitude in the FCP.

 

FIX:

 

The only way to nail this particular bug is to put a very distant waypoint in the flight plan. I add NPOLE before the point that will result in the crash, so the aircraft thinks it has thousands of miles to fly before ToC, and thus ToD is a very long way away too.

 

Once the aircraft is down at a good altitude for the rest of the descent, dial in a cruise altitude in the FCP (e.g. 3000 ft) and tell the FMS in the INIT PAGE 1 that the cruise altitude is 3000 ft (enter 030 at LSK5L). Once this is done and the aircraft has levelled off, you can do a DIR TO as as desired to the next waypoint in the flight plan, and engage PROF/NAV as normal.

 

It sounds complex/like a lot of work but really it isn't, and once you've done it a couple of times, you learn to pre-empt it ahead of time so it won't crash.

 

If you have plenty of distance, then there is no problem. It is only in the short segments that it is a problem, when the FMS is in CLIMB phase.

 

Best regards,

Robin.