I don't know if this is a BRouter problem or a Locus problem, but it occurred in real life using the latest beta version of Locus. I've boiled it down to a particular junction for this example but it's not the only time it happened.Navigating from N 32.38866, W 03.90318 to N 52.38831, W 03.90242 using BRouter offline set for Locus profile Fast Eco I got an instruction to "turn around" instead of "turn left". The map show a "turn left" symbol on the route, but the itinerary shows a U-turn.

@jonny.bluehmm, it depends on what you clicked. If on the middle button, it says to Locus: "insert this point to the nearest place in planned route as possible". In your case, it is inserted into previous points 3 and 5. So you probably really get a route from 3 to 4 and almost back to 5.Try to use the last third button to add cache to the route. This says "insert this point to the end of the planned route".

@Žajdlík Josefhmm, seems that Strava use exactly same old system that Locus Map used > so it computes directly from coordinates of current and next trackpoint. Not an ideal solution I think. I've reverted this part of the code to keep it as is anyway expect that I'll most probably change it in the future to the result very similar to current Beta, thanks (based on a floting average from previous & next trackpoint)

@erfianything new compares to Pro version?And too high ... heh ... you may check five other apps or web pages to find that every compute values differently. I believe that values in Locus Map should be somewhere in the middle ... Also depends if you use Heart rate monitor or not ...

No, I do not use a heart rate monitor. To Pro version are only small differences. In my opinion the difference between walking and hiking is too big. Maybe you are right and I am wrong. Look at yourself, is this difference realistic?

Beta RC, autozoom lock, V3 map. Button at bottom right. The autozoom shows 700 m, manually adjusts to 100 m and locks the lock. After 10 seconds, the map returns to 700 m. The cursor and the trip line flash. I think the chateau worked with scales of 11, 12, and so on. The scales are not used now, so the lock should be rebuilt to lock the meters.

@erfithanks, you are correct. "Walking" was dependent on speed, but "Hiking" no. It was hardcoded to a single value per km. I've improved it and based on information I've found, changes are: "hiking" will use same values for computing of energy consumption like "walking" + 15%, which should be equal to carry 5kg backpack.

@Žajdlík Josefhmm. Even with Czech description, I do not exactly understand where is the problem. Should be possible to create a short video of this problem? Thank you!

These were quite long two months. It is probably for the first time, I publish a version after such a long time since the previous release. Last two days I spend by fixing various problems we found and just now, the new version was published on Google Play.

We have an option to publish version only for certain part of users (probably random selection). So today, it will be only for 10% of users. If there won't be any unsolvable problem, I'll enable version for all users tomorrow. Thanks for understaning.

And mainly thanks for the help. Update of map system was a big task for me and I'm really glad, version with this change is out. Now we can fine-tune it .