@Tony-13 In the scenario that you experienced, I would suggest that as the incident was fresh, it’s doubtful that any diversions were in place, so I would have stopped your A - B route, driven around the obstruction and then entered your destination again into the app.

@Albyus said in problem with waypoints:

@Marinus-van-Deudekom hand-shaped

Hand shaped waypoints are specifically intended NOT to be auto-skipped (mandatory waypoint). So you will have to skip it manually if you do not intend to visit it.

@Con-Hennekens said in Integration of remote controllers:

@Guzzist said in Integration of remote controllers:

And I wonder what the better way is to integrate new controllers in the future...

To be honest, I think the most consumer-friendly way to support controllers is for MRA to add them to their list. Unfortunately it can take a while before a new controller gets adopted into the software though. Many controllers have their own software to program their hardware, which would counter anything you program yourself into some table most people would see as a hassle. Also, there are already apps like Key Mapper for Android that are able to convert controller commands to app commands.

Hi Con, I understand your thoughts. And I believe, if you are talking about "programming" it would be seen as hassle by users.
But my Idea is a bit different: our developers should create and fill the table with standard values, sent by the controller. So, the user sould only select his model - and it'swell working. Same as currentl. But - this is the point - If a user is willing to simply select another possible action, a button should initiate - he can do it.
Because many offroad drivers needs a dedicated "handsome" remote controller for the purpose of event. So, not each and every controller has the buttons on the best position for the fingers.
So, it would be highly sufficient, if the user can decide in the table, which button of the controller should do p.e. zoom in at the map in the App.

@Paul-c5 Tree/List view, in addition to the map view, would be nice too.

@JP-d Try and relax about updating maps and just check for updates every few weeks. The chances of you missing an update that affects your route are very small.

@Rob-Kelley 100% agree. IMO, long outstanding issue that does not appear to even be a blip on the developer list. 😞

@stuart-marritt ok - then it's the steps I described in second sektion. You can do this at your phone 😉

@Arjan-de-Vries Ja, je hebt gelijk - er zijn nu heel wat gebruikers die de Remote 2-controller gebruiken met de MyRoute-app. En iedereen zou heel blij zijn als het eindelijk zou werken!

Laten we hopen dat @Corjan-Meijerink snel een oplossing vindt.

@Dave-J-0 Hi Dave Im referring to the track colour, in the MRA its blue, in other apps its higher contrast or you can choose an entirely different colour.IMG_8100.JPG IMG_8099.JPG

@Marinus-van-Deudekom I must be doing something wrong. When I animate my route I see all waypoints along the route

@Jörgen Hi Jörgen, hab mir schon gedacht, daß du antwortest; wollte dich aber nicht direkt ansprechen, damit die anderen User auch etwas davon haben.

Was du geantwortet hast, ist mir alles geläufig.

Es liegt wohl an der grundsätzlichen Ausrichtung von MyRoute-App - die im Gegensatz zu MRA-Routeplanner - leider nicht darauf abzielt, einen Track aus einer GPX-Datei einfach darzustellen. Und den aktuellen Standort einzublenden. Die App will unbedingt navigieren - mit Icons und Ansagen.

Wenn ich mir die GPX-Datei ansehen, dann sind da einfach nur mehrere <trk> Abschnitte drin. Beim Import in MRA-Routeplanner, werden aber automatisch entsprechend einzelne Routendateien erzeugt. Damit beginnt die Sackgasse der Entwicklung.
Und in MyRoute-App kann man eine GPX-Datei (noch?) gar nicht direkt importieren; nicht einmal, wenn man den Routenplaner der App nutzt.

Andere Apps, die ich nannte, können sehr wohl einen Track einfach nur anzeigen und den aktuellen Standort darüber einblenden. Sie können sogar mehrere Tracks gleichzeitig anzeigen, die ggf. in nur einer Datei enthalten sind. Ist ja auch keine Raketenwissenschaft, da nicht navigiert wird. Das macht der (Offroad-)Fahrer selbst. 😉
............................
Hi Jörgen, I thought you would reply, but I didn't want to address you directly so that the other users could benefit from it.

I'm familiar with everything you answered.

It is probably due to the basic orientation of the MyRoute app - which, unlike MRA-Routeplanner, unfortunately does not aim to simply display a track from a GPX file. And to show the current location. The app really wants to navigate - with icons and announcements.

When I look at the GPX file, there are simply several <trk> sections in it. When importing into MRA-Routeplanner, however, individual route files are automatically generated. This is where the dead end of development begins.
And you can't (yet?) import a GPX file directly into MyRoute app; not even if you use the app's route planner.

Other apps that I mentioned can simply display a track and show the current location above it. They can even display several tracks at the same time, which may be contained in just one file. It's not rocket science either, as there is no navigation. The (off-road) driver does that himself. 😉