matifoopong

Thank you so much for this change. It works perfectly in my environment. Also I noticed that I don't have to do anything with this version in order to see airport names in English. I really appreciate it. Matifoopong

I use Windows 10. Please refer to: https://www.gaeb-online.de/hilfe2014/nounicode_en.html

I cannot attach PLN files onto this post, so let me send you an email, Alex. I created A.pln with LNM and loaded it from MSFS. The result is not good: I changed ° to * and saved the file as B.pln. The result is good: Also for your reference, I created a flight plan from within MSFS and saved it as C.pln, which contains * instead of °. By the way, based on the fact that your MSFS uses ° unlike mine, I began to suspect it only happens in Asian languages environment. While experimenting with various Windows language settings, I found that the problem disappears if I check the box. I am not sure if I can call it a good solution, because I have no idea exactly what it does.

MSFS uses * ’ " as coordinates format when generating a flight plan file (*.PLN), whereas all others including LNM use ° ’ ". A flight plan that has ° ’ " can be loaded by MSFS, but one or more waypoints will be translated into wrong coordinates (thousands of miles away from the correct waypoint) more often than not. While we are waiting for MSFS developers to fix the bug, we can avoid it by replacing ° with * using a text editor. For example, you have to change 11° 22’ 33" to 11* 22’ 33" before loading it into MSFS. This problem has been known for years, but surprisingly I cannot see many people complaining about it. So I wonder -- Is there anyone who uses LNM and MSFS without experiencing it? Is there a more convenient way than using Notepad?

I tried again, and I confirm it can be reliably reproduced in my environment. I do not think this is a serious issue, but I am willing to help you with tests and observations in case you are interested in finding the root cause. Best regards Matifoopong

Now I see airport names displayed in English. I changed Windows language from Korean to English before reloading the scenery database. "User interface language" setting in LNM was always set to US English. It has never been changed, because I could not find Korean from the languages menu. Thank you very much, Alex and Dave, for helping me enjoy this great great utility.

Airport names are shown in Korean in Little Navmap. (red circles in the image below) If I choose "Use Navigraph for all features", airport names are shown in English, which I prefer. If I choose "Use Navigraph for Navaids and Procedures" or "Do not use Navigraph database", then airport names are shown in Korean. This behavior is observed with v2.8.12 as well as v3.0.2.beta. My humble theory is that even though English was chosen as the user interface language in my MSFS 2020 when LNM was loading scenery library from it, LNM extracted Korean strings for airport names, because it is the default language of my Windows 10 installation. Is there a way to have them displayed in English please?