Thanks Ryan for the explanation. Best regards,Jim Young

It's the two different applications of magnetic variation... airports have their own and so does the world as a whole. The local variation at LAS is 2 degrees off from what the world variation below that same spot is. That's where we think the mismatch happens.

Hello Ryanthanks for clearing that up, I am going for SET FSX LOC CRS ON and ignore what FScommander tells me from now on.

Taking a look at the real apt diagram 35l shows a heading 257.5, somebody that knows better that me can explain why is 257 here instead 255?

Yes the map in FSX shows 255 as the ils for both runways but the heading while on the runway in the plane is 257. Just another FSX glitch !!

Make sure you don't get confused between true and magnetic headings. Your inertial system will navigate using only true headings whereas your VOR ILS etc are set to magnetic headings.vololiberista

Good news guys - we took another look and figured out how to fix this, it's done for SP1.

Good news guys - we took another look and figured out how to fix this, it's done for SP1.

Ping Ryan or other PMDG staff, As I experienced as well deviations of ILS track linked to runways of default airports I looked a bit closer to the data files. I felt before confident, that I would not experience any problems with FSX data as I wrote a little tool that extracts all data from the result of Pete Dowsen's MakeRunways and writes them into the PMDG file format (say into airports.dat and wpNavAPT.txt. This includes the FSX immanent magnetic deviation data and as well the exact ILS course data. However, there is a second place where the ident information is stored, and (I guess so) the location of the ILS (no magnetic data at all). My imagination now is, that the ILS location might not correspond with the related runway location as the real world based figures may deviate even some miles from those being implemented in FSX. Example Berlin Tegel, Rwy 26LwpNavAPT.txt: Berlin Tegel EDDT26L07947259 52.560120 13.310249 109.30 25900122wpnavaid.txt: ITGW ITGW ILS 52.556158 13.269706 109.30 T Regarding Airport Design Editor, the stock ITGW is located at LAT 52.556158975, LON 13.269705623 in runway direction which looks good in this example. In other cases (with deviations) it might be one cause of not fitting approaches even in my case as it seems to me that the FMC takes the ILS location from the wpnavaid.txt file and does not link it with the runway location.I'm now quite sure that I'll have to find a tool extracting the nav data as well from FSX directly. Personally I don't care for real world data if they don't match to the flight simulator. However, I'm just guessing and would like somebody who knows something to answer my question, pleeeeze.

Question: Is anyone seeing this at DEFAULT FSX airports? If so I need to know where. We can't control what addon companies are putting in their local magvar. That's the problem with FSDT KLAS - the local magvar in their AFCAD is 2 degrees off from the world magvar there - that's why the NGX calculates 257 instead of 255. If they set their local magvar to the same as the world one it'd work just fine.

Yes indeed. Today I observed at SANT RWY01 an indicated ILS course of 17° which is definitely wrong - and I have had a remarkable deviation from the runway heading. ADE tells me that the ILS HDG is 11° and the MAG VAR 3.0° which makes a course of 14°. I checked the runway data file and found in both, my own "home build from FSX installed data" and in the one delivered by PMDG, exactly the expected approach course of 14°. The enclosed picture may prove my point. I guess that the NGX may (!) just add the MAG VAR to already corrected course data (as the auto tuned course, as already written above was 17°). BTW: Where can I find the possiblity to switch off the auto tune feature? I think I missed it.

Yes indeed. Today I observed at SANT RWY01 an indicated ILS course of 17° which is definitely wrong - and I have had a remarkable deviation from the runway heading. ADE tells me that the ILS HDG is 11° and the MAG VAR 3.0° which makes a course of 14°. I checked the runway data file and found in both, my own "home build from FSX installed data" and in the one delivered by PMDG, exactly the expected approach course of 14°. The enclosed picture may prove my point. I guess that the NGX may (!) just add the MAG VAR to already corrected course data (as the auto tuned course, as already written above was 17°). BTW: Where can I find the possiblity to switch off the auto tune feature? I think I missed it.

Since Hotfix 4..........SET FSX LOC CRS & REALISTIC A/P ENGAGEMENT & A/T MANUAL OVERIDE have been moved from Aircraft-Equipment to Options-Simulation. Fred.

Since Hotfix 4..........SET FSX LOC CRS & REALISTIC A/P ENGAGEMENT & A/T MANUAL OVERIDE have been moved from Aircraft-Equipment to Options-Simulation. Fred.

Thanks a lot Fred!