Via-punt niet herkend - te kleine marge
-
@Nick-Carthew said in Via-punt niet herkend - te kleine marge:
I'm lying back now and having a cigarette
-
Today I drove on the A12 near Gouda and saw 2 times that the app was going offline for a moment. Just a few seconds and than it was back again. That’s a problem I’ve never had before. This must be a bug in the MRA-app.
-
I experienced the same issue as the OP this week. At first I thought maybe my waypoint was off the road. I knew where I was going so it didn't matter but when I got home and checked the route, the waypoint was on the road.
It also happened at the end of two different routes with my endpoint. I rode through the final waypoint and it kept trying to route me back to it. I am using a Pixel 7 and this happened once on my phone and twice through Android Auto.
-
@Tom-Cat said in Via-punt niet herkend - te kleine marge:
I rode through the final waypoint and it kept trying to route me back to it.
This is by design. If you pass the finish, it will keep calculating to it, in case you need the assistance.
-
@Con-Hennekens said in Via-punt niet herkend - te kleine marge:
@Tom-Cat said in Via-punt niet herkend - te kleine marge:
I rode through the final waypoint and it kept trying to route me back to it.
This is by design. If you pass the finish, it will keep calculating to it, in case you need the assistance.
This is a bit unusual. I've never seen that in a navigation app before.
-
@Tom-Cat I prefer it that way though!
-
I find it inconvenient. Extra work and annoying.
-
@Jack-van-Tilburg, it's ideal. You don't have to restart the route of you need to go around the block. It's VERY convenient. About what extra work are you talking?
Thereby, it has been discussed before. It's by design, so it is what it is.
-
@Con-Hennekens said in Via-punt niet herkend - te kleine marge:
Thereby, it has been discussed before. It's by design, so it is what it is.
So no further reaction is necessary.