Hello Alex!

It seems I've found  the kind of "bug" that is caused by Laminar's inconsistency between IDENT field and ICAO code field.
Because of the unknown reasons LR doesn't change IDENT  field when ICAO code is changed (IDENT is the primary key in LR's airports database and their scenery gateway), so for some airports these fields've got quite different ICAO designators (IDENT field's got old ICAO designator, ICAO code field's got new ICAO designator). 

IMHO it implies in flight plans should be always used ICAO code field not IDENT, but in Little Navmap for exports is used IDENT field. 
It was checked under exports to IVAO fpl, XP11/XP12 fpl and old style XP11 FMS3 format, in all LNM versions between newest 2.6.x and newest 2.8.x (2.8.8 at this moment).
In all windows, filenames, etc. there are correct ICAO code field used and displayed, only inside files in flight plans appear old ICAO designators from IDENT field.
Example airport - HSSS (IDENT, old ICAO des.) / HSSK (ICAO code, new ICAO des.).
There are more airports with changed ICAO codes to newer - last time I've found some such airfields in Indonesia.

Regards,
Piotr

ps. sorry I haven't written for a while, but due my younger son's serious illness, I was living in a children's hospital last 1.5 year.
Fortunately he is in remission now, so he can continue his chemo- treatment at home and I could return to virtual flying at the beginning of this year and using/testing LNM of course 😄

ps2. sorry if this bug was reported previously, as I've metioned above I 've got a long time gap ...

Hi Piotr,

the more important question is if XP can load the FMS files. LNM chooses a reasonable display ident (map display, flight plan, etc.) from the available ones but this might not show in the exported files since I use other rules to select an ident for export. I needed a lot of experiments to find out what XP wants there (it is quite a mess). XP can load its internal ident (one of the "XP..." or other) or one of the FAA, IATA or ICAO idents in flight plans.

So LNM decides to use the HSSK as a display ident since ICAO is official but HSSS is used in the export since XP can load this for sure. Just tried this here. Does work. Using procedures changes the rule again. It might be a bit confusing since LNM proposes a file name with a different ident than the one shown in the plan. Maybe I can change this.

The rare known cases where XP could not load a flight plan I could not even build the plans manually in the GPS.

Always using ICAO is not an option since it is missing in some cases where only local, IATA or FAA are available.

Sorry to hear about your son. I wish him a speedy recovery.

Alex

As I've checked, when Navigraph database is loaded then both designators HSSK and HSSS are accepted under XP11, and it's possible to fly in both cases.
However when HSSS is chosen then no procedures are displayed under FMS, it's impossible to display airport schema under AirportNavigator (another add-on to XP11), etc.
So the problem concerns mainly on the lack of procedures in FMS during IFR flights.
My walkaround I've used since I noticed this problem is very simple - I manually replace in exported files the old designators to the new designators and it all works fine 🙂

I  haven't checked yet how it works with "no Navigraph" option in XP11. 

Regards,
Piotr

ps. I was out just "a moment"  and when I've return I get 2.8.8 - great tool that's got so new interesting things I have to learn LNM again. Keep going this good work Alex! 🙂

Edited February 24, 20233 yr by ppgas

The Navigraph database is almost the same as the X-Plane database regarding procedures. Scenery settings do not make much difference.

Just checked the cycle 2301 and there is a CIFP file for HSSS and HSSK and they are for different airports. LNM still finds the correct procedures doing some magic for the airport by searching for ident, ICAO, nearest and whatnot. LNM tries all kind of fuzzy searching by different idents to find the related procedures in such a mess. I cannot blame X-Plane for it. It's real world as it is.

So XP 11 (12 does not run on my development notebook) can neither load HSSS

I
1100 Version
CYCLE 2301
ADEP HSSS
DEPRWY RW36
SID RADK1B
ADES HSOB
NUMENR 3
1 HSSS ADEP 1265.000000 15.590356 32.553154
11 IMSUT DRCT 17000.000000 14.346666 31.375000
1 HSOB ADES 1924.000000 13.152900 30.232700

nor HSSK

I
1100 Version
CYCLE 2301
ADEP HSSK
DEPRWY RW36
SID RADK1B
ADES HSOB
NUMENR 3
1 HSSK ADEP 1265.000000 15.590356 32.553154
11 IMSUT DRCT 17000.000000 14.346666 31.375000
1 HSOB ADES 1924.000000 13.152900 30.232700

with procedures. But no problems without procedures. I think we just have to live with these corner cases.

BTW: Best way to learn about new stuff in LNM: Screenshots: https://albar965.github.io/pages/28/littlenavmapscreens.html

Alex

 

I've found another interesting thing when I've performed my last flight to China 🙂
When IATA code is set and ICAO code is empty, then inside LNM is used IATA code (flighplan, filenames, etc) not IDENT,
but on the other hand export works perfectly - here IDENT is used (not IATA)

Example - ZGHA  (ident), empty (ICAO) , CSX (IATA)

Regards,
Piotr

 

Edited March 2, 20233 yr by ppgas

LNM *shows* the most relevant code to avoid the X-Plane internal codes on display. You still can see all codes in the information window.

Order or relevance is: ICAO if present, otherwise FAA if present, otherwise IATA, otherwise local code. If all these are missing LNM shows the internal X-Plane code.

Export is another story.

Alex

 OK, Tnx for you explanation. Now all is clear 🙂

Regards,
Piotr