[APP] - version 3.8.x (26.04.2015)

[Menion]

15.05.2015 - Locus 3.8.2.5 - Beta version
 Changes: read news after app starts...

11.05.2015 - Locus 3.8.2.4 - Beta version (not published)
 Changes: read news after app starts...

07.05.2015 - Locus 3.8.2.3 - Beta version
 - working support for Munzee!! (for "capture" is still needed official app)
 - merged "Personal" and "Vector" tab in Map manager
 - some bug-fixes as usually.
 - more after app starts in news...

04.05.2015 - Locus 3.8.2.2 - Beta version

03.05.2015 - Locus 3.8.2.1 - Beta version

26.04.2015 - Locus 3.8.1/3.8.2 - bug-fix versions

24.04.2015 - Locus 3.8.0.1 - beta bug-fix version:
add: highlighting for vector sub-theme in chooser
add: small dialog that display required disk spaces in Locus Store
chg: final version (hope) of coloring of track items (mainly gradient)
chg: invalid vector map now in notification display full uri
chg: improved turning of 'screen on' during guidance/navigation
chg: improved loading images to views and mainly notification in case of loading troubles
chg: system for enabling ANT+ devices and improved it's reconnecting based on suggestion from ANT+ developers
chg: better check if waypoint is attached to track (which results to correct hiding of popup when wpt is removed)
chg: improved sending POST requests in Live tracking
chg: improved inverse of track when creating a track copy
chg: fixed and improved small graphical problems
fix: issue in downloading of custom online maps
fix: fixed import (and matching of waypoint) from TCX file
fix: long click on top left shortcut for active guidance
fix: problems with handling of duplicate geocache waypoints over Live Map
fix: incorrectly drawn track when used navigation on track colored by other then simple color
fix: incorrect values of distance and time to finish during guidance
fix: restore of settings over backup manager
fix: issue with incorrect start of app after update (that caused for example lost "overlay" settings after update)
fix: other small un-important fixes

19.04.2015 - Locus 3.8.0 - new version - changelog

[Christian]

Great! Even the description

[Joachim Buhl]

Hello Menion

1. I updated to Beta 3.8. It's not pro any more. By intent?
2. Adding waypoints manually works great now. Blue dots, voice commands. Nice.
3. The option "number of commands"is the setting when Locus creates commands along a track, right? It has nothing to do with the amount of instructions before a turn, right?
4. Did you optimize screen on/off for this version?
5. There is a question left from the 3.7... thread: what is about the "strict" setting in navigation mode. When is it needed and when is it not needed?

Thanks, great progress.

[Menion]

@Christian: thanks

@Joachim Buhl:
1. it is not Pro? I hope that Locus Pro is still a Pro!!
2. perfect, thanks for test
3. you are right
4. nope, not yet, still same system as in 3.7.1.6
5. yes, too complicated to describe without picture. Anyway I'll try. Guidance automatic system search for nearest points and switch on them - nearest! Navigation system also search for nearest points, but only in same direction. So if you will ride highway in one way and then in second during same route, Locus should never switch to opposite direction, because of difference in azimuth. And this may be useful also in this MTB. Anyway generally, if you want really "Strict", use "Strict" checkbox. I have no better solution for MTB for now ...

[gynta]

1. I updated to Beta 3.8. It's not pro any more. By intent?

You have used a FREE BETA before and now its a new pure FREE. That's ok.
Update your PRO and have fun

[balloni55]

creating a copy of a track reverse with commands work well
creating a copy of a track with commands work also well ,
but if i create a reverse copy from a copied track (modified or not), all navigation points are lost

[Sersus]

Now all the perfect voice guiding for bikers is broken. You killed the "high, low and medium" options! We have only two choice between simplified and full standard? And in that two cases the Russian variant of voice guiding is broken too (in other words it is not working now), so what can do for proper tts translation?
I am angry!!! And have to roll back to previous version of Locus.
(**** simplifying, you just killed the good working system.)

[gynta]

Hello Sersus

so what can do for proper tts translation?

read and understand: http://forum.locusmap.eu/index.php?topic=3227.msg21951#msg21951
(any help you will find in this thread)

[Sersus]

High Medium and Low is well hidden now in:
Navigation -> Advanced settings -> Number of commands.
same in Guiding.
I hope it helps.

OMG! Thank you! I could not find it quickly on the way. My fault... 

read and understand: http://forum.locusmap.eu/index.php?topic=3227.msg21951#msg21951
(any help you will find in this thread)

I did the previous version of "ru.tts" but did not see until now that new version needed for new version of Locus.
Just made the new ru translation.
Thank you guys!

[Menion]

@balloni55: thanks, I'll check it

@Sersus: Fine, glad that problem solved. And please, don't be so rude immediately after you find some changes you do not like. I'm sure no one is interested in such posts even they may have sense ...

Surprise for me is that TTS file for guidance/navigation stopped work as version 2 (of TTS file) should be enough. And version 2 is required for quite a long time ... hmm

[Sersus]

And please, don't be so rude immediately after you find some changes you do not like. I'm sure no one is interested in such posts even they may have sense ...

Sorry, that was an emotional outburst   

[Bucky Kid]

So the elevation change colouring seems not too improved yet. On my testing track the initial part slowly ascending by 120 height meters is still drawn in mostly green tint  . I guess there may be a ultrashort segment having inaccurate elevation setting the steepness maximum to unreal value. Don't know if this is related to the colouring problem but I assume that ascending parts should be more yellow. At least descents seem no more be drawn in blue colour - the most confusing attribute of previous versions 

So I have yet another suggestion about the colouring algorithm: make the tints fixed to some global values

hardcore downhill (< -30°) - pure blue
..
mild downhill (-15 - -10°) - blue-green
...
mostly flat segments (-2 - +2°) - pure green
...
mild stepping (+10 - +15°) - yellow
...
hardcore climb (> +30°) - pure red

This scheme has one advantage that all tracks show clearly how steep changes in elevation they have


I also suggest to change the elevation change scheme to two new schemes:
- elevation Δ for colouring by segment absolute elevation change (m)
- steepness for colouring by segment slope (degrees).

[Menion]

http://help.locusmap.eu/topic/improve-change-of-altitude-track-style-mode

[Menion]

creating a copy of a track reverse with commands work well
creating a copy of a track with commands work also well ,
but if i create a reverse copy from a copied track (modified or not), all navigation points are lost

Now I'm trying to simulate this problem, but it is not a problem at all, but an intent. If you create a reverse copy of a track, then all commands should be also reversed right? But because Locus do not know how to reverse some commands correctly on certain places (roundabouts mainly), all orders are removed.

[balloni55]

If you create a reverse copy of a track, then all commands should be also reversed right?

yes and as i wrote this work well. For tests i use my jogging round in forest without roundabouts
And so i don´t understand your answer, sorry
So if you see no other solution please deactivate possibility to create a reverse copy of a track which allready included navigation points.