In ver. 1.1.6, PD [aka along-track] waypoints worked as expected as per A350 syntax, wherein typing a number (7 [or +7], -7) would place a user-created waypoint the specified distance from the selected waypoint, either ahead or behind the waypoint (on track) depending on where a positive or negative value is entered.

In version 1.1.7, this function seems to have experienced a regression; wherein it no longer works at all. When creating a PD waypoint, a waypoint is created the specified distance from the selected waypoint, but is generated on the track from the preceding waypoint and is sequenced behind the specified waypoint. The attached video should clarify what I mean. When “7” is entered as the next waypoint from SIERA, a waypoint 7 nautical miles, on the track from SIERA, should be created. Instead, a waypoint 7 nautical miles is created from SIERA but on the track between the preceding waypoints, and is sequenced behind the selected waypoint where it is meant to go in front of.

Again, this all worked perfectly in ver. 1.1.6, perhaps a fix could be included in the next hotfix 🙏

 

 

 

 

 

 

Edited November 25, 2025Nov 25 by benlong
Grammar

Here is another example that is maybe a bit clearer:



VEDVO was selected, then INSERT NEXT WPT, then "5" was entered.
The expected behaviour is that a waypoint, along the track from VEDVO to SEGPO, 5NM from VEDVO, is created. This would be generated as something like "PD01". It worked perfectly in 1.1.6.
However, as seen in this example, a PD waypoint is inserted before VEDVO [in the TMPY F-PLN], and although it is 5NM from VEDVO, it is 5NM from VEDVO on the track between RAMEN and VEDVO (the preceding waypoint).

Hope this helps.

This problem continues to occur in version 1.1.8

Edited November 29, 2025Nov 29 by benlong