@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.

@Con-Hennekens Dankjewel... Zal de app opnieuw installeren, had ik nog niet gedaan.....

@Jesse-Van-Vilsteren-0 Fijn om te lezen! Binnenkort gaat ook het genereren van routes flink verbeterd zijn!

@LE-DIZES-Freddy J'ai mes paramètres à -15 et alors tout l'écran est visible

@Steve-2t said in Driving aimlessly: @RetiredWingMan It's a feature that used to exist but then disappeared and hasn't been seen since. Free ride/drive mode has never been a feature of MRA Navigation Next. It’s hoped that it will become a feature in the future.

@ginogino, The way you describe this is completely like the logic is programmed. When you deviate from the route (at WP2, to get gas), it takes 3 calculations to auto skip WP3, which in your case is 27km further in the route. It looks at the next 10 waypoints and decides which one is closest (calculated over the roads). If you just past WP2, it is not hard to imagine WP9 is closest, so it takes that one. This is exactly how the algorithm is intended. The real problem with the route is the lack of waypoints. If you deviate from a route to have a stop (whether gas, lunch or whatever), recalculations will occur. It is wise to look at the route before taking off again. You do not have to delete any waypoints, just long-press WP3 in order to set that as the new first WP to drive through.

@Adrian-Avram Your suggested solution is completely correct, but in this specific case, it's particularly difficult to explain why the deactivation might not work. As of mid-last year, it wasn't yet finally clear whether the pass would even be reopened. That's why I explicitly referred to it.

@ginogino you can see that the shortcut is not paved. [image: 1742911984197-2025-03-25_16h12_02.png]

@Con-Hennekens said in Navigate a route as track -> user error?: @Erdna said in Navigate a route as track -> user error?: Is this kind of navigation just ignoring any shaping points or what else could I´ve possibly done wrong? No, on the contrary... Usually a sensible way back to the track is provided. What could have gone wrong is that you touched the screen on the routline, specifying your re-entry to the track, indeed by the fastest way. This can simply be corrected by (long)pressing the route line on a point near your location, the track will be re-entered from there. As far as I rember, I did not touch anything at all. I did not need to, because I know every bend and bump on that roads. But I think we will not get this sorted. I will give Track navigation another try some other time and will update here.

@Andrew-Hoffmanns-0 Yes, definitely select the one that seems to work for you. The problem is that you can use Carpe Iter with or without their app. What are you doing? Their app modifies some input.

@daryl-4 Awesome!

Wel enkel als je zelf de tracklog hebt gestart / opgeslagen

I partially redid the ride from last time, this time with ‘navigate as track’ and ‘navigate offline’ deactivated, arrived at the same point as last time I stop and turn off the bike, on restarting the navigation doesn't work anymore, I had to get off the pass and as soon as I got a signal, restart navigation from the beginning, by the way even with the latest version released there is still the bug that if you start a route from the android auto when you are already on the route, myroute app makes you return to the starting point, I had to turn off the bike and android auto, from the app on the smartphone start the navigation and then turn on the bike and android auto.

@simon-ward new version is online 4.38 - 386

@Adrian-Avram If you don't like the app you can delete it ........you now. Saves you a lot of negativity and disillusions about what you think it should be and how it is...

Ah, besten Dank für die Info. Dann muss es wohl so gewesen sein, dasss in dem Moment kein Netz vorhanden war und die Neuberechnung länger gedauert hat.

@Con-Hennekens I would say after implementation of that no other app or device is required anymore. Lets see.

@Nick-Carthew ok - got it, thank you. But usually, if I receive routes from others, I want to modify a little (may other starting point, etc.). Therfore I feel it more handy to operate in a browser by MRA Routeplanner instead of planner in MyRoute-App

Ik ben mening dat eenmaal op de route het nog te lang duurt voordat de route opgepakt wordt. Eenmaal op de route werd nog minimaal 3x herberekend voordat de route hervat werd. Ik was toen al een paar kilometer verder. Als het nog goed herinner was ik ongeveer op de helft tussen punt 10 en 11 toen de eigenlijke route pas werd opgepakt. Bij het rijden van een traditionele route is die ervaring identiek