[Unified Map]: Individual route with "Set route start as target" behaves erratic

[MagpieFourtyTwo]

Describe your problem!

With Unified Map, an individual route will not just follow the caches in the routing list, but always seems to prepend the end point to the route. In any case, the route is always drawn as a complete loop, as soon as we start to move ...

How to reproduce?

1. Scenario:
   A round trip through the woods with the parking lot at the end.
   Set route start as target is activated.
   Some of the caches are already visited and logged (offline).
2. After visiting and logging the next cache, the visited cache is removed from the route and the target is automatically set to the next one; the rest of the route is properly displayed (thus everything fine and as expected up to this point)
3. but as soon as I start to move (resp. as soon as c:geo thinks it should re-calculate the route) ...

Actual result after these steps?

4. ... the route will be drawn as a complete circle - looks as if the Parking lot has been prepended to the route.
5. Disabling visibility of the route and enabling it again fixes the problem, the route will then be displayed correct again.
   At least until logging the next cache and moving on - then the route is a complete circle again.

Expected result after these steps?

The route should just be displayed as it is defined.

Reproducible

Yes

c:geo Version

2024.04.13-NB-4ae1565

System information

No response

Additional Information

No response

[ztNFny]

#15412

[MagpieFourtyTwo]

Yep, maybe a duplicate, although the effects over here are slightly different: My route list was completely fine all the time, i. e. no doubled waypoints, no doubled length plus the problem did not "solve" itself after a few seconds, it just remained till I logged the next cache. Or until I simply disabled and enabled visibility again. And the latter was the only thing I had to do to "repair" the faulty state.

BTW: It's most definitely a Unified Map problem, because after three quarters of the round I was so annoyed by this misbehavior that I finally turned UM off - and after that the problem no longer occurred.

If you nevertheless think this is the same problem, feel free to move the observations over there and close this one.

[moving-bits]

have not been able yet to reproduce this in the emulator (which prevents fixing it for me). Anyone else?