Kan-ichiro,this isn't PMDGs fault either.

Why do you say that? PMDG aircraft are not freeware; they are very expensive. This is a problem has been reported by three people on this forum in the past 10 days. If there is a problem with the interface between PMDG and FSX then it seems that PMDG should provide a solution that will allow the owner of a PMDG product to repair the problem. If the magdec.bgl is corrupt, why can't PMDG provide a new or revised copy? You can not to the best of my knowledge download a new copy off the FSX install disk. Reinstalling FSX is not a solution, it is a band-aid. Bill Bridges

The offset localizer at JFK is on 22R I believe.. the approach to 31L works okay for me. Hope this helps a little.

That's good to know; I wrote that off as a MSFS issue. I guess it would help to look at the approach plate every once in a while. :(

Why do you say that?

Bill,I was referring to the AFS reverting to APPR ONLY when conducting an ILS approach. Michael has programmed all the requirements for the AFS to go into SINGLE or DUAL LAND. This is an entirely different issue and should not have anything to do with a LOC deviation or MAGVAR issue...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

Fushi,Try this. When you run the Flight 1 registry tool make sure that "you point it to the FSX.exe file (looks like the FSX Icon) in the FSX Folder." I am not sure about the MD-11, but on the B747-400X FMC go to the "REF NAV DATA" page. Enter the name of a navaid such as TTT under IDENT for example if you are at KDFW. If evertything is working correctly there should be a magnetic variance under the MAG VAR line. In the case of TTT it should be something like E4.6. If it reads E0.0 then the registery did not update or possibly the magdec.bgl is corrupt. Let me know and I will tell you where to get the magdec.bgl file.Bill Bridges

Fushi,Try this. When you run the Flight 1 registry tool make sure that "you point it to the FSX.exe file (looks like the FSX Icon) in the FSX Folder." I am not sure about the MD-11, but on the B747-400X FMC go to the "REF NAV DATA" page. Enter the name of a navaid such as TTT under IDENT for example if you are at KDFW. If evertything is working correctly there should be a magnetic variance under the MAG VAR line. In the case of TTT it should be something like E4.6. If it reads E0.0 then the registery did not update or possibly the magdec.bgl is corrupt. Let me know and I will tell you where to get the magdec.bgl file.Bill Bridges

Dear Bill,Thank you very much for your kind advice. I have checked IDENT: TTT on my B747-400X FMC at KDFW and the MAG VER line is E0.0

Fushi,

Dear Bill,Thank you very much for your kind advice. I have checked IDENT: TTT on my B747-400X FMC at KDFW and the MAG VER line is E0.0

Dear Bill,Scceeded!!! Thank you very much indeed.With IDENT: TTT on my B747-400X FMC at KDFW, the MAG VER line has become E4.1

Thanks guys. This thread helped me also. I was having the same problem with the MD-11. The only thing that I can think of that I changed lately was the ntcore 4GB fix to FSX so the game will use 4GB instead of 2. It must have done something to the FSX file. I ran the Flight 1 patch and I'm back in business. Thanks again.

Good to see that this issue has been cleared up! :)As I said in my previous post on this issue, not a PMDG error, and the F1 registry repair tool does its tricks!:)Andrew