A few weeks ago I rode a route that I have done many times. on this occasion the NN did exactly as you describe here. tried to send me off and back on the motorway at almost every junction. I had 1 start point 400m away from my house and the next shaping point was located at the end of the motorway section. I did not need anymore as I know the route, it was a means of getting to the twisty toads and these two points were circa 50miles (80KM) apart. only reason I had the two initial points was to give me a rough arrival time. route as track I sent the log files to the devs, did not get an explanation, which I wasn't really looking for, the answer I received was, they would use the findings from the log files to help with updates. which was my intention when I sent the log files. curiouser and curiouser

We take all feedback serious but please, create a support ticket. Then we have an official way to communicate. Obviously audio is critical.

Allen bedankt voor de diverse zienswijze op mijn vraagstuk. Laat de ontwikkelaars adhv onze opmerkingen maar iets van maken (of niet).

Danke für den Link, Jörgen. Den Beitrag von Corjan kannte ich noch nicht, werde ihn jetzt "beobachten". .....und hoffe, dass das Problem bis zum Beginn meiner Bulgarien-Tour am 16.8. erledigt ist...

@Brian-McG, what issues. Explanation of how things works is hardly an issue. Not adhering to them could be an issue though

Is there any progress or solution available? 2 weeks ago I got a response to my ticket in the support section that a new version will be available in a week. So another week went by, my ticket was closed and the problem still persists. Any chance to downgrade to 5.0 on IOS?

Ich würde kaufen, aber kein Abo nehmen. Ich brauche das zu wenig, deswegen warte ich auf ein Angebot. Das kriege ich, dauernd, aber nur für das Abo und nicht für Lifetime

@Mike-wiruth, I think you enabled some messy track to be visible on the map? Try this: On your phone, in the main map, press the map-style button. [image: a010dd02-e51d-44ad-bc59-e3caa487c7a2-image.jpeg] Then tap the second menu option: "Routes visible on map" [image: c36bc9cb-48ae-4d30-b144-351ba252e19b-image.jpeg] If any routes are listed here, delete them by the X on the right Or click the bin symbol to delete them all at once. [image: 8c62710a-5ac2-47a8-9601-1687bea86bb9-image.jpeg]

@Pierre-c would you possibly be able to share a route where you consistently get the added time & could you check if the distance is the same at the start of the navigation as is calculated on the web planner? I agree with what @nick-carthew is saying & this is how things should work MRA does behave as such most of the time but occasionally it has glitches or edge cases so it would be good/helpful if someone could check your route

That´s why pictures help.

AA and ACP are an extra layer of complexity but they are certainly not the cause of most problems.

Because some apps can run in the background and are not really active on that moment.

Last route is last route edited in app or web page.

I honestly can't tell you why it happened, but I can assure you I didn't accidentally disconnect... the same thing happened when the ability to automatically deactivate additional devices was implemented (if I remember correctly)... but I remember it was a normal thing... here it even synchronized my entire route database from scratch...

@ErikMatthezing The irony is that if you use Google Maps or Apple Maps, you wouldn't think (I certainly wouldn't) to verify the map against HERE, OSM, TomTom, etc. You accept the map/route is accurate and go on with your life. Somehow, we've come to believe that a checklist item in using HERE is to compare it against others maps for accuracy for everyday use. It's reality. At the same time, it's not ideal, but an aspect of MRA that all users should understand.

The same thing happened to me but on mobile devices, both iPhone and iPad, but it seems to me that if I put Google on top, this is what I think the problem is, the map doesn't respond correctly, as if the software needed more resources for a stretch and the processor couldn't handle it, then if I change the map and put MICHELIN for example, everything goes back to normal... it's been happening for a few weeks now, I even wrote about it somewhere, but it seems to me that it wasn't given too much importance... I thought it was just my problem... but apparently that's not the case...

@RetiredWingMan

@Brian-McG @brian-mcg You're right. This has nothing directly to do with transferring files other than it being one of the pieces that ensure Zumos operate correctly as navigation devices. If that doesn't interest you, so be it. BTW, Garmin GPS routing algorithms have changed over the years, pre-Zumo you could take a Basecamp route calculation to the bank in that it would 100% match when recalculated in the Garmin GPS. That's no longer the case. I'm surprised you didn't know this given your "mult-multi years" Garmin experience. To the topic, this discussion has everything to do with: The HERE map not placing the road where it actually is. The MRA app recognizing the map discrepancy, but the Web Routeplanner not showing any overt alert. Sync should actually mean Sync. The MRA "Skip Waypoints automatically" enabled not working in this scenario. I was able to dynamically enable the XT3 to successfully recalculate at WP#7, so what's with the blanket "advice not to enable the recalculate function is decades old"? Nothing is absolute, yet you're hanging your hat on it. Odd. I'm trying to be transparent and reasonable, and I can say with complete honestly that the XT3 worked better than the MRA app in successfully routing the section from WP#7 to WP#8. If this had not been a verification test, and I was just routing with the XT3 (forgetting the app), I probably wouldn't have known there was a problem at all. I would have been on the straighter section on top of the mountain ridge before being able to look down at the route, and I wouldn't have seen that the XT3 handled the situation without any intervention. Again, thank you for helping me unravel what happened. We obviously don't agree on some things, but I appreciate the input you provided.

@Hans-van-de-Ven-MR.MRA ik heb gisteren een vandaag de functie uitgebreid getest. Met een AB route en afwijken van de route, hetzij doordat ik dat zelf deed naar bij wijze van toeval ook omdat ik een onverwachte afsluiting tegen kwam. In beide situaties werd herberekenen keurig volgens verwachting uitgevoerd. Ik kwam keurig op mijn route terug