Navigation starts from wrong WP

RetiredWingMan

Something minor but a little strange. If I load a route, before hitting Start, I turn off Calculate from current location. When the route loads, it starts from WP 2 not WP 1 as expected.

As per below, WP 1 is skipped?!

Corjan Meijerink

@RetiredWingMan thanks for sharing! I’ll check this.
Is it consistent for you with all routes? / just this route? / all the time?

Con Hennekens

@RetiredWingMan, good find!
@Corjan-Meijerink, I have simulated this with multiple routes, and must conclude that it is structural. Whenever you disable "Calculate from current location" the route immediately goes to WP2.

RetiredWingMan

@Corjan-Meijerink yes, it is consistent.

Rob Verhoeff

@Corjan-Meijerink said in Navigation starts from wrong WP:

Is it consistent for you with all routes? / just this route? / all the time?

Same here...

M. Schrijver

@Con-Hennekens
Does it also send you back to point 2 when you're already at point 15 or so?

Con Hennekens

@M-Schrijver, I think I know what you are getting at: Doesn't that function simply bring you to the nearest WP?

I have tested this, and it seems to be a little less consistent now, but I think you are right. I have plotted a rout of 8 WPs where I am nearest to WP6. Starting the route with "Calculate from current location" disabled, fairly consistently sends me to WP2, however in 1 out of 10 tries it send me to WP3 (which is also quite illogical). However, after some seconds (or slight movement, I don't know) it skips to WP6 indeed.

So I guess it is fair to say that if you are already on the route and start it with "Calculate from current location" disabled, it should send you to the nearest WP ahead in the route. However that does not completely explain why people get send to WP2, even if WP1 is the nearest WP ahead in the route, which is what seems to happen according to the experiences higher in this thread. A bit of a guess on my side would be that this is due a mechanism to prevent being send back to a WP back in the route (it sends you to the nearest WP+1 to make sure you are not being send backwards).

M. Schrijver

@Con-Hennekens
That is what i mean.
Your explanation of "Calculate from current location" is a bit odd to me.
When it is "Enabled" i expect MRA will calculate form current position to the nearest waypoint (hand or drop) further on the route (not back).
When it is "Disabled" i expect MRA will calculate form current position to Waypoint 1.

Maybe my expectation is wrong.

GT JWR

@M-Schrijver I 100% agree with you - current location to the nearest WP in the route would be logical. Having it disabled, well, the assumption should be to start at WP1. Seems theres some logic issues within the app that need to be figured out.

Con Hennekens

@M-Schrijver, I see that differently but understand the confusion.

Until now I saw that switch mainly as a means to show the length and duration of the complete route from the current location (default / enabled) or from the planned route only, skipping the part from the current location to WP1. In the screen before you press start, that is. That's what the map on screen shows, and also is shown in the numbers for time and distance. I consider myself fairly knowledgeable about the app but was unaware of this switch leading towards the closest point in the route (maybe I should RTFM...).

In that light the feature would probably better be named "Start at closest WP on the route" (default disabled). And if enabled the route segment from current location to the closest WP should be presented, like it does for WP1 as well, including correct time and distance.

Corjan Meijerink

This will be fixed in the next update!

Con Hennekens

@Corjan-Meijerink, Great! (as always)
Can you disclose what this feature is going to look like?