A -> B route Automatic recalculation always active
-
A -> B route Automatic recalculation always active
Hello,
I have turned off automatic recalculation and am using the display of the planned route from my collection in grey. This works very well, even though the request for recalculation on the monitor is actually unnecessary. But in any case, the recalculation is not being performed.I have created an A -> B route on my smartphone. If there are deviations from the route, automatic recalculation is always performed.
How can I change this?
RTA -> B Route Automatische Neuberechnung immer aktiv
Hallo,
ich habe die automatische Neuberechnung ausgeschaltet und nutze die Anzeige der geplanten Strecke aus meiner Sammlung in grau. Das funktioniert sehr gut, auch wenn die Anforderung der Neuberechnung auf dem Monitor eigentlich unnötig ist. Aber die Neuberechnung wird jedenfalls nicht ausgeführt.Ich habe eine A -> B Route auf dem Smartphone erstellt. Bei Abweichungen von der Route wird immer eine automatische Neuberechnung durchgeführt.
Wie kann ich das beeinflussen?
RT -
Isn't that the idea of a typical A to B route.
Point B is the goal. The route is just to get to Point B. How the route goes is less of an issue.(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
Exactly. For A to B routes it will always recalculate as there is no scenic tour / pre planned route so not recalculating in that scenario makes sense.
-
Understood!
RT -
Isn't that the idea of a typical A to B route.
Point B is the goal. The route is just to get to Point B. How the route goes is less of an issue.@M.-Schrijver I disagree...this program is supposed to take us on the route "we" want to go. I ride a bike, so going 100 miles out of the way is not uncommon! I agree there should be something to shut this off. If I want to go from point A to B....and take XYZ as an alternate route, I should be able to. I believe that's what we pay for...No?
-
i think, creating a scenic route is for you D.Griffin.
But i have not tried out the recalculation on/off in this.
RT -
if its technical possible I would suggest to honour the recalculation setting. It makes the app a bit more consistent in my opinion. The fact that the start is not a waypoint (which would make the A to B navigation into a route navigation) is a detail.
I havent tried it but what happens if I deviate from the route after having started a A to B navigation as "shortest" (in stead of "fastest")? Will the app still find the shortest path ?
This is not very important to me, more important is that the app also recalculates during route navigation (despite the recalculation setting disabled). For example when a shapint point is skipped on purpose).
