[Release] VFRnav 4.29

Updates & Releases
1

:small_airplane: VFRnav 4.29

Dear fellow pilots,

After the summer break, we’re back with VFRnav 4.29! This update focuses on further performance improvements and bug fixes, while also laying the groundwork for more exciting map improvements in the near future.

Over the past few months, we’ve received an incredible amount of feedback from you. We’re very grateful for your continued support and proud of the active community that has grown around VFRnav. Thank you for sharing your experiences, ideas, and suggestions with us!

:sparkles: Important Changes & Fixes

  • Improved: Data synchronization has been further optimized, significantly reducing the time required to synchronize data between multiple devices.
  • Improved: Long NOTAMs in the PIB (Pre-Flight Information Bulletin) are now shortened to keep the briefing clear and easy to read.
  • Fix: An issue in the DFS AIP Browser that prevented some approach charts from being added has been resolved.
  • Improved: Terrain highlighting has been further optimized and now performs smoothly even on older devices.

:hammer_and_wrench: Further Fixes & Improvements

  • Fix: Unit changes were not handled correctly when the selected aircraft had not been saved as a profile
  • Improved: Performance of the waypoint search
  • Fix: Incorrect selection of user waypoints in the flight logbook
  • Improved: Performance of the vertical airspace profile
  • Fix: Incorrect display of frequency and squawk information in the vertical airspace profile
  • Improved: More robust NMEA parsing
  • Fix: Parsing issues with data received via serial interfaces on Android
  • Improved: More robust handling of serial data on certain devices, such as the Oudie N
  • Fix: Map downloads could result in duplicate entries in some cases
  • Fix: Waypoint searches containing special characters could fail to return matching results

As always, your feedback and suggestions from real-world flying are very welcome. If you have ideas for improvements, encounter an issue, or simply want to share your experience with VFRnav, send us an email or join the discussion here in the forum.

Blue skies and safe flying! :airplane:
– Your VFRnav Team

2

Thank you very much for the great work!!

3

Hello, I think I’ve noticed a bug. For the TMZ of EDDG, in the app’s horizontal airspace view the frequency and the SQK (131.015 & SQK 4472) are not displayed correctly. According to the chart it should be 129.300 & SQK 6104.

Regards Jan

4

Thanks from me too for the great update :heart:

Hi Jan, the transponder code 6104 is showing for me — that’s correct, right?

image
image317×571 59.8 KB

5

Screenshot_20260818_134852_VFRnav~3
Screenshot_20260818_134852_VFRnav~31080×2340 461 KB

:thinking: …does that work?

Do you have up-to-date map data? Please take a screenshot.

Clear skies,
Karsten

6

Going great :+1:

:grinning_face:

7

Hello, the cards are up to date according to the app.

Regards, Jan

Screenshot_2026-08-18-23-01-02-53_2fa739525b89008288d0132a25b38438
Screenshot_2026-08-18-23-01-02-53_2fa739525b89008288d0132a25b384381080×2400 470 KB

8

Hello Jan,

when I compare them like this, I think your position in the airspace profile is different from the map above? …because the terrain profile also looks different from my test. I also don’t see the airfields Beelen and Oelde (which could be due to the zoom).

Please write which route you planned (you can only see the approximate north/south course line).

Tapping in the airspace profile at different positions also updates the position on the map above.

Clear skies,
Karsten

9

Hello Karsten, the route would be direct from EDKR to EDWG.

Regards, Jan

10

Screenshot_20260819_102424_VFRnav~2
Screenshot_20260819_102424_VFRnav~21080×2234 457 KB

yep… that’s it! Horizontal route is fine, vertical is off :thinking:
→ @H655

Blue skies,
Karsten

11

Thanks to both of you :+1:
I can confirm and reproduce this - a very “interesting” bug :roll_eyes:

@Jan1 - many thanks for your bug report :100:

12

The incorrect display of the squawk or the frequency occurs only for TMZ and only when two different TMZs appear consecutively in a planned route. In this case, the vertical cross-section pulls the data from the rear TMZ.

I was a bit puzzled, since 4472 looked so familiar up here to me :grinning_face_with_smiling_eyes:

Thanks again to everyone involved - the bug will be fixed in the next update.

13

Version 4.29.3 fixes this bug :+1: