Hello,

during the last two LNM versions i've been using, i think at first i noticed it in 2.80 and now i'm using 3.03rc1- i'm not able to properly search for certain airports. Well, i can search, but there aren't results.
LKPR, LDSP, LDDU, and many other airports aren't listed at all. I can still click on them directly on the map, but there are many airports missing from the search.
I did validate/load the scenery after the updates.
How it works:
I click on search, enter airport ICAO - don't get any result. And if i add just LK and try to search that way, SOME Czech airports appear in the results, but not the major ones. Same goes for Croatia.
I'm not using any filters, although i was using them earlier to look for a specific type of airstrips, but now all the filter radio buttons are unselected. 
I've been using LNM since 2019, at first with X-Plane 11, and later, since 2021 with MSFS, and i haven't seen this particular issue earlier. 
Any tips?

I can fid LKPR, LDSP and LDDU in MSFS data by entering LKPR LDSP LDDU in the search box. Same for X-Plane 11.

Look if "Select automatically" is checked in the menu "Scenery Library" -> "Navigraph" although the Navigraph data also contains all three airports..

Then reset search options by right clicking in the search result table and select "Reset Search" or click the button .

BTW: The search has changed with 3.0.X. From the changelog:

Quote

Search

• Added combined search field for all airport idents and names (ICAO, FAA, city, name and others) using partial match for quick search. Separate search fields are still available. The same rules as mentioned in the point below apply.
• Completely reworked search functions for all search tabs. Now looking for partial text matches per default in all input fields instead of requiring stars as wildcards. This means that a search term of Chicago will find Gary Chicago as well as KORD. EDDE will find Erfurt-Weimar (EDDE) as well as Wedderburn. Stars * act as wildcards and double quotes " force an exact search. You can also enter a space separated list of names or idents and Little Navmap will show the results for each name.
• Search option fields selected from context menu using include/exclude are now opened automatically to avoid confusion. This applies to the Show in search function in the map context menu.
• Modified search fields hidden from the dropdown button menu (three-lines-button) are now ignored when searching.
• Now using better indications in the dropdown menu items. (changed) shows that an option is used and visible to the user. (changed, not used) indicates a changed option is ignored since the related fields are hidden from the dropdown menu button.

Alex

Thank you for the reply. The search started working again after i clicked on "Clear all search filters". But i have no clue what filters were active, and especially WHERE, because not one of the filter buttons were toggled on. Never mind. The most important thing is, that it works now.

Thank you again, for always being helpful, and for the amazing app. 

You can click the dropdown menu in LNM 3.0.X and this will indicate if there are changes in the related section.
Facilities are all the airport properties like add-on, tower and so on in this example.

LNM 3.0.X ignores sections in the search which are not visible (unchecked in the drop down menu). I changed this to avoid hidden search sections affecting the result which was not really intuitive.

(1) has changes in a visible section ("Lighted") and (2) has changes in a hidden section ("Runway") which are ignored:

Alex