Hi everyboby,I've just bought the MD11 it's a great aircraft.But i've recently observed an issue concerning the FMS coupling with the autoflight.During take off after about 400-600 feet FS9 freezed up. Just the sound was still active but not changing and the dispay was freezed.I've made the same scenario again, same airport, same weather, same FMS configuration, but after more tries I've found what the problem was:I was at Marseille airport LFML to make few runway patterns for training. I planned to take off runway 31R, so on the FMS I entered the to/from LFML/LFML and the star ILS 31R with a transition MTG. I've cleared few "FPLN Discont" lines but one was still remain, just after the first line (LFML) and MTG. When taking off at about 400-600 feet the magenta NAV ARMED on the FMA became active and BOUM my display freezed up !-I made the same flight with the "FPLN discon" line cleared on the FMS and everything was perfect.-I made the same flight with the "NAV ARMED" off, on the FMA, with the "FPLN DISCONT" line on the FMS, everything was ok, no freeze.The conclusion is, Display freeze up when the "nav armed" get engaged at 400-600 feet after take off, and the next line on the FMS is a "FPLN DISCONT."If anyone had the same trouble...Julien

Julien: Freezes and CTDs do occur to a few users, most are noted in the forum, but the vast majority do not have these problems. While it may look like a pmdg problem because it only happens while using the simulation, there have not been many cases where the problem turned out to be there. The MCDU interface might have a problem in your case, where you are flying with a known flight plan error. I personnally did not try the same sequence, so cannot rule it out yet but I will give it a try. I assume then that your flight plan indicates a runway, then a disconnect then the remainder of the flightplan. Is that correct? Did you select the departure runway?I have flown local flightplans many times, to clear disconnects I select the departure runway and a fix or navaid as the first fix. It doesn't matter that I don't intend to fly to that point, but then I can select the STAR with an LATREV from it and avoid all kinds of problems, which I suspect you are describing one of. I take off with heading, and use headings to vector myself to the STAR or IAF of the approach I am playing with. Once vectored into position, I use the direct-to to select the point where I want LNAV to take over.Anyway, back to your problem: We know that you cannot select a STAR by going LATREV from the destination. The real aircraft rejects this as well.. there has to be an enroute fix from which you LATREV to the STAR page. Hope this helps.

Anyway, back to your problem: We know that you cannot select a STAR by going LATREV from the destination. The real aircraft rejects this as well.. there has to be an enroute fix from which you LATREV to the STAR page. Hope this helps.Hi Dan, thanks for your answer, I understood the procedure you described above and I will do it in the futur. I'm quite sure this kind of matter will not happen again in that way. But meanwhile I'm disapointed to know that my FS9 can bugged at any time my FMS is not set properly. In the reality aircrafts not freeze in the air ! :( I try to look forward and hope my MD 11 is not installed properly, so I will install it again and see what's happen.I'm still thinking something's strange about all of this, ie: I've performed the same example at EGLL with only departure on FMS "EGLL" then the STAR (09L) transition CHT, and the famous FMS line FPLN Discont, no freeze happened. I desinstalled Marseille LFML aerosoft scenery, just in case, and try again with the same configuration, and you know what : first take off OK, second take off after landing with the configuration set back on the FMS then FS9 freezed !!What a hell is going on ?Julien

I can observe on the forum few topics about the same issue, nearly the same.It was always about the FMS settings.If it can help...Julien.

I can observe on the forum few topics about the same issue, nearly the same.It was always about the FMS settings.If it can help...Julien.

Julien, is the freezing followed by a Microsoft message saying "Flight Simulator has encountered a problem and needs to close"? If so, click where indicated on that message to find out the module responsible for this and post back to let us know. We might be able to help.Iain Smith

Julien, is the freezing followed by a Microsoft message saying "Flight Simulator has encountered a problem and needs to close"? If so, click where indicated on that message to find out the module responsible for this and post back to let us know. We might be able to help.Iain Smith

Iain, thanks for your help. I don't remember the first errors messages, but the last one was "pmdg md11 gauge" this the display was black before closing fs9 !I'm getting tired with this add-on though it is very nice I won't use it any more. Here is a discussion I've had with a PMDG staff member about this issue.1/"Julien,This is a known issue and a shortcoming of trying to emulate the FMC within the limits of FS9. Since the FMC is a core gauge file of the MD11 aircraft, any errors in the FMC can cause the entire sim to freeze. The only work around is to program a valid flightplan without Discont

Hi Julien, seems that the best thing to do is as Paul suggests, avoid disconts in your flight plans. I don't see this as too much of a problem as I'm sure in real life crews would not take off with a discont in their plan. :( Iain Smith