@Dae-0 I totally understand what you mean, I’ll see what we can do about that

@Corjan-Meijerink said in Fouten in berekening / errors in calculation: Dat rode routepunt "1" is automatisch geplaatst door de app wanneer de calculatie op basis van een track (gegenereerde OSM route, met bepaalde bochtigheid). Je zou verwachten dat WP1 je huidige locatie vertegenwoordigd. Daarom vond ik het vreemd dat WP1 zó kort bij de bestemming ligt, terwijl het toch een 100+ KM route betreft.

@Robert-Laudensack Thanks for the feedback! Crashes: working on it! Lagging: continuously trying to improve it. Will fully be addressed when in final stage of development. Voice guidance: will be more configurable / improved later! Orientation lock: definitely will be added! Is also on our own wishlist Previous waypoint: we might add a button to go to previous but for now you can indeed achieve it with a long press on any other waypoint Great to hear you are happy with the other changes!

@Nick-Dawson Happy to hear all is good (ignoring the delay issue)! Regarding the delay, this is something we are working on and will be improved!

Dank voor het delen!

@Mopetenpit great to hear that!

@Corjan-Meijerink Got it. Thanks.

@Dae-0 yes totally agree , hopefully this will improve on the later versions

That "strange" word is linguistic jargon for two words that are written identical but with different meanings dependent on the way it is pronounced. It's a known word in Dutch too. My guess is that it was a little bug in the speech synthesis software, and it was fixed by the developer of that module.

@Steve-Lynch Thanks for sharing! We already saw some crashes in the logs so it isn’t completely solved yet

@Brian-1g This is a known issue and we are working on it! We attempted to improve this is in a previous update but that is only on low speeds / at roundabouts

That’s true! But the app won’t use them (yet)

@Corjan-Meijerink said in Route Color doesn't change after skipping Waypoint: Hope this clarifies what happens. Honestly, it took me a minute to understand, cause i didn't knew this behaviour before. Everything is fine now. @Con-Hennekens @Herko-ter-Horst @Corjan-Meijerink Thank you all for your precise explanations. Greetings Ronni

@Con-Hennekens Correct! So if you download The Netherlands (or whatever country) and start your navigation and never deviate from the route. You can drive completely without internet For the (re)calculations we still require internet. When that isn't the case, the actual offline mode can be used! This will be implemented together with CarPlay

@b0hd1 Thanks for sharing, I’ll process these for the next update

@Franz-van-Lammeren Het probleem zit er inderdaad al sinds dag 1 in Ik heb morgenochtend een afspraak om de oplossing online te gaan zetten!

Thank you for the good reply.

Hello Hans, I've split the route in 2 parts and indeed, I can now load them in the app also. I've also 'disabled seasonal closures' in the toolkit. However, that in itself didn't resolve the issue, I really had to make the routes smaller. (By the way, I usually break the route up in 'day' parts, when I'm ready with it. While I'm working on it, I like to keep it as the whole route, so it's easier to change the daily stops, in case we end up with 1 long day, or if we want to bring in a relax-day. I'll see if I can work with the 'add route' option, to get more then 1 day in the view. At least I know now that I have to split the route into smaller parts, before I can use them in the myroute-app. Thanks for your help. Ad.

@Corjan-Meijerink, vanmorgen weer een stukje gereden. Met de Nieuwe app en met vorige app (Navigatio). Een route gemaakt van A naar B. Daarna bewust een andere route genomen dan is aangegeven. Het viel mij op dat Navigation dit veel sneller doet dan MyRoute-app Next. Kan dat kloppen? Het lijkt wel of het GPS gedeelte langzamer reageert bij de Next app.

With pleasure!