I don't know right now where to put my feedback. It has also something to do withhttp://forum.locusmap.eu/index.php?topic=3318.new;topicseen#new
but I think it fits best here .
Topic: Feedback from testdrive with current version 3.8.0
Track was created within Locus with MapQuest Routing with instructions and a part of the track is overlapping ("8 shape").
1. Adding and deleting of instructions works fine. Great. EDIT: Maybe not, see Video
. Way back should be right (like arrow on the track) not left like spoken and direction arrow. Its exactly this problem (http://forum.locusmap.eu/index.php?topic=4506.msg36315#msg36315
Each trackpoint has an individual number (1, 2, 3 ..........). See picture. Here see point number 34.
Question on that:
Is it assured that a manual instruction is added to the point with the number showed in the popup?
Example: I have a overlapping part of a track. First I follow point 30 to 40 and on the way back I follow the track part in the opposite direction from 80-90. If I choose point 88 and add a instruction there is it assured that I get the instruction only on the way back?
2. Voice instruction timing: I get one at around 200m, 20m and right before the turn. In an older version the one direct before the turn was gone. Now it is back. Was something changed? It is ok for me. Customized amount/distance of instructions would be fine. See http://help.locusmap.eu/topic/navigation-limit-the-total-orders-by-user-editable-navi-order-distances
3. Display activation: Its much better now. I would say for now. Leave it like it is. Further tests will show if we need more optimization
4. strict route navigation: not good, sorry. I will try to explain. I startet the track at the beginning. In the overlapping part on the first way everything works fine. Than I stopped navigation on red dot. On green dot I want to start again and drive back. In this situation Locus does not catch the right "part" of the track (way back part). Even with button "next track point" it always takes points from the "first" way. With "next track point" Locus jumps back the points to the start from the first part of the track. There was no opportunity to tell Locus that I'm on the way back now. What can we do?
How is the start of navigation is initiated? If I click on point 67 on the track to select it and than click start of navigation, I assumed that Locus start from point 67 on. Obviosly it does not.
Over all, I see a clear improvement for biking.