V6 - Track Navigation

[Corjan Meijerink]

I’ll consider a video but honestly, the app just handles it for you. Much better than before. Day and night difference

[BMcG]

@Corjan-Meijerink I appreciate your confidence in the new path calculation
for me I like to understand how these things work as I have low, very low confidence in how Here does its path calculations

leading groups, if it goes wrong it is me that has got it wrong, nobody is going to accept if I blame MRA or Here
a bit of understanding helps me to know when/where it might go wrong & I can hopefully work around it

[Stevedo 6 0]

@BMcG said:

@Corjan-Meijerink I understand how some could be confused by the differences between routes & tracks but this is a major change for those of us who trust & navigate by tracks

As I have not seen a discussion or announcement on the deprecation/removal of track navigation (if I missed the discussion please point me too it) I was not sure if track navigation was just omitted in this new version & might reappear in some later version, glad you have cleared that up

I do think that such a huge change in path calculation philosophy should have been communicated to users & that an explanation of exactly how MRA now does it path calculation should be provided
I have heard mention of Here calculations been done in segments but these have been brief snippets of info no detailed explanation, is this related to the new calculation method?

In the past MRA provided what I thought was a terrific & informative video of how track navigation was implemented & improved on in MRA, would it be possible to provide similar explaining the new path calculation method?

Given that V6 has now been released I would fully expect that the documentation has been updated to reflect all the changes.

[Corjan Meijerink]

Our manuals are being finalised by support. Already visible on the beta website to be honest.

However, things like this aren’t in it and won’t ever be in it

[BMcG]

apologies, looking back at my previous post it is not obvious what was happening & what I was attempting to point out to to the uninitiated
to me it was perfectly clear as I understood the issue
what the Here routing is directing is to climb the 2m gravel/sand bank then ride 0.5 miles through the woods
rather than follow the lovely twisty bendy perfectly fine tarmac road
this happens a surprising amount on twisty mountain passes with the Here routing calculator
hence my desire to understand what the new MRA path calculator is actual doing

[Mike Linzey]

@Corjan-Meijerink I used tracks to make sure I was not re-routed if I left the route. Can you assure me that with 6 this will not happen?
Thanks Mike

[Corjan Meijerink]

If that was the reason you used track navigation, you have been disappointed a lot by the previous app
It's much better now.

[John S Parry]

@Corjan-Meijerink said:

If that was the reason you used track navigation, you have been disappointed a lot by the previous app
It's much better now.

I don't know what's happening under the covers, but off-route behavior has significantly improved under V6. In many respects it feels more like riding a track without shaping waypoints tripping over themselves in specific situations.

Honestly, this is the first release where I have some confidence using the app. More testing is needed, but so far, nice job.

[Corjan Meijerink]

That was the mission

[John S Parry]

@Corjan-Meijerink said:

That was the mission

Again, so far, so good.....

Under V6, there appears to be a new Navigation setting called "Automatic recalculations". At least I think it's new, because I don't recall it and I can't find any reference to it in current documentation.

The little info button states that if disabled, the route will not be recalculated when off-route deviation occurs. Subsequently, I will have to manually drive back to my route to proceed. Does that mean that routing automatically starts up again (without any intervention) when I renter the route at a further point?