Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - CabrioTourer

Pages: [1] 2
Troubles & Questions / Re: Problems with navigating a route
« on: July 20, 2019, 11:28:08 »
Just a (hopefully) small improvement idea.

Right now the no go area after two recalculation is set behind you.
Sometimes there is just in front of you an alternative way back to the point you missed. This means the goal of the no go area doesn't twork in this scenario.
Maybe it's better to place the no go area to the point you missed instead or in addition.

This should solve the problem.

I vote for an option when the no go area is set. In my case (car) I woul set it to zero. Means don't guide me back from the beginning.

Nevertheless thanks for the work you did in this area. Very welcome improvement.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 04, 2019, 20:39:43 »
Can't save tracks in route planner with 38.7.3
Locus restarts or simply close route planner when pressing save. No Save dialog shown.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 20, 2019, 10:24:40 »
I restored 3.37.2. Looks much better.
Something is wrong in new route recalculation in 3.38 I guess.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 20, 2019, 10:04:06 »
Something happens and makes Locus go crazy for me.
I have a route with starting point near by my position and end point 10km away.
When starting Navigation it starts recalculation and recalculates to my end point. It doesn't matter which way of Navigation start I use and it happens even with other new planned route.
Looks Locus is more or less unusable for me.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 03, 2019, 19:54:40 »
I think this isn't mention in changelog for 38.3.1. Redraw of map after zoom change / movement is much faster. Great

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 31, 2019, 20:12:07 »
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.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 27, 2019, 21:53:08 »
Where I can get 38.0 ?
Have to guide a larger group this Thursday.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 27, 2019, 21:51:31 »
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.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 27, 2019, 21:45:06 »
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

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 23, 2019, 16:20:50 »
With 3.38 Free I lost all folders for tracks and points.
If I use old released 3.37 pro the folders are there.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 15, 2019, 22:06:39 »
Sorry for the late answer. I'm quite busy with my buisness.

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.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 13, 2019, 18:42:35 »
Route recalculation in V13
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.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 13, 2019, 13:53:24 »
I'm using V4ML maps and Elevate theme in V12 beta without any crash.

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

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 12, 2019, 17:23:29 »
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.
Much (!) better than before but please consider option to stop U-turn navigation after 2-3 recalculations. Then the new algo will be perfect.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 04, 2019, 21:51:42 »
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.

Pages: [1] 2