Moving new waypoint up doesn't update distance.

[FSullivan 0]

I will try to explain the issue with the following two simple examples (validating on each step, to get TOD):

Example 1:

1) Assume that we import the following flight plan: LPPT GEBTI LPFR  (Distances displayed are: LPPT -> 93.4 NM -> TOD -> 34 NM -> GEBTI -> 13.5 NM -> LPFR) - Correct distances

2) Now if we add waypoint MONUR: (Distances displayed are: LPPT -> 127.4 NM -> GEBTI -> 117.2 NM -> MONUR -> 60.2 NM -> TOD -> 49 NM -> LPFR) - Correct distances but MONUR needs to be moved up

3) If now we move up MONUR to correct it's position, we get: (Distances displayed are: LPPT -> 117.2 NM -> MONUR -> 56.2 NM -> TOD -> 61 NM -> GEBTI -> 13.5 NM -> LPFR) - Not correct

To solve this situation we need to move up GEBTI above MONUR and then move down GEBTI again to it's correct position:

4) Moving up GEBTI above MONUR we get: (Distances displayed are: LPPT -> 117.2 NM -> GEBTI -> 117.2 NM -> MONUR -> 60.2 -> TOD -> 49 NM -> LPFR) - Incorrect distances and MONUR not in the correct position

5) Moving down GEBTI we get: (Distances displayed are: LPPT -> 10.2 NM -> MONUR -> 83.2 -> TOD -> 34 NM -> GEBTI -> 13.5 NM -> LPFR) - Correct distances and waypoint positions

If the flight plan is initially loaded with already the waypoint MONUR in the correct position, we get:

(Distances displayed are: LPPT -> 10.2 NM -> MONUR -> 83.2 -> TOD -> 34 NM -> GEBTI -> 13.5 NM -> LPFR) - Correct distances and waypoint positions 

Example 2:

1) Assume that we import the following flight plan:

YSCB MATLA BANDA OMKAX BERNI YBCG (Distances displayed are: YSCB -> 192.2 NM -> MATLA -> 128.8 NM -> BANDA -> 95 NM -> OMKAX -> 6.6 NM -> TOD -> 26 NM -> BERNI -> 40.5 NM -> YBCG) - Correct distances

2) 3) Now if we add waypoint AKMIR and move it up above MATLA for it's correct position, we get:

(Distances displayed are: YSCB -> 363.5 NM -> AKMIR -> 192.2 -> MATLA -> 128.8 NM -> BANDA -> 95 NM -> OMKAX -> 6.6 NM -> TOD -> 26 NM -> BERNI -> 40.5 NM -> YBCG) - Incorrect distances

4) 5) Moving up MATLA above AKMIR and down again to it's correct position, we get:

(Distances displayed are: YSCB -> 81.3 NM -> AKMIR -> 192.2 -> MATLA -> 128.8 NM -> BANDA -> 95 NM -> OMKAX -> 6.6 NM -> TOD -> 26 NM -> BERNI -> 40.5 NM -> YBCG) - Incorrect distance between AKMIR and MATLA

The distance between AKMIR and MATLA (192.2 NM) was taken from the initial distance between YSCB and MATLA, but should be 111.3 NM as we can see below.

If the flight plan is initially loaded with already the waypoint AKMIR in the correct position, we get:

(Distances displayed are: YSCB -> 81.3 NM -> AKMIR -> 111.3 -> MATLA -> 128.8 NM -> BANDA -> 95 NM -> OMKAX -> 6.6 NM -> TOD -> 26 NM -> BERNI -> 40.5 NM -> YBCG) - Correct distances and waypoint positions

 

I think I have been clear and useful to show this situation and hope that this is not an issue just on my side.

Thanks and Best regards,

FSullivan 

Now I am not sure if this was posted on the correct forum (Pilot2ATC). If not, please be so kind to direct it to the correct place.

Thanks,

FSullivan

Edited May 14 by FSullivan

[Dave-Pilot2ATC 875]

There does appear to be a bug.  After pressing the validate button, the distances and TOD should be recalculated, but the distances  in the first example remains unchanged.

This should be fixed in the next release.

Dave

[FSullivan 0]

Thank you for your prompt answer and support.

Best regards,

FSullivan