
-
Posts
5,258 -
Joined
-
Last visited
-
Donations
0.00 USD
Reputation
1,260 ExcellentContact Methods
-
Website URL
https://albar965.github.io
Profile Information
-
Gender
Male
-
Location
Germany
Flight Sim Profile
-
Commercial Member
No
-
Online Flight Organization Membership
none
-
Virtual Airlines
No
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
No ships on map
albar965 replied to husker_dingo's topic in Little Navmap | Little Navconnect | Little Logbook Support Forum
🙃 Alex -
No ships on map
albar965 replied to husker_dingo's topic in Little Navmap | Little Navconnect | Little Logbook Support Forum
Is this the stable MSFS or the beta? Alex -
There is no limit but too many features on the map can reduce performance. Fifteen rings should not cause any problems, even on slow computers. I'd try to exclude the LNM installation folder and settings folder ("C:\Users\YOURUSERNAME\AppData\Roaming\ABarthel" or "%appdata%\ABarthel") from anti-virus scanning. Alex
-
There is not performance degradation between these LNM versions. You probably collected a huge aircraft trail. Delete it in LNM menu "Map". You can also limit its size in options on page "Map Aircraft Trail" or deselect "Restore aircraft trail" on page "Startup and Updates". MSFS has the strange habit to send fantasy aircraft information while the the sim is still in the menus.🤦♂️ This contributes to the problem. 🤷♂️ Alex
-
Thanks for the information. I put the airspace description into a .txt files and loaded the airspace library. Loading above airspace ok using user airspaces. Class G is enabled. Deselecting "User" hides the airspace. Colors above (half-transparent red fill and blue boundary) according to changes in "C:\Users\YOURUSERNAME\AppData\Roaming\ABarthel\little_navmap_mapstyle.ini": [Airspace] ClassGFillColor=#20ff0000 ClassGPen=#0000ff, 1, Solid Restart is needed after changing colors. Better keep LNM closed while changing the .ini. Alex
-
MSFS 2024 loading is completely different to MSFS 2020. LNM reads BGL and other files from the MSFS 2020 scenery library to build the databases. No files are read from MSFS 2024. All is transferred using the more or less stable SimConnect interface while '24 is running. I'm testing right now and see crashes with the latest MSFS 2024 beta but only having the Navigraph navdata update installed. No idea yet what is going on there. 🤷♂️ Alex
-
You can change the color only by type. This affects all airspaces. To me it looks like you added an unknown or invalid airspace type. Types are listed here: https://www.littlenavmap.org/manuals/littlenavmap/release/latest/en/AIRSPACELOAD.html#openair It is hard to diagnose without knowing what airspace you added. Maybe a snippet from the OpenAir txt file with the faulty airspace can help. Either in scenery library menu to hide all custom airspace or by type. Alex