VFRnav 4.26 introduces new configuration options and improvements for flight planning, while also refining terrain awareness and fixing several reported issues.
What’s New
New: The settings for serial GPS and traffic sources now allow manual configuration of the baud rate.
This provides improved compatibility and flexibility when connecting external hardware and data sources.
New: If individual NOTAMs are permanently hidden in route planning, they will now also be hidden directly on the map.
Further Improvements
Improved: The range for terrain highlighting has been extended to 50 km, making it easier to follow terrain structures and valley routes during flight.
This change may have a direct impact on performance, and we’d appreciate feedback from users across different devices.
We plan to continue refining this feature in future updates.
Fixes
Fix: The QNH setting when using an external barometer is now correctly restored after restarting VFRnav
Fix: The settings dialog for inserting georeferenced approach charts was partially hidden on some devices
As always, if you encounter any issues or have suggestions for improvement, we’d love to hear from you — either by email or right here in the forum.
Thank you for this feature! I took a short flight into the Alps today and tested the feature on three different devices.
On both my smartphone (S25FE) and on two tablets, an older one (Huawei Mediapad M5) and a newer one (Samsung S9FE), there were no problems with the 50 km visibility range and you get an overview of the valleys ahead. Performance was not a problem on any device.
If necessary, you could make the 50 km configurable instead of fixed, in case performance could otherwise be an issue; like 10–150 km?
It would be good if the coloring could also be displayed in front of base overlay maps, or if the base overlay map could be temporarily switched off.
I was in the Alps myself the week before last and found that the previous visibility range of the shaded terrain unfortunately didn’t really add any practical value You had already mentioned the issue earlier. So now the change.
Great! Thanks for testing! That’s what I wanted to hear
I’ll keep an eye on it. As mentioned - there are still some optimizations planned. With those we can then further increase the range. Preferably without any additional setting for the user. We’ll see!
What’s New
You had already mentioned the issue earlier. So now the change.
