Messages

I think this isn't mention in changelog for 38.3.1. Redraw of map after zoom change / movement is much faster. Great

Regarding route planner. Sometimes it losts all (or a part) of shaping points. Can't find a way to reproduce.

The reason for this post is a different one.
I have a preset with hold center disabled for planning and one with hold center active for Navigation.
Today, in the middle of navigation the hold center doesn't work anymore. It's a known issue for a long time and after switching presets (means hold center on/off) multiple times it works again in the past.Today it wasn't possible to make it work again. I tried it a long time. I generated a trace log. Maybe this helps.

In the end the only way to fix this was to stop Locus App and start again.

Where I can get 38.0 ?
Have to guide a larger group this Thursday.

I had the problem with instant crash too, but I following fixed it:
Rename the "locus"-folder on sd-card. Start locus. Select "ok" for a new Locus-folder. Exit Locus and delete the new locus-folder. Rename the old Locus folder back to "Locus".
I have no idea why, but it worked for me.

Works for me UNTIL I select V4 ML map. Now it crashes again.

Got 38.1 via playstore (pro)
Now App crashes after (I guess 100% initalisation). Maybe earlier. Even the Crash dialog window closed.

Same for Free

With 3.38 Free I lost all folders for tracks and points.
If I use old released 3.37 pro the folders are there.

[@CabrioTourer]

@menion
Sorry for the late answer. I'm quite busy with my buisness.

@CabrioTourer
What is the purpose of this your trip?

Just fun.
In case I travel from A to B I don't use Locus. I use Google Maps.

In this case, Locus Map correctly tries to get you back on route, isn't it?

I think your Definition of route priority is too strict.  Yes in principle the idea of the planned route is to touch every route point when you select route priority.
But there are two different reasons why to leave the planned route. First you simply missed the navigation or you took the wrong street if there are two close together. In this case your approach is right. Redirect will be short and turn you back to the missed point is totaly fine.
The second reason is the fact that the route can't be followed. Let's say a
roadwork or the road is closed etc. In this case guiding back to the missed point doesn't help.
Then the alternativ route might be longer because it simply depends on the sreets which are available. At least for me (and I think for the majority of users) the recalculation should bring you to a useful point of the track. "Useful" in terms of easy reachable.
After back on track it should continue the route and don"t send you back to the (more or less long) part of the route you missed. In very common cases this will be a oneway because of the roadwork/road closed etc.

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.

Here is a general problem that you skipped quite a long route segment.

That's not up to me. This depends on the available streets. As I wrote some days ago. "long" in city environment is a different thing as in rural area. In first case it might be 2 km. In the second case it's 10-20 km or whatever.
I think the distance doesn't matter. The number of streets connected to the part which follows the missed point is the similarity.

It's totaly fine to wait for the good solution of recalculation logic.
The logic is the same for 1-2 ywars now. No problem to wait a bit. Main point is to do it and do it good.

Route recalculation in V13
@menion
After 2 recalculations back stop back Navigation doesn't work if there is another way in forward direction where the missed point can be reached.
Remeber my first example. Attached is the route after 2 recalculations.
I guess you avoid the actual position or the position where last recalculation based on..You shoud avoid the first  point where the route was lost.

I'm using V4ML maps and Elevate theme in V12 beta without any crash.

By the way. Theme Support in Presets (V4ML, Elevate) works ! 

Here no crashes on Android V9 with Locus V12.
Very short check of new route priority with Simulation. No more problems wit longer abbreviation/detour. If near by back to track recalculation works fine.
For my liking still to often U turn recalculation.
Get perfect recalculation with manual set of no-go area to avoid U turn.
@menion
Much (!) better than before but please consider option to stop U-turn navigation after 2-3 recalculations. Then the new algo will be perfect.

I don't get the point why to use x trackpoints in a row. Doesn't matter what x is. Only few of them are important. For all others you must touch one of the important ones to reach.
I mean for a lot of activities you are using streets, ways etc. So all trackpoints which doesnt touch another street/way are useless to check.
But don't know if it's easy to select.

For a starting point.
A recalculation which send me back has no real information. It's always the case that a return to the missing point will bring you back on track.
For the first recalculation it might be ok to show the point you missed (?). But maybe it's a good start to assume a "no go area" behind for the following recalculations.

If user didn't follow the advice for 30 sec or over a minute. The user might have a reason to do so.The following recalculation can respect that.

As allows just an idea.

Just a quick comment.
I'm using Locus for two years now and my example shows nothing special. This is what happened quite often to me.

Just for completeness, they do not count as points in context of the point priority recalculation

This is what I thought. I just asked to be sure because 100 trackpoints isn't much for activities like car and even not much for bike in rural area.

Thanks for "shaping point" correction.

@Menion
You talk about trackpoints, not sharp/via points, right.
Then it's a pretty short way for a lot of activities. That's for sure a problem.

Solution might be not to choose 100 in a row but every x trackpoint where x depends on the activity (or actual speed?)

If this does not work for activities which needs defined ways (street etc) then selecting trackpoint located on crosses etc might be the solution.

Just an idea.

@Menion
To focus on new map core and finalize navigation later is fine.
Just that you are aware of some problems which might not be directly related to navigation logic I want to show you some things upfront.

Simulation in V10 is much slower than V9.
Funny thing: Airplane is slower than car in V10. Airplane means it counts meter by meter. That's slow
I checked recalculation in Simulation in V9 and V10. In V10 it's detect "back on track" but pretty late. V9 it doesnt detect recalculations before back on track isn't improved.

Simulation might not show what happens on the street.
I tried the tour I did on Tuesday with Simulation multiple times. The results are sometimes different. My simulation started more or less same as Tuesday but later it changed and I see something different.
I uploaded the settings, planned route, simulation route and video which shows the issue here. All from V9 because simulation in V10 are too slow.

https://app.box.com/s/xfaxre1nil8n3ljv07az9xtab2nmtpf2

Then a question.
Which parameter influences when second, third etc. recalculation starts ?
The first recalculation is influenced by settings but all other seems to be random.
Sometimes after 300m, sometimes 600m etc.
Can't find any settings to change the time/distance. Tried all settings (I think) in navigation and guidance.
I'm asking because the place where recalculation happens influences the result of recalculation.
Without able to influence recalculation time Simulation might show other things than on street.

Again : it' s fine to focus on new map core first. Just that you are aware of some issues any maybe my sample might be good for testing.

[@tramp20]

@tramp20

Thanks also for crash logs. Unfortunately, I'm unable to perfectly find the reason of this issue but seems to be somehow connected to some active dashboard. Is this possible? If so, may you share this dashboard with me as well? Dashboard files are in Locus/data/dashboard directory. Thank you!

Method for navigation simulation

With the Beta version, there is a nice method of how to test the navigation system.

dashboard was active and same as in release. Its appended.

Nrw simulation :
Wooowwww that's great.