Issues, system automatically skipping waypoints and therefore changing the whole route

[Corjan Meijerink]

@Jörgen-Johansson You never need to skip one by one
Simply long press the waypoint on either the map or in the waypoint list to resume from there.

If autoskip shows weird behavior, just turn it off.
4.1.3 will include significant improvements. Release will be early next week.

[Con Hennekens]

@Jörgen-Johansson, Skipping waypoints one by one is a thing from the "Previous" and separate "Navigation" app. Currently Navigation is done with the Myroute-app. I almost can't believe that it is still functioning at all, but humor us and please paste a screenshot here? What is the version of the app?

[Jörgen Johansson]

@Con-Hennekens
Hi! It's 4.1.2 - 305. Tested another route yesterday again and I cannot find any logic in how it skips via-/waypoints. Sometimes it's 1-several viapoints to the next waypoint but other times to the end position.
What do you want screenshots from? I tried to ad files to my original message but when trying I was told I'm not authorized to send files.

[Con Hennekens]

@Jörgen-Johansson, I ask for a screenshot to determine if you were still on the "previous" Navigation app instead of Next. But the version number clearly points out my suspicion was wrong

[Jörgen Johansson]

@Corjan-Meijerink Thanks for your info!

I have again spent some hours testing. When I turn off "Skip waypoints automatically" the app doesn't skip nor via- neither waypoints. Still wish to be able to turn on "Skip waypoints aut" so will test as soon as I see 4.1.3 and then reply back here again!

[M. Schrijver]

@Corjan-Meijerink
De new skip button in Android Auto and Apple Carplay does this works as a skip button for all routepoints untill current/first upcoming one?

[M. Schrijver]

@Jörgen-Johansson
I've read your post. Two comments from my side.

Yes, you are right auto skip should work properly. And i suspect MRA will do it's best to make it better.
This is an important function of navigation.

Knowing the issues with auto skip and other deviation related issues. Why not place your routepoint for your stops a bit before the actual stop . Then you will reach the routepunt in a proper manner and will have less issues.

[Jörgen Johansson]

@M-Schrijver Hi!
There's no problem at all as long as I stay on the planned route. The problem occurs when I take off some 10-200 m for a coffee, fuel, viewing something or similar. When then going back to the route multiple via-/waypoints are skipped.
However, as mentioned by Corjan above, I will await the new release in the beginning of the upcoming week and test again.

[Con Hennekens]

@Jörgen-Johansson, If you deviate from the route and do not follow directions to rejoin the route, you will get multiple recalculations. Auto-skip is not changing your route, you are doing it yourself Of course it is really easy to adjust the waypoint you are guided towards, simply by long-pressing it.

The next public release will contain a lot of improvement to the auto-skip function though.

[Brian McG]

@Jörgen-Johansson I can confirm I have seen this same problem on trips over the last 2 weekends
Running version 4.1.2-305 in offline mode.
A small deviation off of the route & MRA would then skip multiple shaping points & route direct to the next Via point
Trying to get back on the the route by long pressing the next shaping point did not help. The route would calculate to that next way/shaping point ok but on reaching that point it would then re-skip the next multiple shaping points again routing directly to the next Via point
Hopefully 4.1.3 resolves this issue as I have a 10 day trip to France in early June

[Thomas Scharrer]

@Con-Hennekens I have seen the same problem but I didnt even report it until I saw this thread because I thought something is wrong with my specific system since thousands of people are using MRA without this crazy problem, now however I see that this is in fact problem.

Please note that I am not using carplay, just the phone and I am also not able to operate the phone constatly when riding motor bike.
The result of this is that I am getting totally crazy instructions. It is in my opinion impossible to plan a longer route so exact that you can only stop on pre-defined stops etc. I need to take a break sometimes when I see a nice place or fill up fuel etc.
After such a stop, even if I am exactly on the route I have planned again, I am getting loads of crazy instruction to turn right, left or turn around etc which make no sense at all because I am driving on the actual route.
Sorry but this is not navigation, its creates total confusion.

I really hope that this will be fixed in the next version.

[Stefan Hummelink]

@Thomas-Scharrer said in Issues, system automatically skipping waypoints and therefore changing the whole route:

It is in my opinion impossible to plan a longer route so exact that you can only stop on pre-defined stops etc.

Surely this is possible, it just takes some additional research haha. Nevertheless is somehow find yourself deviating from your route because of a stop you did not plan beforehand, it makes total sense the app is continuously recalculating and eventually even skipping your upcoming waypoints. How can the app know you're not deviating due to roadworks but instead are only going to a restaurant? It simply cannot. These are jmho special circumstances that require special attention.

If you notice at the unplanned stop, the app skipped 3 waypoints, simply long press and start from the nearest WP when moving out again.

If the app still messes things up after doing the long press, I agree the app is showing some faulty behaviour.

But suggesting the app should not skip anything when deviating to go to a unplanned restaurant but expecting it to skip when you do the exact same but now due to encountered roadworks or whatsoever makes no sense at all haha.

@Thomas-Scharrer said in Issues, system automatically skipping waypoints and therefore changing the whole route:

no sense at all because I am driving on the actual route.

Please note you're navigating a route, not a track. "being on the route" is not the same as "being on the track" for that matter. You can be on the route, but it can be calculating to some waypoint you passed or upcoming but not where you expect it. Therefore the app does what it is supposed to do, direct you to the next waypoint whichever that may be.

[Thomas Scharrer]

@Stefan-Hummelink I am not even talking about a longer detour or deviation from the route to find a restaurant etc, I am talking about stiff like driving 20m off into a parking place or so.
After that stop and these 40m deviation from the route I am again joining the planned route and and I think any other navigation system would recognize that but for some reason MRA doesnt and creates completely crazy directions.
If you think this is how it is supposed to be then I am not able to use MRA for navigation and there is no point to create and navigate a route if the system does not follow it at all even if you are on the route.

When I export my routes to my beeline system and I have a deviation of the route as mentioned, it immediately recognices the route again when I am back on it

[Con Hennekens]

@Thomas-Scharrer, big improvements to the skip algorithm will be available from the next public update. The behaviour like you describe in my opinion will be one of the fixes.

[Thomas Scharrer]

@Con-Hennekens Thanks, thats great to hear. When will be update be available?

[Con Hennekens]

@Thomas-Scharrer, whenever it finishes being beta only
Really, that's up to the devs, I can't tell you.

[Stefan Hummelink]

@Peter-Schiefer said in Issues, system automatically skipping waypoints and therefore changing the whole route:

If you deviate from the route for other reasons, the system always calculates the next possible suitable point on the original route, whether this is 30 meters back from a petrol station or a U turn around a block of houses

Well the most import difference here is that we, in general, when using MRA next are navigating a pre-planned route using those waypoints! That is very much different from an a2b route as we generally use in car nav systems or similar! You tell the nav to route you on a pre-planned path, any other system as you refer to is simply instructed to guide to from start to end, no matter the roads it seems fit to do so! This is a major differences in the two distinct scenarios.

Your answer seems to indicate you've misinterpreted my post as a negative critique to @Thomas-Scharrer which is definitely not the case. I was merely putting forth my opinion regarding the statement that it does not make sense the app is autoskipping waypoints when deviating from the route.

Now Thomas mentioned specially in the post above, which came before this post from me as a response to yours haha, that his deviation from the route was only a few meters. That makes it a whole different story.

Yet, the mechanism in general, still holds.

@Peter-Schiefer said in Issues, system automatically skipping waypoints and therefore changing the whole route:

Since MRA only takes route closures into account in the initial calculation or already in the planning stage, if stored in HERE, automatic skipping should not exist at all.

I never referred to the traffic information from HERE nor the handling of the app regarding that info. I mentioned roadworks as a practical example of things you can encounter during your trip, that make you explicitly deviate from your meticulously pre-planned route.

[Stefan Hummelink]

@Thomas-Scharrer said in Issues, system automatically skipping waypoints and therefore changing the whole route:

If you think this is how it is supposed to be

If these are the distances at play, no that is surely not how it should work. See my post above as response to @Peter-Schiefer.

[Con Hennekens]

@Peter-Schiefer said in Issues, system automatically skipping waypoints and therefore changing the whole route:

Since MRA only takes route closures into account in the initial calculation or already in the planning stage, if stored in HERE, automatic skipping should not exist at all. What are the rules or reasons for this?

This is a curious question. Closures are taken into account in each and every calculation, whether in the planning state or during navigation. Except when "disable seasonal closures" is enabled in planning, or "traffic aware route calculation" is disabled in the app's navigation settings. Disabling seasonal closures in the planner has no effect whatsoever during calculations while navigating. Besides, all this, closures can change in the time between planning and navigating.

Also, many times auto-skip is not triggered by closures, but by taking wrong turns, or avoiding heavy traffic for example. So yeah automatic skipping should definitely exist...

[Con Hennekens]

@Peter-Schiefer said in Issues, system automatically skipping waypoints and therefore changing the whole route:

up to now MRA says we have no Live Traffic or TMC connection and cannot react to traffic change during the route.
Are I am wrong?

The app DOES have live traffic data, but it is not being used to update your route continuously, or give out suggestions for more time-optimal changes while navigating. This is something that is on the list, but given the use case for scenic multi-waypoint routes (which is the main reason for founding at all) not a high priority yet.

However, the live traffic data (no TMC but internet) IS being used for route calculations. Also while in online mode during navigating you can see by the color of the road the delay on your route.

Last week I sent a note confirmed by other members too that MRA wants to route you back to the original route even when ther is a real better option present and this without additional waypoints only from A detected by GPS to B my home.

in A2B routes there is not such a thing as being routed back to the route. You are being directed to the next waypoint, and in an A2B route that happens to be the final destination. If you think that after a recalculation the suggested route is not logical, you and the algorithm disagree about what's logical That happens for me in Google maps also very often, probably because I am more stubborn that it

On the other hand MRA seems to skip waypoint far ahead if you only deviate by entering a filling station.

As mentioned earlier, big steps are taken in the upcoming public release.