@zossebartI had also Z1C ... it was the best phone I ever had. By my stupidity I broke it maybe a year ago, anyway it is my personal interest to keep Locus Map working on this device as long as possible

.
@CabrioTourerreally no need to sorry

.
The App doesn't know for which reason the route was left. For this I brought up the 2 recalculation idea.
First, Locus can assume it's just a simple missed navigation etc.
After this 2 recalcs the App should assume the route can't follow this way and should find another way which means it's fine to skip a part of the route.
This is partially implemented. After two "failed" recalculations (user ignored new route), app place temporary no-go place behind the user to force routing engine to compute forward and not backward. Anyway, this logic does not affect "target" where recalculation is done and this is what we talk about here.
I still do not see a simple solution. I perfectly understand your reasons anyway as you wrote: "The App doesn't know for which reason the route was left.". In this case (your route) it is almost circular route which complicates the situation. App has absolutely no idea if you are off route because you want to skip the whole circle or you just pick some detour because of complications on road. In rare cases when this happens, exists in the navigation menu button "Nearest point" that should fix this situation.
It is not automatic, which means it is not an ideal solution.
I'll keep thinking about it and collecting ideas. For now, I really think that changes from last weeks are quite big and this not-so-often use case may be solved in another iteration.
@T-mounderstand and thanks for screenshots.
Hope you got the point of these changes in app. If now, simply: app try to unite visibility of content of all maps. Compare vector maps and some online (raster) in Pro and in Beta. Mainly check visible texts. In Beta, there should be very similar in terms of size. On modern devices (with huge DPI), all raster maps are useless in LM Pro.
You, as well as almost all other users, had to solve this by "Map resolution" option. This unfortunately scaled also vector maps = problem.
So generally, "Map resolution" should be no longer important settings. It may be left on default 100% except for cases, you had worst eyes and really need a larger map.
@Andrew Heardno problem. I found an issue in pinch zoom when work with world map = fixed. On your screenshot was higher zoom so it won't be this issue, but I'll keep watching it carefully, thanks.
@slarti76something close to what you want is planned. Anyway, some other priorities firstly
