Quote from Guido on 13.01.2022, 06:16

Sorry about that Oliver. Will have a look at this asap. Working on a small bug fix update now so should be able to incorporate a fix for this too.

Quote from fxstein on 30.01.2022, 13:48

This seems to have gotten significantly better with the latest version(s). On our 750 mile trip the past 2 days this was always correct.

Only once (that I caught) had the arrow in the left top corner the distance to it missing. We were some 5 miles away and I could not tell. Tapping on it to force Scenic to speak the distance gave it to me. After that turn, the distance to the next turn 20 miles away was again displayed.

Quote from Guido on 30.01.2022, 19:19

Ok. Will have a look at this as well. Tx

Quote from Trashhauler on 27.02.2022, 00:11

I have distance to next stop set. When there is one stop and then destination after the stop it does not show distance to destination.

Quote from Guido on 27.02.2022, 00:34

Quote from Trashhauler on 27.02.2022, 00:11

I have distance to next stop set. When there is one stop and then destination after the stop it does not show distance to destination.

Not sure I understand. With that setting  it would only show distance to destination after you passed the stop. Is that not happening?

Quote from Trashhauler on 27.02.2022, 01:05

Hi Guido - after the first stop it is showing zero distance to destination

Quote from Guido on 27.02.2022, 01:48

Ok. Will check that for the upcoming update. Sorry about that.

Quote from Trashhauler on 27.02.2022, 01:49

Thank you

 

Quote from Guido on 27.02.2022, 15:19

@trashhauler I did two rides today, but couldn’t reproduce this problem. I purposefully added a stop to the rides, but when I passed the stop Scenic showed the time, distance and ETA to destination.

Could be that I’m not exactly replicating your scenario. Not sure. Or is it possible that you did not truly reach the stop but passed it at some distance (more than 50 meters / 165 ft)? In that case Scenic would not have recognized that you reached the stop. However you’d see more strange things in that case. It would try to u-turn you to get to that stop after all.

Quote from Trashhauler on 28.02.2022, 01:52

Hi Guido

I didn’t realise that 50 metres is the distance. I could well have missed the points by more than that.

I will try again and see what happens.

Roger

Quote from rocminc99al on 28.02.2022, 11:25

I wonder if 50 meters is a standard used across industry, or it's specific to Scenic.

Quote from Guido on 28.02.2022, 12:46

I don’t know either. 50 meters just sounded more or less practical to me. I mean… if you have a gas station or a restaurant as a stop, you’ll most likely get into 50 meters of where you place the stop. Maybe for bigger things, like a big parking or something you’ll not get within 50 meters, but honestly I think that would be more exception that rule. And you would be able to manually skip that stop (through the skip stop button in the nav menu) should you not reach it.

I could make it bigger but that would also impact routing and rerouting. E.g. to reach the stop you need to make a turn…. But if you make it too big you would have already ‘reached’ the stop (came within let’s say 100 meters) and then the turn would be skipped and possibly missed. I.e. you’d miss your gas stop

we don’t know for sure yet if @trashhauler ‘s issue is caused by this so I suggest we wait for that. Haven’t had any issues other issues with the 50 meters yet.

Quote from rocminc99al on 28.02.2022, 17:59

Thinking back, I think my old TomTom 730 had a tighter tolerance.  I've had several issues with waypoints placed on the intersections in the past.  If it was a little bit off the route, TomTom would suggest a u-turn.  I was usually making an effort to place waypoints before or after the intersections (planning was done using MS Streets & Trips.)  A 5-lane highway is about 60 feet wide.   It's less than 20 meters.  Hopefully 50-meter tolerance doesn't interfere with routing and directions.