@Kirsten-De-Weerd If it was an iOS bug, how come these problems weren't there before the update? I still have iOS 18, so I wouldn't say it depends on iOS...

Wat zou ik nu kunnen doen?

@Steve-Jarrell Gu Question It's controled via wunderwheel or via "extra" controller ?

@Rob-Verhoeff I did not.....I was following the map as it was telling me.

@Con-Hennekens thnkx Con. Dan weet ik het nu wel

@Reinhard-32 said: @Tuxi said: Hat hier jemand einen hilfreichen Vorschlag? Fahre bis über den Punkt 8 und überspringe dann den nächsten Punkt. 9. @jörgen Sehe ich eigentlich auch so, oder man nutzt den MRA Routenplaner in der App. Geht gut wenn man es einmal verstanden hat, kurz nutzen, dazu Route stoppen, bearbeiten, speichern, neu starten und dort weiter wo man gerade gehalten hat. [image: 1780916933921-img_9350.jpeg]

Wat klopt er niet aan dat witte gedeelte? Die volgt precies de lijn die ook je je route zit. Ik denk dus dat die wel klopt, tenzij jouw gedeelde route al niet klopt. De melding "Kan route niet berekenen" duidt op het ontbreken van kaartdelen terwijl je offline navigatie aan hebt staan.

@Vosje Great glad I could help

I found Android's TTS too "robotic" and low-quality lately and thus tried a few alternative engines. (Samsung's has always been my favorite, but, infuriatingly, they don't allow its usage in third-party-apps any longer). After trying out a few free ones, I ended up buying (one-time purchase of 3,99 €) a commercial TTS engine (to be more precise: a specific German voice, "Claudia", of said engine), and am very pleased. Some things are pronounced correctly (e.g. "links halten", see my original post), while others are wrong. But overall, it's easily 300% better (more natural and enjoyable) than Google's German voice, in my opinion. Maybe I'm just particularly picky, regarding this - after all, Android's TTS works great and is free.

@Ed-Lauwerens-0 said: Does anyone recognise this and knows what to do to prevent this, or is it a bug? Yes, I also encountered that during the alpha test. I can no longer determine from the communication with the developers whether this has already been fixed in the public version. In the beta version that is currently being tested, I have not experienced it anymore. And since it is now the developers’ holiday period, it may take a while before a response comes in.

@John-Mul The Gold subscription is for the website route planner only. MRA have two subscription products, the website route planner and the mobile phone navigation app.

I will keep it for the moment. Maybe there will be some updates and in future it will work. Try out Samsung Active 3 which I still have and test it. Thanks for your tips and feedback.

@Marinus-van-Deudekom Thanks

Ok, danke für die Erklärung

First of all, thanks a lot – I could have worked that out for myself. I had a look at it today, armed with my newfound wisdom, and to me it’s neither self-explanatory nor particularly helpful. Especially as there’s a duplicate with the compass on the right-hand side. I switched the display off after a while. Maybe I’ll get used to it eventually.

@Axel-Härtl Calimoto and Kurviger using the TomTom data for this also in their planner

@white.mouse said: Het probleem wordt door Here veroorzaakt. <knip> Volgens mij zijn ze gewoon gebaseerd op historische gegevens. HERE is vrij laat met updates en bewerkingen. Het is niet echt realtime updated. Maar volgens mij is er ook een vertraging tussen nieuwe updates van HERE en kaartupdates binnen MRA??? Ik pas zelf wel es wat aan bij HERE via de mapcreator website en merk dat de aanpassingen die ik heb gemaakt niet direct in MRA te zien zijn maar wat later (uren/dagen/weken zeg maar ff kort door de bocht)

This is the only app where this occurs. HereWeGo? Fine. MagicEarth? Not a problem. OsmAnd? Again, all good. The dreaded Google Maps obviously works fine. It's fine. I've got alternatives, I just need to remember to transfer the GPX files to something else.