June 12, 20214 yr So is this problem with the ILS not lining up: 1: LNM? 2: My Custom Airports? 3: Navigraph AIRAC Data? 4: Something else? https://imgur.com/a/OWFg8IT I'm using MSFS most recent and the most recent AIRAC from Navigraph in LNM. Any help would be greatly appreciated. Thanks Edited June 12, 20214 yr by nasaspaceboy
June 12, 20214 yr 1) I know this airport very well because I very often performed landings at LSGS during online flights on IVAO network (Sion is the airport on the list of the dangerous airports that I like to fly). I use real world charts and there is no ILS25 (and any other ILS) approach at Sion airport. Only IGS25 and RNAV25 instrumental approaches exist there. IGS25 approach based on offset localizer is hard approach with 6 degrees descend that ends at MG25 fix point ~6NM of rwy 25 threshold and then it's necessary to perform visual part of approach (described on separate chart) that is approach with 4 degrees descent into the rwy 25. 2) I suppose this ILS25 approach is a "funny creativity" of Microsoft 😛 or maybe one of your add-ons. Under my XP11 and also under LNM (Navigraph) there is no other localizers displayed there except of ISI 110.70/244M offset localizer - similar like in the real world. Regards, Piotr ps. BTW - if you see under FS2020 only one localizer it doesn't matter they don't lining up in LNM display/map view, as I wrote previously the approach to LSGS isn't straight ILS nor straight LOC approach, so for security during IGS25 approach it doesn't matter 🙂 IMHO IGS25 approach is closer to old-style cloud breaking procedures, however of course it's a full instrumental ICAO procedure in opposite to old NDB/NDB2 cloud-breaking procedures (still in use in some of South African airports) Edited June 12, 20214 yr by ppgas Never give up ... - here are details of the whip-round: https://zrzutka.pl/en/pewr2d -> to help my younger son fights against Acute Lymphoblastic Leukemia (blood cancer).
June 12, 20214 yr Author Thanks for the input but I have many airports like this where the ILS doesn't line up, not just these three. Does anyone else have the same problem?
June 12, 20214 yr First question to find a solution for your problem is which scenery library settings you've got when dump the screenshot?: -use Navigraph for all features, -use Navigraph for Navaids and procedures, -do not use Navigraph database. Every of these options can show different things in LNM - for example, under my XP11 there is a small difference in heading of LSGS ISI localizer - for set Navigraph db it's displayed as it is 243M heading (but it's written 244M in description), for set X-Plane db it's displayed in LNM exactly as it's 244M heading (but as I wrote previously in this case it doesn't matter for this approach) - all is nice visible during switching between simulator database and Navigraph database and using measure distance tool. In general under simulator I use XP11 database as Navaids source because aircraft takes radiosignals from simulator's stations. Second question is - did you make reset your LNM settings, reloaded/upgraded Navigraph and reloaded/upgraded scenery library from simulator to refresh database before testing? Regards, Piotr Never give up ... - here are details of the whip-round: https://zrzutka.pl/en/pewr2d -> to help my younger son fights against Acute Lymphoblastic Leukemia (blood cancer).
June 14, 20214 yr I don't see the problems with LEMD. The ILS are perfectly aligned even if using plain MSFS data. The other examples are like real world and correct. Alex Alex' Projects: Little Navmap
Archived
This topic is now archived and is closed to further replies.