That's right fixed! First I like to thank Ryan Maziarz and Paul Gollnick and also Al Jordan (jordanal) for all their help and support in trying to find and fix the problem, even providing me a new download link on the chance of a bad download! All of these though didn't work! Then I did some research on other reported problems and came across a registry repair tool for FSX (and FS2004) by Flight1. It says it fixes the path for FSX in the registry which sometimes is invalid, causing addon not to install. Well my FSX always reported the correct path, and was also correct in the registry, and I never have had any issue installing an addon before, so I wasn't going to run it. On second thought, I decided to try it, and low and behold it fixed the problem! My 744X has just been released from the Maintenance hanger!!!! So anyone who is having this problem, give this registry repair tool a shot, it sure worked for me!!! Here's a shot with the correct bearing to MEALS from JFK!Again I'd like to thank all those who helped, and hope this also fixes the other affected users 744X, so they can get the Queen back in the virtual skies where she belongs!!! http://www.flight1.com/view.asp?page=libraryThis is a shot showing the problem Note MEALS is on a bearing of 121 which is the true heading for Runway 13R KJFK. It should be at the Entry of the ILS for Runway 31L about 7.2 miles away on Runway heading of 135.http://forums.avsim.net/user_files/188158.jpgNow here is how it is now Fixed.http://forums.avsim.net/user_files/188159.jpg

Excellent, Tom, I'm glad this bug was found.These problems are never easy, and often take serindipity. The original bug was a moth stuck in a relay of one of the first generation computational machines.. in this context, you found the moth.

Woooooohooooooo!!!!!!!!! :-yellow1 :-walksmile :-beerchug :-jumpy :-wave

Tom,Glad to hear your up and running. Will have to put that in the data banks for future use. Now Enjoy!!RegardsPaul Gollnick :-cool Technical Operations/Customer Operational SupportPrecision Manuals Development Groupwww.precisionmanuals.comhttp://www.precisionmanuals.com/priv/img/forum/sig_pmdg.jpg

Very interested to see if this works for the others having the issue... I didn't even think of this. If the FSX registry info is wrong somehow from the very start then PMDGOptions.dll doesn't know where to find the magdec.bgl, which explains the blanked magnetic variation in the FMC.Fingers crossed that this is actually the core issue!

I just flew my first transatlantic flight today, from EGCC to KMCO and the queen tracked beautifully, and I brought her in on a perfect ILS approach to Runway 35R, I normally fly landings in manually to get practice, but I wanted to test out the autoland systems with the ND fixed. They worked flawlessly! Thanks again for everything, and I hope this fixes it for everyone else affected by this!!

woohoo! still dont know what was wrong with it, but it works now. my 737 and 747 are sprung from the hangar.Thank you times a million :)

>woohoo! still dont know what was wrong with it, but it works>now. my 737 and 747 are sprung from the hangar.>>Thank you times a million :)That makes 2 --- Looking good!!!

Although I have not had this issue, I am thrilled to hear of it being solved by this simple fix! It's great to think that now you can get back to doing what we all love, flying our PMDG birds!Tim

Ok that's a VERY good sign that 2 separate people with the issue had it fixed by this... we may have found the gremlin folks!

Hopefully now we can finally see the long awaited update. I am beginning to despair at ever seeing the B737NX in the near future at this rate.John Veldthuishttp://www.virtualpilots.org/signatures/vpa475.png

Fixed my FS9.1 skewed ND and related problems with this program some months ago.See: http://forums.avsim.net/dcboard.php?az=sho...e=search#143596Regards,Harry

For posterity sake of this thread, what exact registry entry could be hosed besides the actual FS9 or FSX installation path? Tom indicated that he beleived his FS path was correct to begin with. Are there other pertinent paths that the F1-utility fixes besides the standard FS install-path?We seemed to have found the problem and fix it, but the question remains, what caused it? Tom, can you think of any add-ons or processes you may have done to change any of the FS related paths? For example, did you install or de-install other aircraft or scenery? Did you by chance ever run a registry cleaner that could have possibly changed the the relevant paths?I think the cuase of the paths changing lies somewhere in the commonality of the two folks that this seems to have fixed to date. Perhaps you two should compare build-notes and software-inventories. That might lead us to the root-cuase.

In search of commonality, this is what I did on my 'OLD' computer.Uninstalled FSXdeLuxe in order to install it on a new computer.Installed FSX Standard on the old one.A couple of weeks later, when flying the FS9.1 PMDG744 (version1.1) I observed several abnormal behaviors:- LNAV not tracking magenta line- AP LOC tracking offset- Autoland touchdown outside RWY boarder.Was able to correct this by running the Flight1 registry repair tool.Regards,Harry

>Fixed my FS9.1 skewed ND and related problems with this>program some months ago.>>See:>http://forums.avsim.net/dcboard.php?az=sho...e=search#143596>>Regards,>>Harry>Hmm, it was under our noses all the time!!! I never looked at that post, as it specifically stated it was for Installation problems for FS9.1. Now we know FSX is affected itself by this!!