For anyone that is interested to mark in LNM his addon airports from MSFS Addons Linker, here is the util i created for that.

https://flightsim.to/file/88630/altolnm-mark-little-navmap-airports-as-addons-from-the-database-of-msfs-addons-linker

 

Edited February 13, 20251 yr by earthdog

6 hours ago, earthdog said:

For anyone that is interested to mark in LNM his addon airports from MSFS Addons Linker, here is the util i created for that.

I put a link to your add-on right here https://albar965.github.io/links.html
Hope it's ok that I copied your description.

Alex

50 minutes ago, albar965 said:

I put a link to your add-on right here https://albar965.github.io/links.html
Hope it's ok that I copied your description.

Alex

Of course it is ok!

On 11/26/2024 at 11:08 AM, albar965 said:

I can load a plan file into the MSFS EFB. Good enough for me

I'm sure you're aware of these bugs in MSFS2024 by now, but FYI after you load a PLN via the EFB, it's still not possible to load a PLN (at least containing user waypoints) from code inside the sim. Working Title have acknowledged two bugs, no commitment or a date yet to fix them:

(1) For User Waypoints the EFB code overwrites the waypoint 'ICAO' code with a new 5-character random value derived from the latitude of the waypoint. Something like "49N03". This creates duplicate replacement ICAO codes for waypoints within some distance of each other (100km?)

(2) The MSFS code that actually passes the flightplan data to the html/js gauges (GET_FLIGHTPLAN) deletes waypoints it thinks are 'duplicates' in the list of waypoints, using the ICAO code as the discriminator.

(1) + (2) means that User waypoints in the PLN are routinely randomly dropped from the flight plan in the internal GET_FLIGHTPLAN API.

That isn't a bug you can fix in LNM but worth being aware of. 

Something more work-aroundable is: a minor other bug I've recently come across but likely you've already programmed for, is 94 of the MSFS airports have an '&' in the name (e.g. EGME). If the *name* of that waypoint appears unchanged in the PLN (i.e. still including the '&') it crashes bits of MSFS2024. You can escape the ampersand with "&" so the XML is ok but then *that* appears in the name in some gauges. Easiest IMHO is to replace the "&" with "and".

2 hours ago, B21 said:

I'm sure you're aware of these bugs in MSFS2024 by now,

Ok. Thanks a lot for letting me know. Last time I tested user waypoints showed up ok. But it looks like there is nothing I can do anyway. I'll have a look again before releasing LNM 3.0.16.

2 hours ago, B21 said:

Something more work-aroundable is: a minor other bug I've recently come across but likely you've already programmed for, is 94 of the MSFS airports have an '&' in the name (e.g. EGME). If the *name* of that waypoint appears unchanged in the PLN (i.e. still including the '&') it crashes bits of MSFS2024. You can escape the ampersand with "&" so the XML is ok but then *that* appears in the name in some gauges. Easiest IMHO is to replace the "&" with "and".

The file name? I'm asking because names are not saved inside the files for MSFS 2024. Only for '20.

I can replace it in the file name and the '20 export just to be sure. I already have code to replace other special characters.

Alex

On 2/13/2025 at 1:03 PM, earthdog said:

Of course it is ok!

Hi Alex, I have an airport that I manually marked as addon that I want to unmark, how do I do that? Thanks.

2 hours ago, Alvega said:

Hi Alex, I have an airport that I manually marked as addon that I want to unmark, how do I do that? Thanks.

The yellow ring is added as a userpoint. Right click on it in the map and select "Userpoints" -> "Delete userpoint" from the context menu.
You can also look into the userpoint tab in the search window to modify or delete.

Alex

22 minutes ago, albar965 said:

The yellow ring is added as a userpoint. Right click on it in the map and select "Userpoints" -> "Delete userpoint" from the context menu.
You can also look into the userpoint tab in the search window to modify or delete.

Alex

Thanks. 👍

Hi guys, I'm having a problem with LIMC Aerosoft airport, the "arrival procedures" screen won't open.

 

https://ibb.co/60dtpCgy

3 hours ago, six1975 said:

Hi guys, I'm having a problem with LIMC Aerosoft airport, the "arrival procedures" screen won't open

No problems here with the stock airport. Seems that the Aerosoft airport either has no procedures or is broken somehow.

LNM does not decode the procedures from MSFS 2024 BGL files. I reads all through SimConnect. Therefore, I doubt this is an LNM issue. 
Does the airport show STAR procedures in the sim?

Alex

 

On 1/6/2026 at 4:13 PM, albar965 said:

No problems here with the stock airport. Seems that the Aerosoft airport either has no procedures or is broken somehow.

LNM does not decode the procedures from MSFS 2024 BGL files. I reads all through SimConnect. Therefore, I doubt this is an LNM issue. 
Does the airport show STAR procedures in the sim?

Alex

 

Hi, I think it's a LIMC 1.0.5 Aerosoft problem,

because now I'm about to take off and it doesn't even show the sid...

but at the same airport in MSFS2020 everything was ok, I had never had this problem

Edited January 17Jan 17 by six1975

8 hours ago, six1975 said:

Hi, I think it's a LIMC 1.0.5 Aerosoft problem,

because now I'm about to take off and it doesn't even show the sid...

but at the same airport in MSFS2020 everything was ok, I had never had this problem

Looks like it is not really compatible with MSFS 2024. Maybe.🤷‍♂️

Alex

13 hours ago, albar965 said:

Looks like it is not really compatible with MSFS 2024. Maybe.🤷‍♂️

Alex

Absurd to think that version 1.0.5 is native MSFS2024

I tried with the 2020 version and everything works normally...absurd