Little Navmap 3.0.17 released

Direct Download

► Windows 64-bit Installer (MSFS and X-Plane) - LittleNavmap-win64-3.0.17-Install.exe
► macOS - LittleNavmap-macOS-3.0.17.zip
► Linux (64 bit, based on Ubuntu 22.04) - LittleNavmap-linux-ubuntu-22.04-3.0.17.tar.xz
► Linux Debian Installation Package (64 bit, based on Ubuntu 22.04) - LittleNavmap-linux-ubuntu-22.04-3.0.17-1_amd64.deb

Other Versions:

► Windows 32-bit Installer (only for FSX and P3D) - LittleNavmap-win32-3.0.17-Install.exe
► Linux (64 bit, based on Ubuntu 20.04 for Debian or older systems) - LittleNavmap-linux-ubuntu-20.04-3.0.17.tar.xz
► Linux Debian Installation Package (64 bit, based on Ubuntu 20.04) - LittleNavmap-linux-ubuntu-20.04-3.0.17-1_amd64.deb

Zipped Windows releases without installer are available in the alternative download locations below or from the release assets at GitHub - Little Navmap Releases - Version 3.0.17 (scroll down to Assets).

► Alternative Download Locations. Look into sub-folders for beta, development or release candidates.

► Read here if you have problems downloading Little Navmap for Windows
► See here if you have problems running Little Navmap on macOS

Notes

This is a stable release of Little Navmap that fixes several small issues.

macOS users: Keep in mind that you have to clear the quarantine flag when updating Little Xpconnect. See Clearing the Quarantine Flag on macOS.

Thanks to everyone who reported issues!

Changes from 3.0.16 to 3.0.17

• Fixed an issue where all VORTACs were loaded as TACAN in MSFS 2020, resulting in incorrect bearings and type display.
• Now omitting the channel for VOR, VORDME, and DME for all MSFS simulators. The channel applies only to VORTAC and TACAN.
• Fixed the issue with double runways when using the Navigraph navdata update in MSFS 2020. Example: The add-on for FHSH (no stock airport available) kychungdotcom-airport-fhsh-sthelena showed duplicate runways.
• Cleaned up error handling for the scenery library loader to allow loading to continue after an error in XML or JSON files.
• Fixed the issue where a broken CSV import resulted in errors for further imports of userpoints or logbook entries.
• More filtering has been implemented to eliminate incorrect MSFS aircraft indications before starting a flight in the simulator. The incorrect aircraft resulted in an aircraft trail crossing all over the world, causing display issues and crashes.
• Saving flown distance is now maintained between restarts. This avoids a zero flown distance in logbook entries.
• Now properly disabling context menu items in the logbook and user data search to avoid crashes.
• Added flown distance alongside flight plan distance to the bottom summary line in the logbook.
• Added an option to scale aircraft icons separately for web pages on high-resolution displays. This can be changed in the options on the Web Server page.
• Disabled the compass rose and other features on the Dynamic Touch and Drag web map.
• The compass rose, endurance, altitude range, and turn path are disabled to avoid a cluttered display when using the Dynamic Touch and Drag web map.
• Added a red extra range ring for zero fuel range. While the black dotted range ring shows the range with reserves, the red range ring shows the range without fuel.
• Clearing the procedure preview now occurs when adding a procedure from the map context menu. This is now consistent with the behavior when adding a procedure from the search tab.
• Improved circle drawing for range rings to avoid edges.
• Changes in command line handling: Opening flight plans using -f from the command line now leaves plans in an unchanged state to avoid question dialogs and ease automation. Passing a filename without an option might still change a plan on loading to adjust cruise and leave it changed.
• Plans created from descriptions from the command line are not temporary and will be cleared on restart. Save the plan manually to avoid this.
• Fixed issues where a changed flight plan was erased when loading from the command line or by double-clicking on the plan file.
• Enabled a warning when loading a plan with the wrong cruise altitude from a logbook entry.
• Fixed the blurry map issue when jumping back to the user aircraft after user interaction.
• Fixed issue where the map center was shifted with airspaces enabled. This placed the compass rose out of center at the right corner of the map.
• Added two options to disable distance and bearing display on top of the map tooltip. Change these in the options on the Map Tooltips and Clicks page.
• Attempt to fix crashes with long aircraft trails.
• Updated user manual for changes in command line and endurance.
• Updated Windows redistributable packages to the latest version.

🐇🐇🪺🪺 Happy Easter! 🪺🪺🐇🐇

See the included CHANGELOG.txt or here online for a complete list across all versions.

All files are checked by VirusTotal.

Note: There are always a few false positives on the installer while the majority of 60 to 70 anti-virus see no issue. Download and unpack the Zip archive it if this scares you.

After downloading this latest version, I suddenly encountered error messages when attempting to save new flight plans in the usual LNMPLN format. "File not found" was the basic summary. In reviewing past posts here (from 2023) on this issue I saw some discussion that MS OneDrive was a likely cause and that moving all things LNM over to Google Drive did the trick. However, I have had LNM and its flight plans deep in my OneDrive subfolders all along and I've had no problem whatsoever creating and saving my LNMPLN files there -- until the update I installed today. So, what is the cause? 

Thanks for asking. After trying and retrying to save a flight plan to LNMPLN, I was going to post in this Forum for some advice. But then I got a popup from my Windows Security/Protection History background process, saying that it had blocked LNM from making changes within a Protected Folder. Accordingly, I went into Controlled Folder Access Settings/Allow an app through Controlled folder access/  and then answered YES to User Account Control, which brought me to the next screen with the box "+Add an allowed app" . Once I clicked on that, I was able to add Littlenavmap.exe to that Allowed list. Then, going back into the LNM app, I was able to save my flight plan in LNMPLN format normally, in the location I've used all along. Problem solved. I hope anyone else having the same glitch I've reported here can solve it in the same way. 

 

 

30 minutes ago, Jakeness53 said:

After downloading this latest version, I suddenly encountered error messages when attempting to save new flight plans in the usual LNMPLN format. "File not found" was the basic summary. In reviewing past posts here (from 2023) on this issue I saw some discussion that MS OneDrive was a likely cause and that moving all things LNM over to Google Drive did the trick. However, I have had LNM and its flight plans deep in my OneDrive subfolders all along and I've had no problem whatsoever creating and saving my LNMPLN files there -- until the update I installed today. So, what is the cause? 

Sorry, but I have no idea. Nothing changed for file saving in the latest version. OneDrive or any other cloud should not cause issues. I use a local self-hosted Nextcloud to keep plans and other files in sync between computers. No problems with that.

I remember cases where anti-virus kept files blocked.

34 minutes ago, Jakeness53 said:

Thanks for asking. After trying and retrying to save a flight plan to LNMPLN, I was going to post in this Forum for some advice. But then I got a popup from my Windows Security/Protection History background process, saying that it had blocked LNM from making changes within a Protected Folder. Accordingly, I went into Controlled Folder Access Settings/Allow an app through Controlled folder access/  and then answered YES to User Account Control, which brought me to the next screen with the box "+Add an allowed app" . Once I clicked on that, I was able to add Littlenavmap.exe to that Allowed list. Then, going back into the LNM app, I was able to save my flight plan in LNMPLN format normally, in the location I've used all along. Problem solved. I hope anyone else having the same glitch I've reported here can solve it in the same way.

So Windows security was it.
Did the dialog state the protected folder? The only folders that are changed are the cache "C:\Users\YOURUSERNAME\AppData\Local\.marble" and the settings folder "C:\Users\YOURUSERNAME\AppData\Roaming\ABarthel" .

Did you install from a Zip file? I'd recommend to use the installer to avoid wrong file permissions.

Alex

Hello Alex, it's a deception for me this release doesn't fix the problem about the size of the plane, texts and other things on the web server map. I told you about that. Is that something you'll fix soon ? For me it's nearly unreadable.

3 hours ago, Darth Patzer said:

Hello Alex, it's a deception for me this release doesn't fix the problem about the size of the plane, texts and other things on the web server map. I told you about that. Is that something you'll fix soon ? For me it's nearly unreadable.

I added a fix for the aircraft but I cannot fix texts:

Quote

* Added an option to scale aircraft icons separately for web pages on high-resolution displays.
  This can be changed in the options on the `Web Server` page.

Alex

Hi,

I noticed a severe degradation of performance with this version. Is it me of anybody else had the same feeling? Moreover, I see lines stretching distant waypoints (like airways or even the route path) disappearing when zooming in "too much" (well actually not so much too much!). The problem was there before, but seems to me much worse in this version...

 

1 hour ago, arrex said:

I noticed a severe degradation of performance with this version. Is it me of anybody else had the same feeling? Moreover, I see lines stretching distant waypoints (like airways or even the route path) disappearing when zooming in "too much" (well actually not so much too much!). The problem was there before, but seems to me much worse in this version...

 

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

That's not the reason for sure. I use LNM detached from any simulator (and i don't have MSFS at all).... what i noticed is that dragging long routes recently cause a lot of stuttering... once that was not the case... will dig on this more.

 

2 hours ago, arrex said:

That's not the reason for sure. I use LNM detached from any simulator (and i don't have MSFS at all).... what i noticed is that dragging long routes recently cause a lot of stuttering... once that was not the case... will dig on this more.

Then I need more information. What OS? What  simulator (scenery library)?

A screenshot of the whole program including status bar and window title might help. Maybe the flight plan showing the disappearing lines.

Alex

 

It's FSX database, but runnning unlinked to any simulator.

Funny enough: i rebooted the system and now LNM is way faster... and the line does not disappear anymore.... i am not sure what happened! I know that the program was running since several days. Maybe some memory leaks or similar can cause the slowdown and the visualization problem? I will keep the program running for some days to see if the problem reappears....

 

2 hours ago, arrex said:

Funny enough: i rebooted the system and now LNM is way faster... and the line does not disappear anymore.... i am not sure what happened! I know that the program was running since several days. Maybe some memory leaks or similar can cause the slowdown and the visualization problem? I will keep the program running for some days to see if the problem reappears....

Ok. Let me know if something blows up again. Normally there are no memory leaks but one never knows.

Is it possible that range rings cause problems? Because while using LNM for many flights i use them to mark the arrival parking gates.... and after few weeks I might have 10-15 rings around the map (but not in the area where i plan the route)....

 

1 hour ago, arrex said:

Is it possible that range rings cause problems? Because while using LNM for many flights i use them to mark the arrival parking gates.... and after few weeks I might have 10-15 rings around the map (but not in the area where i plan the route)...

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