Yes, the LNM diagram shows what is set in the nav data, which will be correct (at least if using Navigraph). Unfortunately that is over-ridden when actually flying the approach by a 4-byte value in the airport BGL file that forces the localizer to ignore the heading value in the nav data and assume the exact runway heading. This was a deliberate design choice by Asobo, which needs to be corrected.
It has never bothered me that much, because I normally fly the LDA on the Localizer Nav ,and that works… I think it is only when drawing the MAP, and making the Flight Plan path, that MSFS is messing up and forcing the runway heading towards the end of the flight.
Seems pretty clear now , and all ASOBO has to do is fix it, that is probably quite trivial, if they ca get motivated to do it.
(1) Read the LDA info from the database correctly, and use the LDA heading.
(2) Stop with the extrar ASOBO generated “USER” Waypoints.
(3) Stop with the strange, ASOBO curved flight plan tracks.
Maybe I’m misunderstanding something, but I’m still not sure how you fly the LDA in MSFS. Even flying raw data, without the GPS, the LOC is simply wrong.
If they suddenly call it ILS they just haven’t understood it. There are many things where I feel the developers simply lack aviation knowledge or exerienced and competent advice. Sounds harsh, not meant so, but they „fix“ things around in circles, they change it but then it‘s just different but not correct. LDA approaches are just displaced localizer approaches, unfortuntely many approaches look basically the same on the charts but pilots have to KNOW the differences. You‘d fly an LDA appr with similar modes you would use for an ILS, depending on the plane, but most of the time they lack a glide slope and they are always non precision approaches… If these things are being understood there is very little probability to make it SO wrong all the time. Aviation theory is a lot, but at least the basics must be accessable.
I’ve said it before, but they obviously aren’t providing the actual software engineers with the aviation specific technical support/knowledge they need to implement things correctly.
At least it calls it a Localizer, correctly like the OEM Garmin
Apparently, the SDK is lacking, in that you cannot directly get an Airport ICAO name from a nav Air at that airport. so the MOD does not current display KIAD
It looks like it is thinking its a ILS …though why ?
There is a Index of Approaches,