Guiding problem on "reversed" track???
Preparing our E3 hike I found a lot of track segments in the internet. Some of them had an east-west orientation so I made "reversed direction"copies of them.
Especially these now give me a headache with my usual guiding along a track settings.
I attached a real used file. Activating the guiding is really hit and miss. It takes more time than usual and sometimes it guides me to the start or the end of the track(segment).
Starting the guiding by tapping on the screen is usually unsuccesfull. From the track list has more succes.
Guiding in "reverse" direction (I sometimes walk towards my wife) is never succesfull. Selecting next point or closest point shows a point close by (say at 240 m) in the top bar but then Locus switches within a second to a distant goal close to start or end of track, say 25 km away.
Since I never had problems with guiding on my present Android 7 phone and Locus 3.37.2, could it be these reversed tracks?
When not I will try a downgrade to make this hike a bit easier.
The same question
Hi Henk,
I'm not able to simulate the issue - both guidance and navigation along the route you sent works OK in both directions. Only both processes start after a while because Locus needs to generate voice commands. Aren't there any more settings you didn't mention? Is the route you sent the original "segment" or is this the route created in Locus by merging those segments?
Hi Henk,
I'm not able to simulate the issue - both guidance and navigation along the route you sent works OK in both directions. Only both processes start after a while because Locus needs to generate voice commands. Aren't there any more settings you didn't mention? Is the route you sent the original "segment" or is this the route created in Locus by merging those segments?
Thank you Michal. It was not a merged track but an original one, but I made a copy within Locus with the advanced setting "change track orientation".
The track came from the here attached original file that was split up by Locus upon importing.
I now also tried without the setting "voice commands upon direction change"in guidng but still irrational results. Sometimes it looks like Locus is iterating but stops after five or so calculations.
Well, at least good to know that it is not due to the file.
By the way, my old Moto G wit 3.26.2 and my wife's new Motorola one with also 3.37.2 handles it without problems. GRRRR.
Thank you Michal. It was not a merged track but an original one, but I made a copy within Locus with the advanced setting "change track orientation".
The track came from the here attached original file that was split up by Locus upon importing.
I now also tried without the setting "voice commands upon direction change"in guidng but still irrational results. Sometimes it looks like Locus is iterating but stops after five or so calculations.
Well, at least good to know that it is not due to the file.
By the way, my old Moto G wit 3.26.2 and my wife's new Motorola one with also 3.37.2 handles it without problems. GRRRR.
Hi Henk,
I've done the same you did - made reversed copies of the E-W oriented tracks, tried guidance along with them - no problem in either direction. Did you hide the original tracks after you made copies of them? If not then Locus was probably confused as to what track you want to be guided along - couldn't be this the problem?
Hi Henk,
I've done the same you did - made reversed copies of the E-W oriented tracks, tried guidance along with them - no problem in either direction. Did you hide the original tracks after you made copies of them? If not then Locus was probably confused as to what track you want to be guided along - couldn't be this the problem?
The originals were not on my phone anymore.
The originals were not on my phone anymore.
In this example one (reverse guiding) is good. 54 km distance. The other two 107 km forward are wrong. Going close to the start of the track but not all the way and even crossing the track, see the second screenshot.
In this example one (reverse guiding) is good. 54 km distance. The other two 107 km forward are wrong. Going close to the start of the track but not all the way and even crossing the track, see the second screenshot.
And my present settings
And my present settings
Hi Henk,
I'm sorry but I'm not able to either simulate the problem you described at first and from your last post I don't understand what your point is - the screenshots display guidance to a route from distance of tens or hundreds of kms. Last screenshot shows guiding line going across the route line - obviously it ends on some previous part of the route? Guidance is used in real terrain when you are on the route, not so far away from it. Anyway, I myself can't simulate this issue. Problems that can't be repeated can't be solved - we can't find out what causes them. I do apologize for any inconveniences.
Hi Henk,
I'm sorry but I'm not able to either simulate the problem you described at first and from your last post I don't understand what your point is - the screenshots display guidance to a route from distance of tens or hundreds of kms. Last screenshot shows guiding line going across the route line - obviously it ends on some previous part of the route? Guidance is used in real terrain when you are on the route, not so far away from it. Anyway, I myself can't simulate this issue. Problems that can't be repeated can't be solved - we can't find out what causes them. I do apologize for any inconveniences.
No worries Michael and thanks for your time and feedback. My last comment was just a tryout. Still the result was the same. The guiding does not find the nearest point but even crosses the track to a faraway point. Normally I am on or near the track when I start guiding.
No worries Michael and thanks for your time and feedback. My last comment was just a tryout. Still the result was the same. The guiding does not find the nearest point but even crosses the track to a faraway point. Normally I am on or near the track when I start guiding.
Replies have been locked on this page!