Encountering some Navdata discrepancy at some airports such as KLAS(in attached screenshot), where airport rwy data doesn't match scenery.In this example using FSDreamteam KLAS. Happens with the default Magdec fileand with the 2010 update also. Any ideas how this can be solved? Is this somethingthat should be notified to Navigraph?Thanks

Encountering some Navdata discrepancy at some airports such as KLAS(in attached screenshot), where airport rwy data doesn't match scenery.In this example using FSDreamteam KLAS. Happens with the default Magdec fileand with the 2010 update also. Any ideas how this can be solved? Is this somethingthat should be notified to Navigraph?Thanks

The AIRAC headings are correct...DJ

Have you tried the Flight1 Registry repair tool? It should fix your issue. Also what's up with your EICAS? Lots of problems going on there, it also looks like you forgot to go tank to engine at some point.Regards

Thanks, the discrepancies in the panel due to reloading an autosave flight without any proper config and simply to showdiscrepancy on the display between fsdreamteam runway orientation and AIRAC runway display. I have placed 2 separate non PMDG aircraft on same rwy 01L and everything displays correctly. This would indicate to me that there may be an erroron the PMDG 1201 AIRAC for this runway. Will contact Navigraph.

Thanks, the discrepancies in the panel due to reloading an autosave flight without any proper config and simply to showdiscrepancy on the display between fsdreamteam runway orientation and AIRAC runway display. I have placed 2 separatenon PMDG aircraft on same rwy 01L and everything displays correctly. This would indicate to me that there may be an erroron the PMDG 1201 AIRAC for this runway. Will contact Navigraph.

Here is the relevent data from 1201 AIRAC for PMDG:LOS ANGELES INTERNATIONAKLAX06L08925069 33.949109-118.431156108.5006900112LOS ANGELES INTERNATIONAKLAX06R10285069 33.946853-118.434239111.7006900108LOS ANGELES INTERNATIONAKLAX07L12091069 33.935825-118.419336111.1006900119LOS ANGELES INTERNATIONAKLAX07R11095069 33.933645-118.419014109.9006900119LOS ANGELES INTERNATIONAKLAX24L10285249 33.950189-118.401664111.7025000111LOS ANGELES INTERNATIONAKLAX24R08925249 33.952100-118.401945108.5024900117LOS ANGELES INTERNATIONAKLAX25L11095249 33.937359-118.382708109.9024900098LOS ANGELES INTERNATIONAKLAX25R12091249 33.939553-118.382906111.1025000094The runway headings are in bold...DJ

Thanks, the discrepancies in the panel due to reloading an autosave flight without any proper config and simply to showdiscrepancy on the display between fsdreamteam runway orientation and AIRAC runway display. I have placed 2 separate non PMDG aircraft on same rwy 01L and everything displays correctly. This would indicate to me that there may be an erroron the PMDG 1201 AIRAC for this runway. Will contact Navigraph.

It could very well be an AIRAC issue.I still think you should try the flight1 repair tool. It has fixed issues like this in the past on the PMDG 744 and MD11Regards

http://www.flight1.com/view.asp?page=library has the flight1 registry checker download link. Installing and removing the FS versions can result in incorrect versions. If running VISTA or Win 7 be logged in with admin rights and also right click on the .exe and select run as admin, a program level access privilege in addition to user level access.

Good news, I ran the registry fix and that seemed to make it work OK. However this installation of FS9 was only made a couple of months agoand cannot understand why the registry fix solved it. All installers so far seemed to be able to find FS9 directory before the fix applied.Thanks for the advice everyone.

Good news, I ran the registry fix and that seemed to make it work OK. However this installation of FS9 was only made a couple of months agoand cannot understand why the registry fix solved it. All installers so far seemed to be able to find FS9 directory before the fix applied.Thanks for the advice everyone.

I don't think anybody quite understands what is going on with this... it happened to me a while back, more or less out of the blue and there was nothing visible wrong with the registry. I ran the registry fixit for lack of any better idea and it worked. If you look through the PMDG forums there have been a number of folks who have had this issue for no particular perceptible reason. Whatever - glad it's fixed.DJ