Shaping point not skipped
-
https://www.myrouteapp.com/route/open/10824858
Using App version 4.3.8
Using all waypoints, skip waypoints automaticly, No automatic recalculation, navigate route as track.Today the shaping points in this route were not skipped. It looked like the app was treating the points as via points. It started already at point 2. I did stay on the main road as I had nobody to drop off at point 2 which is just off the main road. The app tried to send me back to point 2 for multiple times. Same problem at the following points.
This is a serious issue for me. It used to work and it maybe still does for other routes. This route I drove for the first time. Luckily the road was easy to find and the view was magnificent and I could ignore the audio instructions.
-
https://www.myrouteapp.com/route/open/10824858
Using App version 4.3.8
Using all waypoints, skip waypoints automaticly, No automatic recalculation, navigate route as track.Today the shaping points in this route were not skipped. It looked like the app was treating the points as via points. It started already at point 2. I did stay on the main road as I had nobody to drop off at point 2 which is just off the main road. The app tried to send me back to point 2 for multiple times. Same problem at the following points.
This is a serious issue for me. It used to work and it maybe still does for other routes. This route I drove for the first time. Luckily the road was easy to find and the view was magnificent and I could ignore the audio instructions.
@Herman-Veldhuizen said in Shaping point not skipped:
The app tried to send me back to point 2 for multiple times. Same problem at the following points.
This sounds like you are NOT driving in "route as track" mode. It then takes about 3 recalculations to skip a waypoint.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Herman-Veldhuizen said in Shaping point not skipped:
The app tried to send me back to point 2 for multiple times. Same problem at the following points.
This sounds like you are NOT driving in "route as track" mode. It then takes about 3 recalculations to skip a waypoint.
@Con-Hennekens I agree but the setting was that I was navigating as a track. See picture below. I suspect that the app is not always using the setting as it should.
-
@Con-Hennekens I agree but the setting was that I was navigating as a track. See picture below. I suspect that the app is not always using the setting as it should.
@Herman-Veldhuizen The only thing I can think off what I did different is that for this route I have used both the route planner in the app and the planner on the web to edit and move points. Usually I just import routes from an xml file.
-
@Herman-Veldhuizen The only thing I can think off what I did different is that for this route I have used both the route planner in the app and the planner on the web to edit and move points. Usually I just import routes from an xml file.
@Herman-Veldhuizen It happened again today. This time I was able to get screen dump of the settings during navigation and the log on arrival at the destination.
I added a shaping point (7) called 'to be skipped' before starting the navigation specifically for testing . There is definitely something broken. No white line (planned track) becomes visible after I decided to stay on the main road (skipping the point). After passing the point the tries to send be back to that point.The route
https://www.myrouteapp.com/route/open/10819850I can email the MRA log.
-
@Herman-Veldhuizen said in Shaping point not skipped:
The app tried to send me back to point 2 for multiple times. Same problem at the following points.
This sounds like you are NOT driving in "route as track" mode. It then takes about 3 recalculations to skip a waypoint.
@Con-Hennekens
Even in Route-as-Tracks it takes 3 recalculations before a point is skipped.
That is not no good enough.
If you use Route-as-Track and you are getting (back) on the track. The track should immediately pick up without any recalculations.Besides this. The recalculation should not only be based on the amount of recalculations but also on how long (time) you are back on track/route.
Example.
Let say you are back on your route/track for 15 sec but there has only been 1 recalculation. The shaping point should be skipped. Because you were given time enough to decide what to do. And you choose just follow the route in the right direction and skip the missed shaping point(s).As i experienced more than once. 3 recalculations can easily takes multiple kilometers to be executed. That is far to long.
The thing also is that the 3 recalculations is used for every missed shaping point. If you were forced into a detour and because of this, you missed 3 shaping points. You need to wait for 9 recalucations before the missed points were skipped. In this time there is large change you'll pass new shaping points but MRA is still busy with the missed ones. The passed ones will be placed in list of missed shaping points also.
You get the idea of this problem.(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
@Con-Hennekens
Even in Route-as-Tracks it takes 3 recalculations before a point is skipped.
That is not no good enough.
If you use Route-as-Track and you are getting (back) on the track. The track should immediately pick up without any recalculations.Besides this. The recalculation should not only be based on the amount of recalculations but also on how long (time) you are back on track/route.
Example.
Let say you are back on your route/track for 15 sec but there has only been 1 recalculation. The shaping point should be skipped. Because you were given time enough to decide what to do. And you choose just follow the route in the right direction and skip the missed shaping point(s).As i experienced more than once. 3 recalculations can easily takes multiple kilometers to be executed. That is far to long.
The thing also is that the 3 recalculations is used for every missed shaping point. If you were forced into a detour and because of this, you missed 3 shaping points. You need to wait for 9 recalucations before the missed points were skipped. In this time there is large change you'll pass new shaping points but MRA is still busy with the missed ones. The passed ones will be placed in list of missed shaping points also.
You get the idea of this problem.@M-Schrijver It didn't recalculate on my other routes (I have the setting to automatically recalculate set to off). Maybe the shaping point is closer to the main road than the points I had on previous routes.
I totally agree that the app should not recalculate (with the recalculation set to off). When I have ignored instructions to drive a planned route then I can have made a conscious decision to do so and expect the app to be silent about the missed point(s), a non intrusive warning that I am deviating from the planned route would be fine. And as soon as I am back on the planned route the App should just forget about the point(s) which I skipped. Indeed when the app tries to send me back to the skipped point I miss the instructions to navigate to the next point.
Eventually I hope that this behaviour can also be the behaviour for via points (when navigation a route as track) but that's for another time.
