I was trying an engine failure in the MD-11 and when I tried to enter a new destination by clicking the key next to my next waypoint and entering a new destination(in this case the departure airport, KLAX), the FMC's screen had a bunch of odd characters pop up and subsequently CTD'd attributed PMDG_MD11.dll

FS9 or FSX?Andrew

I was trying an engine failure in the MD-11 and when I tried to enter a new destination by clicking the key next to my next waypoint and entering a new destination(in this case the departure airport, KLAX), the FMC's screen had a bunch of odd characters pop up and subsequently CTD'd attributed PMDG_MD11.dll

There is a chapter in the FMC manual how to deal with alternate Airports normally.The way you did, can cause a CTD and you can "kill" the J41 in a similar way, too.It seems the logic behind doesn't like using destinations as waypoints, but it would be fine to issue text like: "wrong input data" at this moment than a CTD.

I'm using FSX, and I followed the instructions in the manual. Sorry if I didn't explain that clearly.I clicked the key next to my next waypoint to arrive at the LAT REV page. I then typed KLAX and inserted in the NEW DEST box on the right side. I did this as described on FMS 80.1.Any help?

I'm using FSX, and I followed the instructions in the manual. Sorry if I didn't explain that clearly.I clicked the key next to my next waypoint to arrive at the LAT REV page. I then typed KLAX and inserted in the NEW DEST box on the right side. I did this as described on FMS 80.1.Any help?

ok, this way should work and it does every time i need this function without CTD.Did you type the primary route manually into MCDU or was it generated by any tool?feel free to post the route, i'll give it a try.Operating system? if 64bit enviroment, do you run the fsx.exe elevated? (right-click mouse => compatibility => check "always as admin") Did you or your OS update the vc++ 2008 environment? if yes, deinstall the updates only, not the redist packages! => new try

Entered it manually, route was: CASTA2 EHF J65 SAC J126 OED J501 TOU J523 YZP J501 JOH YESKA3. The flight was loaded from a saved flight. 64 bit win 7, FSX elevated(although I don't believe that has anything to do with the bit)Did not update vc++2008Thanks

Entered it manually, route was: CASTA2 EHF J65 SAC J126 OED J501 TOU J523 YZP J501 JOH YESKA3. The flight was loaded from a saved flight. 64 bit win 7, FSX elevated(although I don't believe that has anything to do with the bit)Did not update vc++2008Thanks

This seems not to be a local problem, experienced it in the meantime, too:KLAX CASTA2 EHF J65 SAC J126 OED J501 TOU J523 YZP J501 JOH YESKA3 PANC (manually input)Initial planned alternate: PACV, departure RWY 24L, AIRAC 1101, FSX@SP2, weather ASE actually patched, FSUIPC 4.60)started 4 shots with "New Destination" at waypoint SILEX in climb, every try ended with CTD. 2 times with "new" destination KLAX (one with weather one without) => each time directly freeze (test flights 2-4 were rebuild by FSUIPC autosave and weather was deactivated during climb)2 times with "new" destination KLGB (again with and without weather) => first try directly freeze, second time MCDU assumed the input KLGB and freezed after some seconds)Based on this issues did another flight in europe: LOWW - LSZH without weather, at waypoint SITNI "New Destination" LOWK worked as it should.Went back to KLAX, generated 3 totally new flights (intentional not from FSUIPC "autosave" to prevent errors due to it's pre-stored weather conditions) Test1: route KLAX-PANC (flight planned alternate PACV) with "new destination" KLGB started at SILEX again and now it worked proper (FSX "clear sky" conditions)Test2: route KLAX-PANC (flight planned alternate PACV) with "new destination" KLAX again at SILEX => CTD (FSX "clear sky" conditions)Test3: route KLAX-PANC (flight planned alternate PACV) with "new destination" KLGB at waypoint SILEX => CTD (ASE real weather conditions!)Conclusion:a) MD-11 doesn't like the "new destination" feature generally, in ASE weather conditions, every time pointing at PMDG_MD11.DLLB) MD-11 doesn't like the "new destination" feature, in case of the "new destination" is the departing Airport, pointing at PMDG_MD11.DLL again.

PMDG, please fix this bugI honestly thought the MD-11 didn't have any serious bugs until now....):

This bug is very frustrating, because with this MD-11 you get alot of realistic failures but you cant go back to the departure Aiport; just a nosense.I guess in PMDG they're very busy to make the new 737, but I hope they will still listen to MD-11's customers!!!It would be nice to get a feedback from the team about this bug.Bye

PMDG, please fix this bugI honestly thought the MD-11 didn't have any serious bugs until now....):

Just discovered that this bug doesn't occur if the FMS is switched to CRZ/ENG OUT CRZ prior to the destination being changed. Not an issue, then.

Sorry but I cant understand the sense; why I need to select ENG OUT if all my 3 Engines are working?I

Just discovered that this bug doesn't occur if the FMS is switched to CRZ/ENG OUT CRZ prior to the destination being changed. Not an issue, then.

You don't. It still works fine if your in CRZ. I was just saying that it also works in ENG OUT CRZ.

This might be associated with a known bug comes alive if you enter a destination without an enroute fix in the string. Just guessing, but try entering one fix enroute to the new destination before entering the new destination. Like I said, just guessing but worth a try. I've not played with the new destination method myself.

As far as I can tell it works fine as long as you are in CRZ mode.

Negative; I just tryed and mine works only in ENG OUT mode; in CRZ mode if I select as NEW DEST the departure airport I still get a CTD.Im' using FS9.Maybe there's a specific way to get in CRZ mode in order to donìt get CDTs?Bye

As far as I can tell it works fine as long as you are in CRZ mode.