MRA Community Forum

After a bit of experimentation I've settled on the Dart and Explore combination which gives reasonable contrast and certainly a lot more usable than the default settings.

@Travellexxie sharp

@John-S-Parry Dear John I have extensive experience with the XT and XT2. None with the XT3. The only thing that you have mentioned that the 3D function on that XT3 is what you like. What other big difference would there be that would make that XT3 that great. Up till now I haven't seen any but I hear that there are many. So state them do we van compare them. You are a great fan of Garmin and I'm into MRA those worlds van exist next to each other. Bare in mind that you're posting on an MRA forum zo to me it seems you're brushing of on MRA. That might not be your intention but that's the impression that sticks to me. If there are that many of differences between the XT3 and MRA Please let us know. The 3D one to ME in non interesting but I would like to know other differences. And if they are of great use to the community ask the devs of they could be implemented in MRA. Meanwhile have fun

@Guzzist said: ...other Apps are doing it without AppStore more and more. We don't need the Americans... That has been discussed over and over and its by choice to use the Google Store

@Guzzist Yes and make absolutely shure that recalculation and traffic info is OFF What I do to make shure there's enough shaping points is compare the route with TomTom and make shure they are the same. Even when the Garmin is doing its trick or won't find other roads to plot I have no preferences set in MRA and Garmin

@herman-3j-0 Check the second post from @tenmill-0. The route is good now.

My 2 cts: motorway is in German: Autobahn. Motorcyclists have no business being there, otherwise they would have called it "Motorradbahn"

The combination of Tread and Garmin external storage (i.e. Explore DB) are dangerous to the health of your routes. This means your routes can be manipulated by Garmin without your knowledge. As noted by others here, transfer routes using the wired method where you copy your GPX file directly into the Gamin/GPX folder on your XT2. This will guarantee that your route will not be altered. I know -- it's more work than using the Tread app for copy. It's not really that much more, but an annoyance all the same.

Het moet zijn 5,5 uur. Als de route binnendoor gaat, dan heb je zeker 5,5 uur nodig.

Hartelijk dank voor het warme welkom. @superg: ik ben nogal een impulsieve rijder, én digibeet zonder pc dus routes maken gaat gewoonweg niet

User name resolved. Thanks to the Admins.

@gerson-2-0 sagte: Hallo, Ik kan geen rondrit meer genereren. De foutmelding die ik krijg: Scenic routes kunnen alleen worden gegenereerd wanneer je internet hebt. Dit heb ik getest met zowel wifi als mobile data. Ik heb wel iOS 27 beta 8 draaien, meerdere mensen ook last van? Gr. Perhaps the starting point "set point on the map" is not on the road, please check more closely. Note: the message text is incorrect, should be read differently, will apparently be fixed soon. The distance also plays a role, is it too long? A tip, maybe shorten the radius a little more if it should be a round trip, maybe then the calculation will work.

@corjan-meijerink Hey MRA Team, On this topic there are always messages in the general forum, there is a solution. VG Hey MRA Team, zu diesem Thema gibt es immer wieder Meldungen im allgemeinen Forum, gibt es dazu denn eine Lösung. VG

Just use the nearest gas station as a starting point when you want to share your routes.

To operate tracks isn't the main competence of MRA. May in future...

@Hubert-Thoring said: That's how it works offline... I never said route planning doesn’t work offline! I said that the RouteLab option (which is actually the web planner on mobile) doesn’t work offline, not the MRA Route Planner! And I think you’re still missing the main point, which is the “POI naming/text display” issue.

Alles werkt nu weer Groetjes Jens

I agree with all the sentiments that this needs to be addressed. I think the best way to address this is not via a txt file but by a number of profiles that can be configured by the end user. These profiles would be configured in the online planner and synchronised to the app for navigation. The end user can then select the most appropriate profile for their current situation. So for example, I might configure a profile for use on my bike where I use a ruggedised phone for navigation. In my car I have a built-in Android Auto/Carplay device which would use a different profile. For my camper I have a different set of requirements and therefore a different profile. The key is that I as the end user can define, easily save and then select the best profile for my scenario. Settings would include, but certainly not limited to: map colours, road colours, contrast, route colour, line width and opacity, map scaling, zoom level at which POI's appear (by category), etc etc. This way you can set a "sensible" default that can be used, probably by a majority of users, but also give "power" users the opportunity to customise their navigation experience. We all use different devices in different environments, some are colour blind or have other visual impairments and others have very strong preferences. The development team will never be able to accommodate all of these scenarios so give the end user the option to choose.