Navigation route sometimes rendered behind other objects or inconsistently

Q: Is the example with the Icons versus navtrack similar ? I did not report as I mostly use map rotation, so is no issue, just is +/- strange. I notice this mainly while taking a nice screenshot only.

The 3 screen captures were all from the same track while in navigation mode.

Hello Willy, no no this is different story. In this case, order how items are draw on screen is little bit different in case of rotation. And in this case, track is drawn little bit later then points. Technical unsolved complications ...

Andrew,

May I ask how did you test ? Real drive or Virtual by moving center position ?

Settings-> Navigation -> Advanced Settings -> Strict Route following: SET !

Out and Return sections: Correct Navigation by Locus ! Must Set Strict !

http://www.locusmap.eu/another-playing-with-locus-navigation-settings/

See 4. Strict navigation with auto recalculation

https://www.youtube.com/watch?v=PVivEWy3TpE

Real bike ride.

Strict route following:UNSET.

Navigation works fine for out & return. That wasn't my point.

I am indicating the rendering of the navigation line (thick in front of current position/ thin behind) was thin instead of thick.

Hello Andrew, Willy,

unfortunately no matter what I do, I'm unable to simulate this problem anymore.

Is this happen to you with all tracks? Any idea what trigger this problem, since which moment? Thanks

Hi Menion. I wondered in this specific example whether the out/ return route may be a factor? It is certainly not with all tracks. I will probably ride this route in next few days so will check more closely when the rendering issue begins. I could also try to simulate. Leave it with me ;-)

Hi @Menion. I can easily reproduce incorrect rendering of navigation track (thick/ thin) with the attached TCX route. In this example I am sure it is related to route being out-and-back along same road.

Screen cap below 15.5km remaining: position is nearing U-turn. All thick nav-track is correct:

Screen cap below 15.0km remaining: position is just after U-turn. Nav-track between U-turn and big blue arrow should be thin:

Screen cap below 11.7km remaining: near to strange thin/ thick nav-track. Nav-track above/ right of big blue arrow should be thin, not thick. And nav-track below/ left of arrow should be thick.

Screen cap below 11.4km remaining: nav-track above big blue arrow is correct (maybe luck because now past mystery point of last screen cap), but nav-track below arrow should be thick:

Virtually I can't reproduce that behaviour. What a strange ugly generated navtrack.

Total distance: 16,13 km Traveltime: 313h55m13s ! Sloooow... ...pfff

That tcx course includes 20 Coursepoints, but 6 of them are identical.

In the example pictures (by gpx) around the return point: 15,5 km and 15 km to go ?

good observation - track is 16km, but near 8km U-turn Locus displays 15km to go

Hello Andrew, please export track as GPX, not TCX, there seems to be lost some parameters (like u-turn) and I'm unable to simulate your problem, unfortunately. Thanks

Thanks Menion. GPX in V1.1 format is attached. I normally only export as V1.0 to retain maximum future compatibility. I did another test of route yesterday on bike, this time not virtual/ simulated, and noticed even more unusual double change of nav-track line thickness:

Ah perfect, this helps, thanks! Track was separated into two segments and Locus was not able to correctly compute parts fat/slim.

Was that my fault? To create out/return route I merged out/return tracks, each with own turn instructions. Maybe I forgot to merge without gaps? Or should Locus handle track (route) composed of multiple segments better?

Would that also explain wrong Distance to target below? Actual distance is ~4km, not 12km.

And here 7.2km to target but map shows red flag and ruler, only about 200m to target.

It's definitely not your issue! It may happen (gaps in track), so Locus should handle it better of course. Distances are anyway interesting. It has nothing to do with how track is drawn, so I'll rather check these as well, thanks!

EDIT: hmm I'm unable to simulate it. Maybe it's already solved? :), you will see in next version ...

I see 2 segments but the navigation waypoints seem to be distributed "in the wild" ? Looks a very complicated, failure success inbuilt, system to me. If nav instructions where combined direct into track points even multiple track merges without any loss of attached info, would be as simple as a piece of cake. Or cut , split, merge track operations without any extra complication caused by associated waypoints. Not ?

3000km in 60 days, so not too much distance each day. Plenty of days off the bike for rest and avoiding bad weather. While traveling Locus is like my totally dependable best friend, always there when I need him for help. Hard to explain.

Planning each days route to minimize steep hills or unsealed surface is always problematic. My dream is Locus Pro 3D. Surely v3?

For sure leave it, I just wanted to let you know it was rare. Could there be a byte or two corrupted in the 800MB Italy map file maybe? I guess unlikely because a restart always fixed the problem.

Ah 60 days, right ... nice :).

It won't be an issue in map as it has nothing to do with this. More probably some my algorithm to compute in which part of track are you currently. I just do not understand that it appear so rare and is almost impossible to simulate. Never mind ...

And 3D ... I was working on it maybe an week or two year back, but it's too much on me now. Anyway some options are coming so I definitely do not say "never".

Menion - I have again observed this bug as discussed 3 months & longer ago where LoMap map is no longer displayed. It happened on two recent days, only when navigation enabled, only after many hours of navigation. This time with Australia>Tasmania map, previous Italy, so I believe nothing to do with actual map. I was not able to do any good testing because riding in rain and/or with other people. Observe POI and track are displayed but no roads. I was using Voluntary theme not a Locus theme and didn't have time to switch/ test.

Navigation stopped few minutes later:

Hello Andrew,

sorry to hear that problem with visibility of map appear again in latest version. Unfortunately I'm sure you will understand, that without ability to simulate this problem (which is almost impossible here), it is also almost impossible to fix it. I'll be watching it ... thanks

It's no problem for me but thought I'd report it. I don't usually use navigation for local rides but will see whether I can characterize the problem better on future longer rides. Just the fact no one else has reported anything similar is strange in itself; not sure why it would only happen to me.

I believe you are not the only one with this problem. Few people already reported similar problems on forum as I remember. Over all these years, I wrote many various optimizations how to save some CPU power here and there during map rendering and some may be in conflict, some may not work on 100% and this is result. Solution? Find exact steps to reproduce it or completely rewrite it from scratch. First one is a problem and second ... ah, not yet :). Thanks