Waypoints not being marked as 'reached', causing navigation
Quote from Old Man Emu on 28.10.2024, 03:41
- Waypoints not being marked as 'reached', causing navigation instructions to freeze
Today I rode a route using 4.03 and my mate rode the same route with 4.04.
We both experienced Waypoints not being marked as reached when I know that we passed with 5 meters of the Waypoint. I think 4.04 had more misses.
For me not so bad as I knew how to skip and I knew more of the route, but my mate went ahead and got lost for 15 minutes doing a loop.
Are there any other reports of this still happening? I did see another post about this but cannot find it at the moment.
Wondering if turning Don’t Recalculate ON will help? As we pass a Waypoint that’s is not “reached” but we are still
on the line will it pick up the trail?
- Waypoints not being marked as 'reached', causing navigation instructions to freeze
Today I rode a route using 4.03 and my mate rode the same route with 4.04.
We both experienced Waypoints not being marked as reached when I know that we passed with 5 meters of the Waypoint. I think 4.04 had more misses.
For me not so bad as I knew how to skip and I knew more of the route, but my mate went ahead and got lost for 15 minutes doing a loop.
Are there any other reports of this still happening? I did see another post about this but cannot find it at the moment.
Wondering if turning Don’t Recalculate ON will help? As we pass a Waypoint that’s is not “reached” but we are still
on the line will it pick up the trail?
Quote from johansw on 28.10.2024, 05:11I don’t recalculate automatically as I then have a problem registering what is happening and when. I’d rather get the beep that I am making a mistake, and then press the recalc button when I know what is going on and what is likely to happen. That gives me far better control, I think. But then I have the Motive Monkey remotes controller, which makes it that much easier to control the various functions.
I don’t recalculate automatically as I then have a problem registering what is happening and when. I’d rather get the beep that I am making a mistake, and then press the recalc button when I know what is going on and what is likely to happen. That gives me far better control, I think. But then I have the Motive Monkey remotes controller, which makes it that much easier to control the various functions.
Quote from Guido on 28.10.2024, 06:07Quote from Old Man Emu on 28.10.2024, 03:41
- Waypoints not being marked as 'reached', causing navigation instructions to freeze
Today I rode a route using 4.03 and my mate rode the same route with 4.04.
We both experienced Waypoints not being marked as reached when I know that we passed with 5 meters of the Waypoint. I think 4.04 had more misses.
For me not so bad as I knew how to skip and I knew more of the route, but my mate went ahead and got lost for 15 minutes doing a loop.
Are there any other reports of this still happening? I did see another post about this but cannot find it at the moment.
Wondering if turning Don’t Recalculate ON will help? As we pass a Waypoint that’s is not “reached” but we are still
on the line will it pick up the trail?
Yes. I believe this will help. But it shouldn’t need to be necessary obviously. Do you still have the route you were following and the recorded ride? If yes, would you mind sharing those with me so I can try and reproduce and find out why even 4.04 was still missing waypoints?
Quote from Old Man Emu on 28.10.2024, 03:41
- Waypoints not being marked as 'reached', causing navigation instructions to freeze
Today I rode a route using 4.03 and my mate rode the same route with 4.04.
We both experienced Waypoints not being marked as reached when I know that we passed with 5 meters of the Waypoint. I think 4.04 had more misses.
For me not so bad as I knew how to skip and I knew more of the route, but my mate went ahead and got lost for 15 minutes doing a loop.
Are there any other reports of this still happening? I did see another post about this but cannot find it at the moment.
Wondering if turning Don’t Recalculate ON will help? As we pass a Waypoint that’s is not “reached” but we are still
on the line will it pick up the trail?
Yes. I believe this will help. But it shouldn’t need to be necessary obviously. Do you still have the route you were following and the recorded ride? If yes, would you mind sharing those with me so I can try and reproduce and find out why even 4.04 was still missing waypoints?
Quote from Old Man Emu on 31.10.2024, 21:17The route is here using 4.04
https://scenicapp.space/route/kwSUgRzf
The recorded ride is here Waypoint 3 didn’t register
https://scenicapp.space/ride/KVmmOQKX
The last 3 days we rode with “Don’t Recalc on” and it was much better. The Guide function worked well.
The route is here using 4.04
https://scenicapp.space/route/kwSUgRzf
The recorded ride is here Waypoint 3 didn’t register
https://scenicapp.space/ride/KVmmOQKX
The last 3 days we rode with “Don’t Recalc on” and it was much better. The Guide function worked well.
Quote from Guido on 01.11.2024, 09:41I took a look...
Waypoint 3 not being marked as reached, is expected in this case, because you never actually reach it. I'm assuming you decided to go to waypoint 4 directly and not go to waypoint 3.
With detour behaviour set to the first option, Scenic will keep guiding you to waypoint 3, relentlessley, until you reach it, or until you skip it.
Even if you reach waypoint 4 (like in below screenshot), Scenic will still try to guide you to waypoint 3, and not mark waypoint 4 as reached either. This is the expected behaviour with detour behaviour set to the first option. You need to reach (or skip) all waypoints in sequence.
Scenic 3 had a "auto-skip-waypoint" feature where a waypoint would be automatically skipped after X recalculations (where you could set that number X). I'm planning to add that back, but for now, if you want to skip a waypoint, you need to manually skip it. Or, like you did on your last ride, set detour behaviour to 'do not recalculate'.
Hope this makes sense?
I took a look...
Waypoint 3 not being marked as reached, is expected in this case, because you never actually reach it. I'm assuming you decided to go to waypoint 4 directly and not go to waypoint 3.

With detour behaviour set to the first option, Scenic will keep guiding you to waypoint 3, relentlessley, until you reach it, or until you skip it.
Even if you reach waypoint 4 (like in below screenshot), Scenic will still try to guide you to waypoint 3, and not mark waypoint 4 as reached either. This is the expected behaviour with detour behaviour set to the first option. You need to reach (or skip) all waypoints in sequence.

Scenic 3 had a "auto-skip-waypoint" feature where a waypoint would be automatically skipped after X recalculations (where you could set that number X). I'm planning to add that back, but for now, if you want to skip a waypoint, you need to manually skip it. Or, like you did on your last ride, set detour behaviour to 'do not recalculate'.
Hope this makes sense?
Quote from ulimach on 01.11.2024, 11:08Ich persönlich würde es sehr gut finden, wenn die Einstellmöglichkeiten mit dem Wegpunkt überspringen wieder so wie bei der Version 3 verfügbar wären.
Das hat super funktioniert!
Ich persönlich würde es sehr gut finden, wenn die Einstellmöglichkeiten mit dem Wegpunkt überspringen wieder so wie bei der Version 3 verfügbar wären.
Das hat super funktioniert!
Quote from Old Man Emu on 01.11.2024, 15:32Quote from Guido on 01.11.2024, 09:41I took a look...
Waypoint 3 not being marked as reached, is expected in this case, because you never actually reach it. I'm assuming you decided to go to waypoint 4 directly and not go to waypoint 3.
With detour behaviour set to the first option, Scenic will keep guiding you to waypoint 3, relentlessley, until you reach it, or until you skip it.
Even if you reach waypoint 4 (like in below screenshot), Scenic will still try to guide you to waypoint 3, and not mark waypoint 4 as reached either. This is the expected behaviour with detour behaviour set to the first option. You need to reach (or skip) all waypoints in sequence.
Scenic 3 had a "auto-skip-waypoint" feature where a waypoint would be automatically skipped after X recalculations (where you could set that number X). I'm planning to add that back, but for now, if you want to skip a waypoint, you need to manually skip it. Or, like you did on your last ride, set detour behaviour to 'do not recalculate'.
Hope this makes sense?
Yes of course. I lost my mate and then I didn’t look close enough at the actual route he took. He did miss 3 buy a long shot!
Auto skip after X recalcs would be a great feature because sometimes my ride buddies don’t know the names of little towns - with just a pub and a service station or scenic detour - coming up.
out friends at Kurviger have just implemented a feature to not skip the next waypoint/s but navigate to a chosen one down the list.
they also now warn if you place a waypoint too close to a junction or would create a U-turn
good work Guido
Quote from Guido on 01.11.2024, 09:41I took a look...
Waypoint 3 not being marked as reached, is expected in this case, because you never actually reach it. I'm assuming you decided to go to waypoint 4 directly and not go to waypoint 3.
With detour behaviour set to the first option, Scenic will keep guiding you to waypoint 3, relentlessley, until you reach it, or until you skip it.
Even if you reach waypoint 4 (like in below screenshot), Scenic will still try to guide you to waypoint 3, and not mark waypoint 4 as reached either. This is the expected behaviour with detour behaviour set to the first option. You need to reach (or skip) all waypoints in sequence.
Scenic 3 had a "auto-skip-waypoint" feature where a waypoint would be automatically skipped after X recalculations (where you could set that number X). I'm planning to add that back, but for now, if you want to skip a waypoint, you need to manually skip it. Or, like you did on your last ride, set detour behaviour to 'do not recalculate'.
Hope this makes sense?
Yes of course. I lost my mate and then I didn’t look close enough at the actual route he took. He did miss 3 buy a long shot!
Auto skip after X recalcs would be a great feature because sometimes my ride buddies don’t know the names of little towns - with just a pub and a service station or scenic detour - coming up.
out friends at Kurviger have just implemented a feature to not skip the next waypoint/s but navigate to a chosen one down the list.
they also now warn if you place a waypoint too close to a junction or would create a U-turn
good work Guido



