Track remaining time inconsistent (still)

Ulrich Kiermayr shared this problem 2 months ago
Solved

Hi,

The Issue is still there in some cases.

https://help.locusmap.eu/topic/32269-track-remaining-time-inconsistent

lG uk

Replies (2)

photo
1

Hi Ulrich,

is the issue the same as in the linked topic? In what "some cases" in particular does the issue occur, could you describe them in detail? Is the navigated route planned in the app or on the web?

photo
1

Hi,

Attached is a recent screenshot. I had the issue for a long time and just did not come around to re-report it (and I assumed, it is not yet fixed since there was no more activity on the original posting).

What I do/know:

  • Planning is always done in the App
  • I mostly use "Plan Route to" after selecting my destination
  • Just noticable if the destination is also a waypoint (the blue square one).
  • I use guidance mode
  • I did not yet see a pattern (but I did not really to find one).
  • It does not occur before I start (e.g. in the beginning of guidance).
  • Track recording is also used.
  • I use offline LoRouter
  • In the screenshot there was also a slight difference in Distance despite the fact, that the waypoint is the end of the track (and the distance to the waypoint is *longer* than the distance to the track destination).

I can try to pay more attention during the next rides.

lG uk

Screenshot: 8d8024a44936023f306637b3e9a9343e

photo
photo
1

I'm not able to replicate the problem:

- I tap a LoPoint > Plan route to > set my location as the start > save the route

- I start navigation along the route

- the time to target is the same as the time to via point on the route end

- I start moving along the route - the time to target is still the same as the time to via point

Is there anything I'm missing?

photo
1

That is kind of my problem too. It does not happen at every time. In principle I do the same.


To me it seems, that it only happens in longer tracks. But I plan a tour this weekend. There I can try to replicate it (step by step).


Greetings

photo
1

Hi,


In the latest beta I'm unable to reproduce the problem. So it seems that the latest changes fixed the issue.


Thanks for looking and sorry for the false alarm

Ulrich

photo
Leave a Comment
 
Attach a file