@Herman-Veldhuizen said in App does recalculate despite recalculation setting being off: Then while driving I need to see the ETA to the next possible stop. Yes that's what I meant of course, the first stop in line. Let's see if devs (they are reading along) see a possibility to a plausible solution for you.

@Corjan-Meijerink : Bedankt voor je reactie. Ik heb een support ticket aangemaakt met alle gevraagde info toegevoegd.

@Corjan-Meijerink Thanks.

@borde-0 graag gedaan

@white-mouse-on-the-motorbike if you are using an Android device, check if Animations are turned off from system settings ! Same happened to me, and everything is working fine after enabling animations.

@Angelo-d op die manier machtig je de incasso

@white-mouse-on-the-motorbike Dank je!

I don't see the 377 number when looking at my installed app in settings. The version number (in this case '4.3.4 - 377') can be seen in the account screen within the app: Menu (top left) -> Account (top right) scroll to the bottom You won't see the full version info in Google Play Store. [image: 1735063661673-version.jpg]

@M-Schrijver That's what threw me, the original settings that I had on the phone worked well with Waze, and Google maps, but affected MRA, which made me feel I was doing something wrong in the app. Trouble is I don't like messing about too much with phone settings, as before I know it I've buggered everything up.

I did some more tests and probably figured out what was going on. Here are my thoughts: When creating a route with the web planner, the calculated result is supplemented with "hidden shaping points" (similar to the GPX 1.2 format) to store and preserve its shape. An imported track (route track) gets its shape from the (typically huge amount of) track points. Let's call this the "original shape". Opening such a route or track with the navigation app shows its original shape as a preview. When starting navigation, the original shape is drawn on the map as a white line. On top of it, a route will be calculated using strictly HERE data that follows the original shape as closely as possible. The result is drawn as a blue line. If white and blue match, we see just a blue line; otherwise, both. If a part of the blue lines deviates too far from the white line, it will be cut and replaced by a straight line. The same happens when deviating during the navigation: the blue line will be recalculated and leads back (or close) to the white line. All turn indications refer to the blue line, not the white line. So, we are not navigating a pre-calculated route or track; we are actually navigating a route that is calculated on top of it and is always based on HERE data. I'm curious about any feedback. Am I right? Or, if wrong, what's then going on?

@M-Schrijver when navigating an offroad road as track, the original track data is used. However, as the entire route is marked as offroad, there is no track data. The track data is just straight lines between all waypoints The app does calculate a nice route to the nearest point on the track. Therefore you get a correct route to a point on the track and then just straight lines as the offroad route has no information.

I haven't used lane assist very often so far. For some tests, I gave it a go yesterday on a 50 km trip with a mix of highway, overland and cities around Hamburg / Germany. About 30 % of all lane assists were not exact or downright misleading. I turned lane assist off again...

@moto_ness open the app settings and you can choose the unit

@Robert-Hillen said in Tankstations tijdens navigatie: Misschien een idee dat als je klikt op dit tankstation plaatje dat deze als eerst volgende routepunt wordt toegevoegd en je dus meteen navigeert naar dit punt. Dat is precies hoe het werkt, als je als route navigeert (en niet als track).

@white-mouse-on-the-motorbike, of course not, previous versions did not have this track navigation

@Corjan-Meijerink Ah yes it might very well have been the case. Then I was only a bit confused by the text that tells me "... Go online ..." while being online. It is probably better to not show that part of the text but no big deal.

@seasdes I sometimes see this, too. In my country (UK),we drive on the left but I also drive a lot on the Continent, where they drive on the right. I see the misnumbering here at home and abroad, so it has nothing to do with the side of the road you drive on. What I think is happening is that MyRoute sometimes interprets a small side road ‘exit’ (sometimes leading nowhere other than to a gated field or a tiny road, used only by a person on foot or now just redundant) as a full exit, whereas other apps ignore it. I have seen other apps do the same thing (ie. adding an extra ‘exit’) when MyRoute ignores them. I have also seen some apps interpreting large roads, where there is an exit lane off the roundabout and an entry lane onto the roundabout, as both being exits. Sometimes, you just have to use your common sense and ignore the number. PS Most roundabouts have a sign on their approach, showing where the exit roads lead to and their position on the roundabout. Use the information the signs give, alongside the navigation, to help work out which exit to take. Just like we used to do before navigation app’s appeared to rule our lives.

The original route was calculated online but you navigate offline. Probably due to traffic / online data the white line was calculated but as you switched to offline another route has been taken.

@Herman-Veldhuizen @Con-Hennekens @Corjan-Meijerink. The latest app update looks very promising. I used navigation as tracks, no automatic recalculation. My route (set of possible stops) is now finally a set of via points (such that the app shows me the time/distance to the next possible stop) and it doesn't recalculate, just as I wanted. Driving a bus is maybe not so much different as driving a scenic route with a motorbike. Both go after a set of possible stops. The app has lots of potential. Thanks and keep up the good work.