Dan,

If you are landing in the grass, start looking for a magdev error. Start with the registry repair tool from Flight1, then start turning off add-on sceneries. FS9 or FSX?

This is the same problem that I reported earlier. I have a "Help" request into PMDG, but have not received a reply. Since this is happening to a lot of folks with different aircraft (PMDG only) with different sceneries there has to be a common thread.Bill Bridges

Dear PMDG Team members,I have reinstalled MD-11 1.10 and 1.20 from scratch; however, there is no change!Although I like most this Douglas way PMDG MD-12 of the airliner, it's beautiful and manageable, this problem is very troublesome.Why cannot the AFS set DUAL LAND or SINGLE LAND but G/S APPR ONLY (track the localizer deviate from the center) sometimes? Would you please solve this problem by all means?Sincerely,Kan-ichiro Fushihara

Dear PMDG Team members,I have reinstalled MD-11 1.10 and 1.20 from scratch; however, there is no change!Although I like most this Douglas way PMDG MD-12 of the airliner, it's beautiful and manageable, this problem is very troublesome.Why cannot the AFS set DUAL LAND or SINGLE LAND but G/S APPR ONLY (track the localizer deviate from the center) sometimes? Would you please solve this problem by all means?Sincerely,Kan-ichiro Fushihara

Hi Fushi, You seem to have two seperate issues, 1) localiser on the grass and 2) unexpected landing mode. The first issue is not PMDG specific as it doesn't affect Cuddly or me but has been reported by others, including non PMDG users and is usually associated with magnetic varience. I would suggest a few searchs might provide clues or diagnostics steps which might help. The second issue, your unexpected landing mode indications, looks to me like you are in "FD Only ILS Operation" as described in the Systems manual, page AUTO.10.15. Perhaps if you review your landing procedure step by step, the fault might become apparant. /Paul.

I noticed one critical thing in your picture at JFK: The Runway on the ND is off set from the actual runway. Try disabling any recently added scenery. Even small airports can do this; I once had the issue caused by FT SAN.

I noticed one critical thing in your picture at JFK: The Runway on the ND is off set from the actual runway. Try disabling any recently added scenery. Even small airports can do this; I once had the issue caused by FT SAN.

Thank you for your valuable advice, I have been recently noticed the off set of runways, too.As you said, I disabled all add-on sceneries; however, the off set of runways hasn't been corrected. It must be true cause, if you could, help me further please.Sincerely,Kan-ichiro Fushihara

Has it always been the case? I usually solve the issue with a system restore because I notice it within 24 hours. I would backup your addons and try and restore the computer to before the runways were offset.

Dan,This is the same problem that I reported earlier. I have a "Help" request into PMDG, but have not received a reply. Since this is happening to a lot of folks with different aircraft (PMDG only) with different sceneries there has to be a common thread.

As shown above the only aircraft that are not working correctly are the PMDG aircraft. If the Magdec.bgl file was corrupt, then all the aircraft would be having the same problem. I have received one message from PMDG help and it was "No Help". My only hope is my B747-400X doesn't turn into a $75.00 albatross, because it sure will not track the LOC.Bill Bridges

I had a recent issue with EGLL Mega Airport... I ran the F1 reg fix and everything was sorted... I only noticed it in the MD-11 as that was the only aircraft I had used onto the affected runway (one of the 09s), the 27s were fine when I had used the Wilco A320...I really believe that this is NOT a PMDG issue, this is either a magdev issue, possibly being exacerbated by a more recent addon, or the registry issue...If this WERE an issue with the PMDG aircraft, I am sure a LOT more people would be blowing their trumpet here or by private communication with the developer team...

I noticed one critical thing in your picture at JFK: The Runway on the ND is off set from the actual runway. Try disabling any recently added scenery. Even small airports can do this; I once had the issue caused by FT SAN.

That is DEFINITELY a sign of a scenery/magvar issue if the runway displayed on the ND is canted off at an angle vs. where it is in the actual outside view.

That is DEFINITELY a sign of a scenery/magvar issue if the runway displayed on the ND is canted off at an angle vs. where it is in the actual outside view.

Then why will the PMDG aircraft not track the LOC when there isn't a flightplan loaded? When LOC is pushed the aircraft should track the LOC (B747). Bill Bridges

As shown above the only aircraft that are not working correctly are the PMDG aircraft.

I am sorry Bill but what, exactly, is the problem you believe to be PMDG specific?

I am sorry Bill but what, exactly, is the problem you believe to be PMDG specific?

The problem is the inability of the PMDG aircraft to track the LOC while other aircraft can. This is shown in the two pictures above. I am experiencing the same problem with my B747-400X. It will not track the LOC, but the default MS aircraft and my Coolsky MD-82 will track the LOC on the same LOC course. I have been exchanging e-mails with PMDG support for the last 5 days. I send them a help request, I get a receipt from them, two days later they send a response, I respond, get a receipt, then two days later I get another question, I respond, get a receipt and I should be getting a response tomorrow (hopefully). This is the same problem as outlined in this thread "747 AIRAC data not working... I think" last posted on June 29, 2009 on this forum.Bill Bridges

Captains,I have tested PMDG MD-11 on my old machine (AMD +2400, Windows XP) with fresh installed FSX +SP1 +SP2. Since no problem occured, this problem should not be PMDG's own. As Paul-Smith said, there are two issues:1) ILS localizer doesn't capture and hold the ND-11 in the LOC beam. This isn't allowable!!! It seems that the clause is corrupted Magdec.bgl file or registry issue..., I would like to know the measures to solve the problem.2) Unexpected landing mode has displayed. Although I have correctly carry out step by step the procedures, as an example, 'SINGLE LAND' on the LSGG 05 and 'APPR ONLY' on the LSGG 23 have been displayed??? However, I will tolerate this inexactitude compare with the landing on the grass.Sincerely,Kan-ichiro Fushihara

2) Unexpected landing mode has displayed. Although I have correctly carry out step by step the procedures, as an example, 'SINGLE LAND' on the LSGG 05 and 'APPR ONLY' on the LSGG 23 have been displayed??? However, I will tolerate this inexactitude compare with the landing on the grass.

Kan-ichiro,this isn't PMDGs fault either. The MD11 autopilot has certain conditions to be met at a certain stage of the approach to be able to go into dual- or single-land. So the next time you do get an APPR ONLY please note EVERY step you took during the approach including these items:- altitude- speed- configuration- FCP buttons pushed- airfield elevationThat way we'll quickly spot the error in your procedure.Regards,Markus

Dear Markus,Thank you for your kind advice,I have done the test an autoland as you said on the RJGG 36 ILS (CAT IIIA Avbl. on the n DAC 3).- altitude: 3500- speed:159- configuration: OK- FCP buttons pushed: 'LAND ARMED'- airfield elevation: 15The 'APPR ONLY' hasn't changed!If you agree, I will send you the 3 Flight Simulator X Files (PMDG MD-11 RJNH 27 for RJGG.XXX). Sincerely,Kan-ichiro Fushihara