When I have auto-recalc ON and use BRouter (offline) (but it's the same with GraphHopper or MapQuest etc)
I select a point and Navigate to, the route is calculated... and hear the 'Let's Go'
but then the sequenc eof events is:
1. 100-200m later, the ? question mark comes up and locus beeps.
2. Several seconds later, the voice says "track has been re-calculated" and gives me a nav instruction.
3. 100-200m later, the ? question mark comes up and locus beeps...
this repeats all the way along the track...
What is causing this? How do I let it just sit on the track (unless I move off it). Is there a setting to avoid this?
It doesn't matter if I choose point of route priority - it's the same result.
If I set auto-re-calc to OFF, then the ? question mark comes up and never gets refreshed.
Alan
I have locus 3.28.1
So I turn Strict OFF? in the Advanced settings for both Guidance and Navigation?
Do not use them in both?
How does this problem manifest itself? (with the strict stting ON)
Where can I see the list of general advices?
OK - further testing and I can at least confirm that switching strict OFF makes a big difference in functionality. I can start to rely on Locus again. Thanks
Navigation on Tracks works
Navigation on Destination Points works
Guidance on tracks works - deviation from track alerts work
No undue re-calculation delay
POI alerts work
Alan