Updated beta! 4.3.4 (372)
-
@Corjan-Meijerink it seems that there’s no longer a differance Between route and track. My question is what Will happen if you export that track to let’s say a Garmin device. Will it see is as a normal track and thus having the same problems as a track has in a Garmin. Just 2 viapoints and when déviations from the track resulting in a boring ride to the end or Will there bée a lot of shaping points beeing added to that track and making it a route. My guess is that it doesn’t so for Garmin user it would mean that a route still would be MY prefered situation.
What do you think @Corjan-Meijerink or even better what us your expert opinion on this@Marinus-van-Deudekom that’s where the fun part starts
(and why it has been quite some work).
Under the hood we use a lot of internal stops along the track to prevent you ever being sent straight to the end
If you have 2 viapoints (start & finish) you won’t ever be sent straight to the end. The only situation where this happens would be if you press and hold the end waypoint. You can always long press near a point along the track to resume from there
In short:
- route calculation always has a degree of freedom to calculate the route between individual waypoints. Due to traffic you can indeed get a different route than plannend.
- track navigation is identical to planned always as we follow the breadcrumb (disclaimer for offroad waypoints). The shown waypoints are there for visual information but do not influence the calculation. You can use them to skip a section / resume from a point. But even without displaying them that would be possible as you can long press anywhere near the line.
In both situations, viapoints are never skipped / missed
-
@Marinus-van-Deudekom that’s where the fun part starts
(and why it has been quite some work).
Under the hood we use a lot of internal stops along the track to prevent you ever being sent straight to the endIf you have 2 viapoints (start & finish) you won’t ever be sent straight to the end. The only situation where this happens would be if you press and hold the end waypoint. You can always long press near a point along the track to resume from there
In short:
- route calculation always has a degree of freedom to calculate the route between individual waypoints. Due to traffic you can indeed get a different route than plannend.
- track navigation is identical to planned always as we follow the breadcrumb (disclaimer for offroad waypoints). The shown waypoints are there for visual information but do not influence the calculation. You can use them to skip a section / resume from a point. But even without displaying them that would be possible as you can long press anywhere near the line.
In both situations, viapoints are never skipped / missed
@Corjan-Meijerink This is all great information that helps us understand exactly what to expect. Can I assume that track navigation (created as a route with shaping points) will not suffer with the problem where audio instructions are not read aloud because a route point is positioned before a turn?
-
@Marinus-van-Deudekom that’s where the fun part starts
(and why it has been quite some work).
Under the hood we use a lot of internal stops along the track to prevent you ever being sent straight to the endIf you have 2 viapoints (start & finish) you won’t ever be sent straight to the end. The only situation where this happens would be if you press and hold the end waypoint. You can always long press near a point along the track to resume from there
In short:
- route calculation always has a degree of freedom to calculate the route between individual waypoints. Due to traffic you can indeed get a different route than plannend.
- track navigation is identical to planned always as we follow the breadcrumb (disclaimer for offroad waypoints). The shown waypoints are there for visual information but do not influence the calculation. You can use them to skip a section / resume from a point. But even without displaying them that would be possible as you can long press anywhere near the line.
In both situations, viapoints are never skipped / missed
@Corjan-Meijerink Hi Corjan. As far as the MRA next app I'm with you all the way. My question was related to the external devices such as the Garmin Zumo's. How do those devices react on the track beein send by for instance the Drive app. Do the Zumo's see the track of the track with all of the fine extra's you've added.
Honda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT (almost in the cupboard)
Samsung S20FE mounted on a Quadlock and using Android Auto in my car -
@Marinus-van-Deudekom that’s where the fun part starts
(and why it has been quite some work).
Under the hood we use a lot of internal stops along the track to prevent you ever being sent straight to the endIf you have 2 viapoints (start & finish) you won’t ever be sent straight to the end. The only situation where this happens would be if you press and hold the end waypoint. You can always long press near a point along the track to resume from there
In short:
- route calculation always has a degree of freedom to calculate the route between individual waypoints. Due to traffic you can indeed get a different route than plannend.
- track navigation is identical to planned always as we follow the breadcrumb (disclaimer for offroad waypoints). The shown waypoints are there for visual information but do not influence the calculation. You can use them to skip a section / resume from a point. But even without displaying them that would be possible as you can long press anywhere near the line.
In both situations, viapoints are never skipped / missed
Hey Corjan, that's exactly what I've always missed personally, and the way it looks and apparently behaves, this also applies to this button 1./ 2. /3. / 4./ in the picture.
Thank you very much for that
-
@Marinus-van-Deudekom that’s where the fun part starts
(and why it has been quite some work).
Under the hood we use a lot of internal stops along the track to prevent you ever being sent straight to the endIf you have 2 viapoints (start & finish) you won’t ever be sent straight to the end. The only situation where this happens would be if you press and hold the end waypoint. You can always long press near a point along the track to resume from there
In short:
- route calculation always has a degree of freedom to calculate the route between individual waypoints. Due to traffic you can indeed get a different route than plannend.
- track navigation is identical to planned always as we follow the breadcrumb (disclaimer for offroad waypoints). The shown waypoints are there for visual information but do not influence the calculation. You can use them to skip a section / resume from a point. But even without displaying them that would be possible as you can long press anywhere near the line.
In both situations, viapoints are never skipped / missed
@Corjan-Meijerink Great work and I am really liking the options. One quick query for when navigating a route as a track, how would a road closure be handled? Would the app route around or would the rider have to take a detour and be directed back and, in this case, would the new directions be to beyond the known closure? Understand that the app can only deal with promulgated and known closures.
-
@Corjan-Meijerink Hi Corjan. As far as the MRA next app I'm with you all the way. My question was related to the external devices such as the Garmin Zumo's. How do those devices react on the track beein send by for instance the Drive app. Do the Zumo's see the track of the track with all of the fine extra's you've added.
@Marinus-van-Deudekom said in Updated beta! 4.3.4 (372):
My question was related to the external devices such as the Garmin Zumo's.
The change in navigating a route as a track is entirely implemented in the navigation app. Nothing changed in regard to a GPX export, and therefore nothing will change on your Zumo.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Marinus-van-Deudekom said in Updated beta! 4.3.4 (372):
My question was related to the external devices such as the Garmin Zumo's.
The change in navigating a route as a track is entirely implemented in the navigation app. Nothing changed in regard to a GPX export, and therefore nothing will change on your Zumo.
@Con-Hennekens That's indeed what I already thought so I will keep exporting the route to my Zumo and leave the track where it is
-
@Marinus-van-Deudekom that’s where the fun part starts
(and why it has been quite some work).
Under the hood we use a lot of internal stops along the track to prevent you ever being sent straight to the endIf you have 2 viapoints (start & finish) you won’t ever be sent straight to the end. The only situation where this happens would be if you press and hold the end waypoint. You can always long press near a point along the track to resume from there
In short:
- route calculation always has a degree of freedom to calculate the route between individual waypoints. Due to traffic you can indeed get a different route than plannend.
- track navigation is identical to planned always as we follow the breadcrumb (disclaimer for offroad waypoints). The shown waypoints are there for visual information but do not influence the calculation. You can use them to skip a section / resume from a point. But even without displaying them that would be possible as you can long press anywhere near the line.
In both situations, viapoints are never skipped / missed
@Corjan-Meijerink would be possible to have in track navigation more visible info if we are currently on the (planned) track or not? There is a line along the route but quite weakly visible. Maybe some color change od the arrow would be good idea, what do you think?
-
@Corjan-Meijerink
I planned a test ride with some of my favourite parts of mid wales in order to test version 4.3.4 - 272 properly on a long route with navigation of the route to be by track with only ‘vias’ showing - display of the navigation was through CarPlay.First issue was at the start as the app kept saying, “Reached Waypoint 40” (the end) and then ended the navigation! I had to ride the bike nearer towards Waypoint 1 and skip to Waypoint 2 for navigation of the track to resume correctly.
All good and no problems on the way to Waypoint 7 for a disconnect and coffee break. On reconnect and recommencing navigation after the ‘stop’, I followed the app to see where it would take me and I followed the instructions to Waypoint 25 - the next via on what appeared to be the fastest route and not the desired track. The routetrack should have taken on a southern loop (white):
Before stopping at Waypoint 25, I took a SE direction to backtrack the intended track to see what would happen. I was quickly presented with ‘recalculating’ as mobile signals for both data plans on my iPhone dropped but the app did not switch to ‘offline’ for the next 20 mins and the app appeared to have frozen when I stopped at Waypoint 25.
The app had to be closed on the iPhone to resume the track recording but the app would not recalculate the route even though I had signal with both sims. A switch to offline also did not resolve the issue despite having the correct maps loaded for offline use. A soft reset of the iPhone did not resolve the problem either.
Abandoning the route and setting a ‘course for home’ was met with repeated ‘no route found’ for offline and online. Manually selecting the destination from the map also did not help.
Not sure what was happening but I will raise a support ticket with app logs attached for you @Corjan-Meijerink .
Interesting trip.
Kind Regards. Help where I can.
Ducati Multistrada V4 Rally
iPhone 15 Pro
Chigee AIO-5 Play
Google Pixel 6 Pro - mounted on SP Connect Plus
Ex Garmin XT2 and XT1 as well as Ex TomTom Rider User -
Hi, I used the new version today for a 2-hour trip as A to B route on iOS CarPlay and everything went very well. Traffic jam and roadworks very announced and a shorter way during traffic was recommended. All were displayed on the car screen. The App is becoming better and better.
Hardware
iPhone 12 pro (iOS 17.0.2)
Oukitel RT3 (Andr. 12)
Samsung Galaxy XCover 4 (Andr. 9 Pie)
Wireless CarPlay mit (Elebest C650)
Wired CarPlay (SEAT Arona - 2021)
For more information, click here -
Hi, I would like to use Track Navigation:
To do this, I take a route that I have created in advance in the MRA Webplanner. In the MRA Next settings, I set the “Navigate routes as tracks” switch to ON. Is that all or do I need to adjust other things?Peter
-
Hi, I would like to use Track Navigation:
To do this, I take a route that I have created in advance in the MRA Webplanner. In the MRA Next settings, I set the “Navigate routes as tracks” switch to ON. Is that all or do I need to adjust other things?Peter
@Mopetenpit, that's all indeed. You do have choice however to enable the visibility (ON) of all waypoints, or only the VIA points (OFF) on your track. The preferred method of track-navigation is still online. Of course only really relevant for the moments when recalculations occur (which you can disable now too).
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
Hi, I used the new version today for a 2-hour trip as A to B route on iOS CarPlay and everything went very well. Traffic jam and roadworks very announced and a shorter way during traffic was recommended. All were displayed on the car screen. The App is becoming better and better.
@Jörgen Happy to read that you had a positive experience
-
@Corjan-Meijerink
I planned a test ride with some of my favourite parts of mid wales in order to test version 4.3.4 - 272 properly on a long route with navigation of the route to be by track with only ‘vias’ showing - display of the navigation was through CarPlay.First issue was at the start as the app kept saying, “Reached Waypoint 40” (the end) and then ended the navigation! I had to ride the bike nearer towards Waypoint 1 and skip to Waypoint 2 for navigation of the track to resume correctly.
All good and no problems on the way to Waypoint 7 for a disconnect and coffee break. On reconnect and recommencing navigation after the ‘stop’, I followed the app to see where it would take me and I followed the instructions to Waypoint 25 - the next via on what appeared to be the fastest route and not the desired track. The routetrack should have taken on a southern loop (white):
Before stopping at Waypoint 25, I took a SE direction to backtrack the intended track to see what would happen. I was quickly presented with ‘recalculating’ as mobile signals for both data plans on my iPhone dropped but the app did not switch to ‘offline’ for the next 20 mins and the app appeared to have frozen when I stopped at Waypoint 25.
The app had to be closed on the iPhone to resume the track recording but the app would not recalculate the route even though I had signal with both sims. A switch to offline also did not resolve the issue despite having the correct maps loaded for offline use. A soft reset of the iPhone did not resolve the problem either.
Abandoning the route and setting a ‘course for home’ was met with repeated ‘no route found’ for offline and online. Manually selecting the destination from the map also did not help.
Not sure what was happening but I will raise a support ticket with app logs attached for you @Corjan-Meijerink .
Interesting trip.
@Dave-J-0 Thanks so much for the elaborate feedback
I've been working on fixing the mentioned issues and with joy can report the following changes that will be included in the next beta update / public release:
- Fixed an issue with route not recalculating after deviating (when recalculations are enabled)
- Improved determining the nearest marker to start route from (your route specifically had a specific case where the finish was closer than your start marker but the one before the finish marker was extremely far away. This caused your route to start at the finish).
- Improve determining next waypoint when deviating from the route.
- Improved route generator fallback option when not having internet / online route calculation failed (your last issue).
Thanks again for the nice feedback. I believe all the encountered issues are resolved now in upcoming version 374
-
@Mopetenpit, that's all indeed. You do have choice however to enable the visibility (ON) of all waypoints, or only the VIA points (OFF) on your track. The preferred method of track-navigation is still online. Of course only really relevant for the moments when recalculations occur (which you can disable now too).
@Con-Hennekens Thank you very much for your explanations! Together with the new version (372) it now works as expected.
-
@Con-Hennekens Thank you very much for your explanations! Together with the new version (372) it now works as expected.
Of course I mean version 374!
-
This post is deleted!
-
TestFlight says 375, Correct?
