LarsBot

Thanks scandinavian13 I will try that too, hopefully it it works. To all: using Bobs suggestion I used proc mon and confirmed that the panel is in fact NOT calling up MAGDEC.BGL at all, therefore anything to do with the registry or the file it's self is not the issue. Not sure if this is intented in the FSX version of the MD but I doubt it. Could be a limitation of Prefer3d with these old planes as mentioned before. For those who say the MD works try an autoland into Toronto or Montreal, you'll see the acft does not follow the LOC. I don't own the 747 for FSX so I can't test it and Im not about to fork out the $$$ unless I know it will work. I tried the latest AIRAC files and still no joy. I tested my FS2004 MD-11 and it calls up the magdec.bgl when loading. I will rename the magdec.bgl in 2004 and check and see if I get similar results. Again with PMDG not supporting their product in Prepar3d and Prepar3d not supportong PMDGs product it feels a bit like the NHL strike, someone needs to comprimise. As an excellent arbitrator I volunteer to arbitrate the deal!

Hi guys, sorry been on the road for a while, no go on any of this. Bob, Ive tried pointing the registry to every location I could find. Here's the thing, I ran procmon and there is no read call for magdec.bgl from the panel. I am going to try an AIRAC update since I see the files are 2008 vintage. Will reply back on the outcome.

WR269 I hope its not as bleak as that! Does anyone know what exactley the Flight1 registry fix writes in the registry? even the FSX example could lead to a conclusion on P3D.

scandanavian13 thanks for the enlightenment, not sure why you chose to even waste your time writing that response - my question was not "Is Prepard3d a supported simulator". Good news! If it was your answer would be the solution I was looking for. Till then, stop wasting bandwidth and my .3 sec to read your repsonse.

Hello All! got a brain teaser here! I'm running Prepar3d v 1.4 with PMDG MD-11 for FSX, no other addons are added - I used FSX2Prepar3d to install the aircraft. Everything works fine except the runway heading vs navigaion display and auto pilot are off. The aircraft dows not follow the localizer on ILS approach and seems to be selecting a different runway approach heading. I've read all there is to read on the subject available on the internet. The standard answer is to use the Flight 1 registry tool which I have in every concivable manner. I realize the aircraft uses the registry to steer its guages to the magdev.bgl file in the simulator (I have replaced this file). All I really need is to see the actual registry entries for some one who does not have this issue and is running the MD in Prepared. Since the flight 1 registry repair tool is kind of a black box I need to know what its output actually is in the registry and what excatly the MD is looking for in the registry (ie. EXE Path, SetupPath, etc.) Photos below show the MD in FS9 on the same KDFW rwy and station dec for VOR TTT at 6E. The other pic shows the MD in Prepar3d on the same rwy the ND display shows the rwy hdg offset of 5 deg (and TTT Stat. Dec at 00 - Im running windows 7 64 BIT so registry entries are in a different location. I appreciate any advice.