27.01.2016 - Locus 3.15.0 - new version
Blog post about major version: blog post (http://www.locusmap.eu/news-version-3-15-0)
Detailed list of news: list of news (http://help.locusmap.eu/announcement/version-3-15-0-27-1-2016)
01.02.2016 - Locus 3.15.1 - bug fix version
03.02.2016 - Locus 3.15.2 - bug fix version
11.02.2016 - Locus 3.15.3 - bug fix version
11.02.2016 - Locus 3.15.3.1 - beta version (test for live tracking)
24.02.2016 - Locus 3.15.3.2 - beta version
- Changes: read news after app starts...
04.03.2016 - Locus 3.15.3.4 - beta version
- Changes: read news after app starts...
08.03.2016 - Locus 3.15.3.6 - beta version RC
- Changes: read news after app starts...
The issue with .osm appearing in the names of offline maps has not yet been fixed in this release.
Hi,
I found a bug when logging a geocache.
The timezone info is removed in the logging dialog.
So far, so good. But the timezone set on the smartphone has to be respected when saving the log info.
My current timezone is set to UTC+1.
I. e. in the attached "fieldNotes_20160127_1940.txt" the logging time 19:39 ( UTC + 1 ) is not corrected to 18:39 ( UTC + 0 )!?!? The part 19:39Z has to be 18:39Z!!
In the attached "fieldNotes_20151103_2259.txt" created with an earlier version of Locus Pro, everything works as expected.
Or is this a problem with the Addon fieldnotes?
c.s.g.
Hi,
I do a little testing with the Locus Pro 3.14.2 version on the smartphone of my wife. There everything works as expected.
Because my problem seems to be a "Groundspeak / geocaching.com" only issue maybe the best way to solve it is ...
(1.) ... to reactivate the checkbox "Zeitzone berücksichtigen" in the "Einstellungen --> Geocaching" dialog like in Locus Pro 3.14.2.
(2.) ... respect the setting of (1.) in the geocaching logging dialog without showing the current timezone like in Locus Pro 2.15.0
(3.) ... only if necessary, respect the setting of (1.) in any other geocaching diaogs as in Locus Pro 3.14.2 without showing the current timezone in that dialogs.
c.s.g.
@john_percy: really? Weird. Name of files are really just *.osm.map?
@c.s.g.: hmmm really nic problem I wasn't aware, damn. Problem is, that previously all around times in logs were ... bad. Now all should be after years correct :). If you log a cache with new version, all should be correct in Locus and on a web. But seems that add-on Field notes incorrectly handle time of a log. I have to contact author ... thanks.
Nice update, still a fantastic app. Now how do I modify the Travel Times profiles? :)
My rest times while hiking are much shorter.
Onlinemap download by country doesn't select right area. In fact, tapped menu item and actually selected area are shifted by one. For example, if you want 'Czech Republic' map, you have to tap 'Cyprus'.
@menion:
.osm appears in main map title bar and in points database drop down menu but NOT in maps menu.
(http://uploads.tapatalk-cdn.com/20160128/48d0db66aecb044b8ead38ad970b3009.jpg) . (http://uploads.tapatalk-cdn.com/20160128/d941b0b4225f4b78292c7503313d7687.jpg)
Is there likely to be downloadable SHOCart/freytag-berndt maps for Slovenia any time in the future?
inside download window some CZ text is displayed between german
(http://s11.postimg.org/onwbqevov/image.jpg) (http://postimg.org/image/onwbqevov/)
on first start of FREE version i didn´t understand "Locus Pro" in top of screen,
there is no link to buy it :-\
(http://s17.postimg.org/iqcvmd96j/f_p.jpg) (http://postimg.org/image/iqcvmd96j/)
Hi guys, so ...
@biship: currently custom profiles are not planned. Any suggestions for improvements usable for everyone?
@ta-ka: ah, thanks!
@john_percy: seems I used two similar functions that generated names from filename. United = fixed, thank you
@Andrew Heard: you already may download them for every area you wants. Just download them with same method like all other free maps - map manager > menu of wanted map > download. Areas prepared in Store are just for a people that do not want to deal with own area selection or that are familiar with paper maps
@balloni55: hmm seems that Petr has some mess in texts in Store. Thanks. And screen with "Locus Pro" ... well it is really really old screen that promo Locus Pro in Free, but I already have some prepared better version, just find some time on this.
@balloni55
German description for mentioned item should be fixed. Thanks!
Quote from: menion on January 28, 2016, 18:12:20
@Andrew Heard: you already may download them for every area you wants. Just download them with same method like all other free maps - map manager > menu of wanted map > download. Areas prepared in Store are just for a people that do not want to deal with own area selection or that are familiar with paper maps
@menion - thanks - maybe I miss your point - I'm not after free maps - when I go maps > online > SHOCart-Freytag-Berndt > Cycling > offline/Locus store > a list of 11 EU countries is displayed - Austria, Czech, Denmark...UK, but Slovenia isn't on the list. So back to my original question, is it likely other EU countries will be added to this map list in future? BTW I also experience complete phone crash while writing this post, going back & forth in Locus shop/ menus - display blank then reboot, has never happened before, no other details sorry.
Ah sorry. We asked SHOCart/Freytag which countries we should define in Store. And what you see are suggested countries where is something "more", some hiking, cycle trails etc. In other areas are anyway hiking maps also usable. Best from my point of view is check quality of maps in your region on this web map: http://phonemaps.cz/mapa/#openManual
Thanks Menion. It's not so important. The OSM/Locus maps are good enough for me in Slovenia but would have been prepared to pay more for upcoming cycle tour.
Hmm do you know any map company or web map that worth it for Slovenia? We should try to contact them.
Sorry I have no idea. I live in Australia but will cycle tour in Slovenia in June/July with offline Locus maps.
Oki, understand. Because as I know, there are no specialized maps for Slovenia yet, suggest to take for sure backup as some vector maps ;).
Hi,
the setting "Einstellungen --> Geocaching --> Wegpunkte automatisch laden" seems not to work anymore.
I just have activated this feature but it does not work.
c.s.g.
Hello,
what means "not working anymore"? This function before version 3.15 always loaded defined waypoints when you placed a cache on a map. Since 3.15, Locus remember visibility state of all waypoints! So when you display a cache, display also some waypoints of this cache, hide this cache and again display, "automatic loading" won't be applied because cache has already own definition which waypoints load. Anyway if you hide all waypoints, then "automatic loading" should be used next time you try to load a cache. Hope it is clear and make it sense to you. And also that it works as I wrote :).
Hi Menion,
thanks for the info .....
To be true I just activated this feature yesterday for the first time. I select all additional waypoints to be loaded for the geocache in the settings dialog.
I tried it only with my test geocache which was already visible before the activation.
Then I hide the cache on the map and displayed it again. After that I expected the additional waypoints
of that geocache would be visible too. So it looks like it was my fault.
I will test it now with your described szenario on other "new" geocaches....
One more question:
What happens if I empty the database before importing the geocache again?
Does Locus remember the state of the additional waypoints of that geocache though it
was "new" imported to the database because the database was emptied before?
c.s.g.
QuoteAnyway if you hide all waypoints, then "automatic loading" should be used next time you try to load a cache. Hope it is clear and make it sense to you. And also that it works as I wrote
i didn´t use
Settings/Geocaching/Automatic waypoint loading/.....
but i can reproduce behavior c.s.g. reported ;)
please try:
- disable each waypoint typ in setting
- display e.g. 5 Multi caches with WPTS with visible coords
- open each of this caches and hide all WPTS
- enable all WPT type inside Settings/Geocaching/Automatic waypoint loading
- restart locus
- no additional WPT is visible on map.
so for me since V 3.15 this settings are useless
oki and when as next step you re-display all caches?
Quotewhen as next step you re-display all caches?
nothing chage, furthermore no WPT is displayed
last state is allways used
ah sorry, I'm just checking it and you are both correct. If there were no waypoints to load, Locus skipped "auto-load" feature. So fixed. Thanks
V 3.15.1
QuoteLocus skipped "auto-load" feature. So fixed. Thanks
Hi menion
generaly this auto load work now if in settings wpts are set and if i (refrech) hide all geocaches of folder and display them again.
But if i change settings and disable all wpt types for autoload they are always displayed from "last state"
I can hide them by " Remove temp map ttems" but on next start of locus all wpts of all caches are visible again. :(
For now i found no solution to hide all wpts at once :-[ permanent
i have to click each cache label/arrow right/hide all wpts to hide them again ::) nice evening work with more than 500 multi caches in folder
Edit:
my idea to restore pois from yesterdays backup didn´t help, all wpts are furthermore displayed :o
Do you know any other solution?
Good evening balloni, hope you have nice evening yesterday. So seems that main issue is, that removed waypoints with "remove temp map items" are not remembered and are restored after restart of app, like you never hide them, right?
Fine, thanks! Issue fixed. Because I found two more serious problems (incorrectly coloring tracks when they have breaks, online SmartMaps), I have to publish one more version probably in Thursday, so hope it will not be a problem, to wait till then.
no it´s not a problem ;)
QuoteFine, thanks! Issue fixed
this is the important news!
One additional question, aren´t "states of wpts" stored inside poi backup?
Hmm as I see, they aren't stored in backup. They should be right? Information about which points/tracks is stored, so why not also these cache waypoints. Oki, I'll add it.
Hi menion
generaly hide all temp visible wpts work no after i have changed settings "all wpts disabeled" :)
thanks
i didn´t know it´s intended,
if i enable display wpts in settings this is dominant after restart of locus,
means:
- after start of locus all wpts are visible :)
- now i disable visibility of wpts of one cache
- next disable visibility of this cache and enable it again, state of wpts are stored - no wpt of this cache is visible :D
- but on next restart of locus all wpts of this cache are visible (from settings) and not unvisible from last state :-[
i hope it´s understandable
one small change i notice after each locus update:
down right button "zoom lock" is allways enabled, althought i never set it :-[
Hi menion, I have issue with OruxMaps SQLite in 3.15.2. Shown as white area. Other formats seem show properly.
Sent from my phone by Tapatalk
Good evening guys, such a fast reactions on a new version, seems I can't have even an evening free ;)
@balloni55: on new visible geocache (no matter if you display it or is loaded with application start) should be applied two rules:
1) are there any waypoint that should be load (restore of previous state)
2) if previous is negative, then - are there enabled any "auto-loading" options
Nothing more ...
And bottom "zoom lock" - again some option enabled without any change in app? Hmm :/ (previously it was OSM notes if I remember correctly) ... interesting.
@Bucky Kid: I have just three old OruxMaps in device that I tested and they work fine. May you share any not-working map with me? Btw. hope that map worked in previous versions.
Quote from: menion on February 03, 2016, 21:31:03@Bucky Kid: I have just three old OruxMaps in device that I tested and they work fine. May you share any not-working map with me? Btw. hope that map worked in previous versions.
Here's a nap that doesn't render: http://www35.zippyshare.com/v/idY06trN/file.html (http://www35.zippyshare.com/v/idY06trN/file.html)
And yes it showed fine in 3.15.1 version.
Sent from my phone by Tapatalk
Map with 0 bytes can't work well in Locus ;)
Oh wrongly created archive. Please try this: http://www53.zippyshare.com/v/3f4A1OOF/file.html (http://www53.zippyshare.com/v/3f4A1OOF/file.html)
setting -> gps -> run at startup -> always / previous state
don´t work anymore. when i use one of the options, gps is running and i exit locus the gps is off at the restart
when gps is running and i kill locus und restart it the option is working
@Bucky Kid: thanks, fixed
@skwal: hmm what you mean with "restart"? Did you wait a few seconds before you start Locus again?
Quote from: menion on February 04, 2016, 08:05:46
@Bucky Kid: thanks, fixed
Thanks for quick fix. Was it lost WEBP support in Orux SQL if I'm guessing right.
Quote1) are there any waypoint that should be load (restore of previous state)
2) if previous is negative, then - are there enabled any "auto-loading" options
Nothing more ...
so if i understand your description right, it´s intended
QuoteAnd bottom "zoom lock" - again some option enabled without any change in app? Hmm :/ (previously it was OSM notes if I remember correctly)
exactly
With the latest bugfix release, the extra .osm has disappeared from the title bar (thanks) but my Great Britain map from OAM is now titled "United Kingdom" in the title bar, although it displays the correct name in the map selection dialogues. Odd.
Not only odd, though, but wrong. United Kingdom is not the same as Great Britain. GB is a geographic name for England, Wales, Scotland but none of Ireland. UK is the political name for GB plus Northern Ireland.
(http://s11.postimg.org/mgg04dlqn/Screenshot_2016_02_04_08_23_39.jpg) (http://postimg.org/image/mgg04dlqn/) (http://s12.postimg.org/otyptnkjd/Screenshot_2016_02_04_08_24_04.jpg) (http://postimg.org/image/otyptnkjd/)
@Bucky Kid: hmm, what is "WEBP"? :) Anyway problem in 3.15.2 is that Locus try incorrectly set zoom level to selected OruxMaps (that use little bit different system compare to other basic SQLite based maps).
@balloni55: trust me, I have absolutely no idea, why this rarely happen.
@john_percy: hmm, little bit "funny". Thanks for explanation, so in next version it should be finally ok.
Hi menion,
i didn´t know it´s new, but i noticed it today
- i display a POI on map
- open POI folder and move this POI to another folder
- POI isn´t activated in his new folder
- but icon is forthrmore visible on map, popup label open also but it is not clickable :-[
- back to POI folder i activate this POI and go back to map
- label is furthermore not clickable
- back to POI folder i open this POI and click on map preview
- now label on map is clickable :)
Hi,
I actually have a very strange behavior on opening a (single) cache (GC2200G).
Every time I click on the icon (on map or folder) Locus crashes. All other caches work fine.
I already deleted it completely (even in directory) and reinstalled it. Same happens as mentioned above.
(http://s23.postimg.org/7sripm9h3/2016_02_05_201226.jpg) (http://postimg.org/image/7sripm9h3/)
(click - you will see gemf mtb tar img and orux )Quote from: jusc on January 06, 2016, 08:37:08
Yes map icons are really too small. please try with Google online maps.
For offline maps the icons could better distinguished if they differ more. Vector and gemf format map icons are very similar.
Quote from: menion on January 06, 2016, 13:21:00
@jusc: understand. I've currently other important tasks for Scinkk (graphics), but I'll keep this in mind (together with black/white icons in settings)
hello menion, any news about unreadable icons?
@balloni & JoxM: have to test it in Tuesday when I return from short vacation
@gynta: nope, new icons not yet even requested, not an important I think
Quotehave to test it in Tuesday when I return from short vacation
additional info
with GC2200G problem appears for me not after "update cache" as described on help desk with GC67TXG, but after "download loggs"
Its me on helpdesk. Nice to hear that other have the same Problem
Meninon, please, fix the following bug:
When logging a geocache from Locus:
1) Seconds (which cannot be set by users) in the final time are not zero (Currently they may be set randomly ?!!)
2) The time set in Locus is still not considered UTC and IS BEING TRANSFORMED (currently by one hour in the Czech Republic)
For details, please see http://forum.locusmap.eu/index.php?topic=4975.0 (http://forum.locusmap.eu/index.php?topic=4975.0) (Czech)
@balloni55: thanks for a precise description of problem when moving a point between folders - should be fixed
@JoxM, @balloni55, @Diddi : as mentioned on help desk, issue should be fixed
@Čelda: I don't think there is any problem in Locus. Seconds are not set by Locus. Whole time is created in moment, you tap on "log" button, even a seconds. And time moved by hour? From your Czech post is not clear what is wrong as I do not see time, when and where you made a log.
Hi menion,
once again "MapQuest" didn´t work as source for address search for me:-[
google and bing work well :D
We know ... it's same here http://help.locusmap.eu/topic/problem-with-mapquest-online-routing . Problem is simple .. we pay them quite a lot for routing for a last months and as a gift, they changed our account to "free", so limit for routing/address search was reached.
Hope they'll fix it soon ... terrible communication with them, really, can't recommend to anyone!
Mainly because of incorrectly working support for OruxMaps based maps and crashed when display of caches on older devices, new version should be soon available on Google Play. Thanks for help with fixing some remaining bugs, hope that finally ... third bug-fix version ... will be fine ;).
If I do a two finger zoom, and then zoom with the + or - buttons, or with the volume keys, map zoom jumps to a regular value, eg Z13 @ 100% (or Z13 @ 125% if I have "Increase map resolution" set to 125%).
If I do a two finger zoom TWICE and then zoom with the buttons, Locus behaves as above UNLESS I have "increase map resolution" set. In that case the zoom is stuck at whatever random value I ended up with from my two finger zoom, eg Z13 @ 168% goes to Z14 @ 168% not Z14 @ 100%.
To get out of the locked zoom I have to do a single two finger zoom after a button zoom, and then do another button zoom.
I hope you understand my explanation and can reproduce this or I'll have to illustrate with a load of screenshots.
And please don't tell me it's an undocumented feature.
Hello john,
I'm not 100% sure that I understand, but probably yes. And well, it's an new undocumented feature. It works now that if you are in range 75% - 125%, then zoom in/out round this value to full scale. If you are in range below 75% or in 125% - 175%, then scale should remain. Well, this is just for a testing for now and few days/weeks of usage shows if this is usable and logical or not.
I suppose that makes some kind of sense but it didn't seem obvious to me when i was using the map.
My conclusions about the circumstances where it happened were wrong!
Hello menion,
thanks for new version :)
problems with "GC-logs" and "move POI´s" are solved ;D
New orange label is misleading for me, it´s the same text independent GPS is off, or GPS is on but no satfix
(http://s28.postimg.org/5xln0gnbt/orange.jpg) (http://postimg.org/image/5xln0gnbt/)
and puuuh what a ugly new icon!!
with this new icon i didn´t know is FREE or PRO running :o
btw, new icon
http://forum.locusmap.eu/index.php?topic=4913.msg40679#msg40679
your answer
Quoteicons ... good point. If I'll not forget, I'll ask scinkk for an alternative icon
did you forget it?
Quote from: balloni55 on February 11, 2016, 19:27:48
New orange label is misleading for me, it´s the same text independent GPS is off, or GPS is on but no satfix
good point
orig string: "Last known location is outdated.\n\nConsider enabling GPS for better positioning."
but is "satfix" the right hint?
what about cell an network localisation?
Quotebtw, new icon
http://forum.locusmap.eu/index.php?topic=4913.msg40679#msg40679
your answer
Quoteicons ... good point. If I'll not forget, I'll ask scinkk for an alternative icon
did you forget it?
http://forum.locusmap.eu/index.php?topic=4963.msg41028#msg41028
...and read following answer
The new version gives Great Britain as the map name correctly. Good. Sadly it no longer recognised the great_britain.osm.db database file I downloaded as beta and have been using for a while.
New version is displaying all maps properly, thanks ;)
I see a change in zoom handling when switching maps. If I found out right, Locus now forces preserving same magnification level from existing map to new map. This is good idea but also cumbersome for some cases.
I give an example:
I'm on vector map on zoom layer 16 and magnification 100%.
When I switch to raster map with only having zoom layer 15, it is now displayed with magnification 200% (OK).
But when I switch to raster map with having only zoom layer 12, it is now displayed with magnification 1600% (terrible and unusable!).
I'd suggest to keep preserving of same overall magnification but only when the new (raster) map has layer at least close to target magnification. If not, use some min/max limit for acceptable optical zoom, ie.50%-200% would be fine.
Edit: when switching from lower zoom to higher zoom layer, the magnification is reset to 100% (OK). So my remark was only for cases when switching from higher to lower zoom layer (hard max magnify limit)
img server down?
(http://s7.postimg.org/645cwf4br/2016_02_12_224205.jpg) (http://postimg.org/image/645cwf4br/)
broken link
(http://s10.postimg.org/41bk7dx9x/2016_02_11_235249.jpg) (http://postimg.org/image/41bk7dx9x/)
Hi all, sorry for a delay with answers, here we go ...
@balloni55: hmm text when centering. Quite complicated task. This text should warn that position (GPS or network, newest is used), where map is centered is really really old (more then 2 hours). When I disabled centering on these old positions, I get messages that Locus do nothing. If I center on every location, I get messages that Locus center on weird places. So this is another desperate attempt :).
Icon: well, on Android 5.0+, Android itself change color of status bar icons to full white. So nice Locus logo became just white rectangle. So this is different try which seems to be fine I think ;)
Ah this icon ... gynta's answer was incorrect - in this case I forget.
@gynta: answers in above paragraph
@john_percy: understand. I still do not know how to properly handle these DB Points. Anyway within next few months, things will surely move
@Bucky Kid: yes, I'm aware of it. My opinion was, that no-one will use map with just zoom level 12, 13 etc. But seems, someone has such maps :). Oki, I'll try to improve it if I don't forget.
@gynta: images are downloaded directly from homepage. Seems it's working now ... probably temporary issue. And link ... thanks, fixed.
Quote from: menion on February 13, 2016, 19:20:45...gynta's answer was incorrect - in this case I forget.
my fault - sorry
the keyword "scinkk" was the trigger :)
The GEOnet Names Server has moved (used in offline searches)
(http://uploads.tapatalk-cdn.com/20160214/1010136edf64cacdbde681ddd3799804.jpg) . (http://uploads.tapatalk-cdn.com/20160214/8486bc11e0fbe2d5d1a0b48dee089407.jpg)
Thank you John. Btw. are you using this feature? I'm just finishing some improvements around searching options, so is support for geonames/gns useful and working?
I've used Geonames quite a bit for offline search. For some reason I hadn't used GNS until just now. A combination of offline maps, offline routing and offline search works well.
Oki, thanks. Good news is at least that in next version, offline search in these files will be twice as fast ...
Quote from: menion on February 11, 2016, 17:38:28
I'm not 100% sure that I understand, but probably yes. And well, it's an new undocumented feature. It works now that if you are in range 75% - 125%, then zoom in/out round this value to full scale. If you are in range below 75% or in 125% - 175%, then scale should remain. Well, this is just for a testing for now and few days/weeks of usage shows if this is usable and logical or not.
So I do a two fingered zoom in on a vector map to see a feature more clearly. I end up at say zoom 19 at 168%. I click a [ - ] button a few times to return to a smaller zoom -- but whatever zoom I go to stays magnified to 168%. I don't like that.
To return to a standard zoom level I have to do a two fingered zoom to the range 75% to 125% and then press [ - ] or [ + ]. I don't like that either. Maybe others do.
Hi again.
Just a short question because I didn't find it in the doc and don't want to start a new post.
I enabled all waypoints of my geocaching points with the geocaching tools.
Is there a way to disable them again? I don't want to see them all the time. When I disable and enable all points the last state is shown (all enabled)...
Gesendet von meinem LIFETAB_S831X mit Tapatalk
after you have disabeled them in settings , e.g. long klick on "data icon" > Remove temp map items
Thanks a lot
One fresh new Beta version after almost 14 days.
Complete list of news after app start, as usually. Main focus - probably live tracking who is interesting and search screens. There are rewrote from scratch and even I've tested them a lot, there sure may be some issues. Thanks and enjoy evening!
V 3.15.3.2
Markdown problem * in cachelisting solved :) thanks
after click on sidepanel icon "points of interest" blank screen with message "No data in list" independent what map type is used, in Pro it work :-[
Ah ... after some massive changes (preparation on offline search for addresses), I've completely forget to check this feature. Thanks, I'll look at it tomorrow! (issue confirmed also on my device so consider it as "fixed")
Quote from: john_percy on February 15, 2016, 19:01:54So I do a two fingered zoom in on a vector map to see a feature more clearly. I end up at say zoom 19 at 168%. I click a [ - ] button a few times to return to a smaller zoom -- but whatever zoom I go to stays magnified to 168%. I don't like that.
I don't like that either, sorry.
I understand it's intentional, but hopefully we can change your mind...
Something seems to be wrong reading the maps at startup :
(http://uploads.tapatalk-cdn.com/20160225/8f1a41a2c39ac889750f2a78418d45a3.jpg)
In the running application the maps are available.
Strange.....
And these are vector maps or some downloaded online maps? You have added directory with these maps as "Own directory" directly in map manager or you set this directory as default for vector maps in Locus settings?
Hi Menion,
these maps are vektor maps only (OAM)
I set this directory as default for vector maps in Locus settings.
Regards
Ralf
Same map load error problem, but only in Beta, Pro works like a charm.
Quote from: michaelbechtold on February 27, 2016, 01:53:22
Same map load error problem, but only in Beta, Pro works like a charm.
Same here.
Also found in Beta, that Quick Map Switch does no longer care about the visible map - it just lists kind of history of maps viewed. No longer nearest maps.
Locus 3.15.3.2 doesn't skip device's lock screen even if "Disable screen lock" is checked. Please confirm that.
Hi,
problems with maps ... because I did some more changes, I'm unable to simulate it now. So hope it's fixed for now.
@michaelbechtold: as I know, nothing should change in Quick Map Switch
@ta-ka: are you using secured lock screen (you need to enter pin or pattern to unlock)? Then it probably do not work anymore as you noticed. There were some issues with secured lock screen. Anyway if you are using basic non-secured lock screen, all should work as previously.
Hi menion,
Yes. I use pattern lock when I'm not at home. I like "Disable screen lock" function because it gives very quick access to Locus by just turn on the screen while keeping the security of the other apps at the same time. As you mentioned, "Disable screen lock" works with non-secured lock screen. However in this case, the advantage in security is lost because no apps are protected any more. What are some issues by the way? I personally don't have major issue so far. A minor issue is that the lock screen is sometimes shown in short time between screen transition.
Hello,
just from last few days http://help.locusmap.eu/topic/locus-pro-freezes-after-screen-offon , anyway it is quite common problem. It is not allowed for programmers to completely disable protected lock screen. It's only possible to move a single screen from own application before this lock screen, but "lock screen" remains active when you move from this one screen to any other app or other screen. Unfortunately, but quite logically I think.
I am currently using Locus in heavy load on our summer holiday :-) and to my suprise I have found out that an existing wpt under a geocache cannot be changed ! It looks like it can but the coordinates are not being updated in 3.15.3 ! This definitely worked OK in the past but now an issue with refresh could have occurred. Adding a completely new wpt works OK.
@menion
Thanks for the link. I've understood the situation and I'll accept new behaviour of the "Disable screen lock" function.
@Čelda: are we talking about waypoints from internal database?
@ta-ka: thanks, appreciate it.
>@Čelda: are we talking about waypoints from internal database?
The geocaches were downloaded in Geoget, expoted as a GPX file and imported into Locus.
Hmm for my own surprise, it works fine for me. So I need as usually ... exact step by steps, how to simulate it, or a video that should this process. Thanks
Well, I have reimpoted the geocaches from the GPX file into Locus and everything is OK now ::)
So apparently there was an error but a more complicated one than it seemed to be. So let it be for now.
It might have something to do with an unpleasant feature I observe on my Lenovo Android 5.1 device:
I keep my phone unlocked when running Locus (Nastavení - Obrazovka - Vypnout uzamčení obrazovky) . However, when I want to edit a wpt setting (eg. coordinates) the Locus dialogue window does not override the phone lock - nothing appears till I switch to the Android desktop, unlock the phone and switch back.
beta 3.15.3.4
POIDB function -> FC
The error message at start appears again:
(http://s18.postimg.org/7u3j4bmfp/2016_03_05_06_15_04.jpg) (http://postimg.org/image/7u3j4bmfp/)
@gynta: thanks, damn, fixed
@tramp20: hmm may you post here also screenshot of your settings of Locus directories (menu > settings > misc ...) + screenshots of custom map directories (menu > maps > '+' > External maps)? Thanks
Ok here are my Screenshots
(http://uploads.tapatalk-cdn.com/20160305/e46edbd6874cf8d8e23e9b1130da2bd5.jpg) . (http://uploads.tapatalk-cdn.com/20160305/e9638787c426584a9c4db16d64a10393.jpg) . (http://uploads.tapatalk-cdn.com/20160305/e2a0763055f5f33be5f0854e869e39d0.jpg)
Hope this helps you
Gruß
Ralf
vom Schmartfon
Hmm thanks.
So if I understand correctly, your "maps" and "mapsVector" directory are same and you also added same "A_Maps" directory as external directory? So you point on same place from three various methods where all should be unique? Hmm oki ...
EDIT: oki, I was finally able to simulate this problem and "fix" it, thanks for help
Quote from: menion on March 05, 2016, 07:41:47
@tramp20: hmm may you post here also screenshot...
(http://s29.postimg.org/mlux9tko3/2016_03_05_10_41_21.jpg) (http://postimg.org/image/mlux9tko3/) (http://s28.postimg.org/5q1jrt37t/2016_03_05_10_56_53.jpg) (http://postimg.org/image/5q1jrt37t/) (http://s18.postimg.org/mbe9mio9h/2016_03_05_10_58_48.jpg) (http://postimg.org/image/mbe9mio9h/)
You notice the difference in the paths between "maps" and "MapsVector"? They are both on my external card.
If I want to change the maps dir I get this picture where I can select the path in the first line:
(http://s22.postimg.org/z52fp9vrh/2016_03_05_10_49_26.jpg) (http://postimg.org/image/z52fp9vrh/)
If I want to change the mapsVector dir I get a complete different picture to select the path:
(http://s8.postimg.org/f94982k81/2016_03_05_10_53_43.jpg) (http://postimg.org/image/f94982k81/)
I assume this is not intended but it is the same in the pro version.
Quote from: menion on March 05, 2016, 11:34:09
Hmm thanks.
So if I understand correctly, your "maps" and "mapsVector" directory are same and you also added same "A_Maps" directory as external directory? So you point on same place from three various methods where all should be unique? Hmm oki ...
EDIT: oki, I was finally able to simulate this problem and "fix" it, thanks for help
And it does not only appear when directory "pointers" are the same. I have Maps and mapsVector separated, but still have the problem. Glad you found it, and looking forward to he fix.
New beta version today redraws much more slowly than current pro version. Is it the hill shading?
yep, around two times slower now ...
Oh no. Are you going to improve this before final release???
The release notes said this was an improvement!
Improve - we will see. Not so simple now. And "Improvements" - well, compare how it looked before and how it looks now. This is what I call improvement.
with raster maps since now i didn´t noticed delay of displayed map while zoom or shift, now tiles load slowly, it depends on new "map shading"
Quote from: menion on March 06, 2016, 15:32:04
Improve - we will see. Not so simple now. And "Improvements" - well, compare how it looked before and how it looks now. This is what I call improvement.
I remember last year when you changed algorithm for redrawing maps and it was a little bit slower. Was not happy with that.
This year it is gonna be 2x slower. :(
When you make an improvement for a function (shading) but another function is more worse than before (velocity of redrawing) its not an improvement of the package (Locus) its a change...
So i hope you will continue to develope on velocity to avoid of slowing down
Hill shading display slower : after several test, sorry to say that, but the hill shading function is no more usable for me as is at this time. Too slow. It's a shame :'( . For me, if i had the choice, i would prefer to choose the old hill shading processing way and be able to use it. Hmmm having the choice between old and new style in the settings menu is imaginable ? My device : Samsung SM-G800F (Galaxy S5 Mini) .
Hill shading is important to me.
I may have to stop upgrading if the slowness makes its way from beta into a regular release. Thanks for the warning.
Ok, I take a look at the new hillshade. It realy look better, special in lower zoom levels.
But I agree to the answers before: It is mutch to slow, compared to what we have today.
Gruß
Ralf
vom Schmartfon
Can somebody please post a screenshot of new hillshading for non-beta-testers? Thanx.
http://help.locusmap.eu/topic/slope-shading-in-different-colours-30-35-40#comment-25480
@ Christian
(http://s15.postimg.org/tq2mo827b/Hill.jpg) (http://postimg.org/image/tq2mo827b/)
Thanx. Also for the link.
@Christian : and for me ...
(http://s10.postimg.org/43l28pa85/Locus_Compare.jpg) (http://postimg.org/image/43l28pa85/)
For me, the new hill shading is far too dark and obscures detail in mountainous regions. (http://uploads.tapatalk-cdn.com/20160307/610ced4bb27ea105ad0e659d07f6762f.jpg)(http://uploads.tapatalk-cdn.com/20160307/88620dbf501bdf1350787b2a82ebf625.jpg)
1. Pro | 2. Beta
yes much too dark, the Alps look like Modor. ;D
Thanks for opinions.
Result: little lighter, compare to current public version is shading itself around 40% faster (previously 0.23 sec per 512x512 tile, not 0.14 sec). That's much I can get from it now. If this won't be enough, I'll consider some caching options.
At the Moment I can only test with Note 2. For me the speed is sufficient. nothing I can´t wait for.
Dark:
If I zoom out to 11 the darkness of shading is ok, looks nice. but if you zoom in to 14 or 15 it´s a bit too dark.
Is it pssible to make a slider as for overlays, that users can set it for their own?
Hmm if we find some collective agreement, I may code different "darkness" for various zoom levels. It's not an unreal task. I usually rather wait on some field testing. So if you don't mind, wait on new 3.16.0 version and use it for a while. If after week or two, more people will agree that some changes in darkness will be useful, I'll do it.
And slider - I hope that such extra settings won't be really needed.
Jeep, different darkness according zoom level would be also fine for me.
Quote from: menion on March 07, 2016, 11:50:45
I usually rather wait on some field testing. So if you don't mind, wait on new 3.16.0 version and use it for a while. If after week or two, more people will agree that some changes in darkness will be useful, I'll do it.
That is ok for me.
Quote from: menion on March 07, 2016, 11:50:45I may code different "darkness" for various zoom levels.
While you're in there... If you extended the shading to zoom level 17, even a little bit of it, I'd be a happy camper.
I must agree with the other comments here... the new hillshading is a) way too dark and b) waaaaaay too slow. It might be "prettier" and "more detailed", but that doesnt help usability at all. With the latest beta, my state of the art super highspeed phone (note 4) needs more than 10(!) seconds to redraw the map. I would consider this not fit for release.
menion, if you want to keep this new algorithm, I strongly suggest running it *separately* and *after* normal tile rendering. Just render non-shaded standard tiles first, so we can instantly see the map. Then "fade in" the hillshading (or slope coloring) smoothly afterwards (tile by tile, as soon as they finish rendering). Then speed will not matter that much.
The current beta basically cuts Locus map rendering speed in half (or worse)... a horrible idea indeed! You spent so much admirable effort speeding up mapsforge by single percentage values... and now you simply enforce a 100%(!) penalty as if it meant nothing and even call it a feature. Please think twice before releasing this. Almost nobody will notice the increased "prettyness" but everybody will whine about the major slowness.
As for the darkness... that's at least 100% too much! Even with one of the brightest smartphone displays on this planet, I can hardly make out anything in your shaded areas... WHEN I AM OUTSIDE. You users run Locus OUTDOORS in difficult conditions, not on a comfy developers couch with smooth ambient lighting. If you really think that the new look is useful, you must give us a slider to tune it down by an order of magnitude.
Btw... no complaint without a suggested fix. Apparently this HGT altitude file format is super bitchy, performance-wise. I can't really see a reason to parse and render it over and over (and over and over and over) again for hill shading on every map scrolling operation. Couldn't you simply turn it into a sqlite map with greyscale png tiles, right after download? Like S14W074.hgt becomes S14W074.sqlite? Then your hill shading will simply be as blazingly quick as any map overlay, no more extra work to be done repeatedly, no more users bitching about speed. You could even delete the original file (uncompressed bullshit?) after download and save loads of storage space.
Then the speed of your shading algorithm wouldn't matter at all, because it will only run ONCE. And you could make it super-pretty and super-nice. And we would even get "adjustable hillside darkness" automatically with the opacity slider for overlay maps. Any reason this wouldn't work? Am I missing something? Couldn't hill shading (and also slope coloring) simply be a special kind of pre-rendered map used as overlay?
Danke Stefan. Sounds good.
Quote from: Christian on March 07, 2016, 22:11:56
Danke Stefan. Sounds good.
If I could, I would vote for a MONTH-OF-PERFORMANCE :-). No work at all put into new features, but instead only focus on snappyness and speed and usability. The most annoying things that Locus does to its users at the moment are IMHO
1) showing a "working..." dialog, completely blocking the app.
2) showing a blank screen, basically meaning downtime for the user.
3) scrolling and zooming choppily by doing too much work on the main thread.
#1 for example makes editing a track on screen a complete nightmare... deleting a few bogus points from a recording is an experience I wouldn't wish upon my worst enemy.
#2 staring at a blank screen waiting for stuff to appear is really annoying. sad enough that Locus still can't pinch&zoom properly in 2016, even though this is arguably the most often used gesture on a smartphone. and now the latest beta more than doubles the "staring at blank screen"-time even for simple scrolling operations. holy moly.
#3 is an ongoing topic since the very beginning due to missing multi-threading. the more data you have, the choppier and more unpleasant your overall Locus experience will become.
Don't get me wrong... I do LOVE features and Locus is the most amazing gps software I have ever seen in that regard. But it really wouldn't suffer from focusing on a snappier user experience for a while. I mean... seriously... even for such a simple thing as tapping the GPS icon... my phone takes a break of nearly one second(!) before anything happens on screen. This might not sound like much... but any tap that doesn't give instant feedback will make you wonder... did I miss the button? was there snow/rain on screen? are my gloves too thick? is my bike shaking too much? was I shaking too much? shall I tap again now or wait some more?
I know stuff like this is hard to imagine on a cosy beta testing couch with perfect lighting... no wind... pleasant temperatures... not wearing sunglasses... not sweating... not freezing... not being in a hurry... not having to operate your 6"-phone single-handed... etcpp.... anyway... long story short:
Locus is an amazing app, but snappy it is not :-/.
Stefan, do for me one test please. Do backup of your "Locus/data/database" directory and then delete it (or just rename it).
Start Locus and check mentioned issues once more. I remember I get from your for some testing your database with tracks, which had around 100 MB and well, work with tracks was really slow for me as well. If app and mainly work with points/tracks will be a lot faster, then issue is in not-well-optimized work with database itself, nothing more.
Well, hope that last Beta in this row is out. Enjoy it and use last chance to fix some remaining problems till release ;).
And who have loooong evenings, may check our new "secret" feature: http://forum.locusmap.eu/index.php?topic=5016.0
I have to agree with Stefan. My db is about 35MB couch size. The first 4 seconds after tapping the Locus icon on homescreen i get always a black screen.
Map scrolling and zooming have lags.
Editing track... ehm... i'm waiting for the rubberband feature.
A project "Locus lubrification" (german joke) for a better performance would be nice. Its imho essential for a mobile app.
I will wait for the next release, read the forum and will than decide to update or not.
Tested with 3.15.3.6
- No longer error screen for loading maps
- Darkness for hill shading OK for me
- Rendering performance with hill shading is still not in an acceptable range
confirm the map loading error is gone.
Gesendet von meinem SM-N9005 mit Tapatalk
@joeloc & @christian and also other who now or will in future complain about performance:
Nice talking Stefan. I'm quite often surprised that mainly you, who previously were an developer, see things as so easy to do. Anyway performance with empty/fresh installation is one thing, performance with few years of collected maps, points, tracks and many various settings is another thing, no matter if you sit home and spend most of time on improving app or you ride a bike in wild countries and just report "it's slow".
So if someone wants to improve performance in cases it make no sense that app is slow (like just a few points on a map, etc), only usable information as I see it now, is reproducibility on own device.
So best
- clear installation and empty Locus directory
- here download and import this X file and do this, bam .. slow
I have not a big "problem " to invest time to some optimizations of performance when I know exactly where and why. On second side, no matter what you think, it is something I invest quite a lot of time into it and I think that speed of Locus is quite well.
Thanks for understanding.
@jajaballard: oki, thanks. I'm worried that current performance is best I may get from device with current algorithm in latest 3.15.3.6
@michaelbechtold: thanks, finally
@menion But in this case hill shading was modified to improve it in beta. Beta users report that the slowing down was too great for the improvement gained. Isn't that what you have beta testers for?
absolutely agree. Did I said something that is against it? In case of hillshading I spend on it, because of previous reports, almost whole weekend and result is latest Beta version. And on report from jajaballard I wrote, that for now it's unfortunately not possible to speed it more.
@menion,
I have no problem with hill shading, it is fast enough for me.
QuoteIn case of hillshading I spend on it, because of previous reports, almost whole weekend and result is latest Beta version.
we belive that :)
but i agree with john_percy and for me it´s a step backwards :-[
While playing on sofa with disabeled GPS i noticed that my device temperature grows up ~45°C, so i assume the new shading needs more accu. With PRO i didn´t notice increase of temperature.
With Lomaps Germany and Baden_wurttemberg i see a problem on ZL 10-12 independent on used locus theme, with PRO it work well. N 47°59.940 E 7°50.526
It seams that some tiles ZL hang
(http://s15.postimg.org/6lumhqkrr/Problem.jpg) (http://postimg.org/image/6lumhqkrr/)
Quote from: balloni55 on March 09, 2016, 16:43:53
It seams that some tiles ZL hang
confirmed
eg
(http://s9.postimg.org/x2vpjw2kr/Screenshot_2016_03_08_20_25_31.jpg) (http://postimg.org/image/x2vpjw2kr/) . (http://s9.postimg.org/hiobtcsgb/Screenshot_2016_03_08_20_26_51.jpg) (http://postimg.org/image/hiobtcsgb/) . (http://s9.postimg.org/yfdels00b/Screenshot_2016_03_08_20_27_20.jpg) (http://postimg.org/image/yfdels00b/) . (http://s9.postimg.org/z0xs455or/Screenshot_2016_03_08_20_28_34.jpg) (http://postimg.org/image/z0xs455or/)
althought i have disabeled shading, in down left area of german maps shading is visible in lower ZL
(http://s21.postimg.org/63tbfxpxv/Screenshot_2016_03_09_21_20_02.jpg) (http://postimg.org/image/63tbfxpxv/)
@gynta: hmm really nice issue. It's there also in latest public version and this issue should be there since exists shading. Problem is that on that tile are no data in vector map. Result is empty tile and well .. no shading. I was trying to fix it, but all attempts break mainly auto-loading of vector maps. So for now, no simple solution. I'll try to do something with it later.
@balloni55: anything I may do to reproduce it? For me, when I disable shading, whole map redraw without it. Weird.
Hi menion
it´s more and more confusing for me
today i purchased new map "germany south" in hope to solve my problem with it, please compare both screenshots with different maps i get different results :-\
most problems apeare at ZL10-12
with disabeled shading
(http://s30.postimg.org/gkmw8oi1p/disabeled.jpg) (http://postimg.org/image/gkmw8oi1p/)
and with enabeled shading
(http://s22.postimg.org/5f3qxni4t/enabeled1.jpg) (http://postimg.org/image/5f3qxni4t/)
how can i support you to solve this behavior?
Nice, interesting. Do you have disabled autoloading of vector maps? May you try to enable it? Only what I think it may cause, are some cached tiles for vector maps. And vector maps are cached only in case, auto-loading is disabled.
thanks for your idea,
but it doesn´t matter vectormap autoload is enabeled or disabeled
all works fine on ZL13 and higher
I can confirm some hanging tiles with latest beta... but it looks to me as if only the "hill shading part" is hanging. Is there maybe some separate caching going on for the hillshade layer now?
As for the hill shade speed... better... but not quite fast enough :-(. Is it really such a bad idea to first render ALL TILES normally and ONLY AFTERWARDS, when the screen is completely filled already, spend any cpu power on shading? You probably think it doesn't make any difference in overall rendering time... but the difference in look & feel & snappiness would be absolutely major. Blank screen staring time is reduced to a minimum.
Also... when scrolling&zooming, it usually takes a few taps & swipes for me until I find the area I am actually interested in. But I still have to wait for the map to render in-between to see where I am going. If shading/coloring would NOT BLOCK normale tile rendering, this process could be much faster. Locus would obviously abort shading/coloring for the tiles that are scrolled off screen quickly... saving battery and cpu time.
Hill shading for me is nothing I enable "just occasionally". On the contrary: I consider it absolutely essential for vector maps to make them look reasonably good. So anything that happens here directly affects every single moment of my "time with Locus". Progress in this area is just as important as in actual osm data rendering and slowdowns are just as annoying.
From a users point of view, things are really simple: If you can see an app (any app) "slowly" build up its screen part by part, it feels "sluggish". If the screen is just there, it feels fast. I admit having no idea whatsoever about the complexity of the actual shading algorithm... but if you'd simply do the work *afterwards*, it's slowness really would not matter so much. Thinking in this direction is IMHO much more rewarding than squeezing out another 4% in actual algorithm speed.
Oh... to end with something positive... the brightness/darkness is totally OK now :-).
Edit: Added a video of current beta hill shading speed on a Galaxy Note 4. Ten seconds for a screen is not exaggerated.
Quote from: menion on March 09, 2016, 11:17:07
- clear installation and empty Locus directory
- here download and import this X file and do this, bam .. slow
This is one way to look at it... and I have a hunch that your own Locus installation is basically similar... almost always almost clean... with just a few tracks and very few points.
Another suggestion, that is probably more likely to give results, would be for YOU to personally always use Locus with a 50MB database and at least 100 enabled tracks and 5000 enabled points... worldwide... no excuses. I can almost guarantee that you would start looking at things differently :-)
Regarding hanging tiles: I just tested "the old way" of hill shading to compare speed & looks by using an online map hill shade overlay from http://korona.geog.uni-heidelberg.de/contact.html . It seems that there is some serious tile hanging going on with Locus overlay maps. At the moment, I do not know if this is related to this beta version or if it is a server issue:
(http://forum.locusmap.eu/index.php?action=dlattach;topic=4963.0;attach=3663)
<provider id="11234" type="0" visible="true" required="false" background="-1">
<name>OSM Layers Uni Heidelberg</name>
<mode>Aster/GDEM Hill Shading</mode>
<area></area>
<url><![CDATA[http://korona.geog.uni-heidelberg.de/tiles/asterh/?x={x}&y={y}&z={z}]]></url>
<zoomPart>{z}-8</zoomPart>
<zoomMin>8</zoomMin>
<zoomMax>26</zoomMax>
<tileSize>256</tileSize>
<attribution>http://korona.geog.uni-heidelberg.de/contact.html</attribution>
</provider>
...played a few more minutes with map overlays & scrolling & zooming (the hillshade layer from last post on top of mapsforge Alps from openandromaps) and had plenty more hanging tiles. Also, Locus Beta crashed on me at least two times. No more time to properly debug right now since I am leaving for the weekend... just posting this so you can maybe look into it a little more before releasing another version. Something is very bogus.
Hi menion
- i delete all srtm data from folder, srtm folder is empty
- i clear cache of Locus Free app
- i start Locus Free/Beta
and now my question an perhaps the solution:
- where get locus info for shading in south west area of my map on ZL9-12, independent shading is enabeled or disabeled? Exactly in this region the problem with hangig tiles appeare.
see screenshot
(http://s12.postimg.org/ck1gej509/Screenshot_2016_03_11_13_03_00.jpg) (http://postimg.org/image/ck1gej509/)
I can confirm hanging mapsforge tiles completely independent of hill shading. Map is from http://www.openandromaps.org/maps/europe/Alps.zip , no overlays, no internal hill shading, no slope coloring, nothing fancy. Tiles are randomly forgetting to be rendered when you zoom in and out frequently. This happens with latest beta and is easily reproducible here.
(http://s29.postimg.org/hzlj303sz/Screenshot_2016_03_11_14_46_30.jpg) (http://postimg.org/image/hzlj303sz/)
Quote from: joeloc on March 11, 2016, 09:04:55
I can confirm some hanging tiles with latest beta... but it looks to me as if only the "hill shading part" is hanging. Is there maybe some separate caching going on for the hillshade layer now?
Yep, small cache for test on background
Quote from: joeloc on March 11, 2016, 09:04:55
As for the hill shade speed... better... but not quite fast enough :-(. Is it really such a bad idea to first render ALL TILES normally and ONLY AFTERWARDS, when the screen is completely filled already, spend any cpu power on shading? You probably think it doesn't make any difference in overall rendering time... but the difference in look & feel & snappiness would be absolutely major. Blank screen staring time is reduced to a minimum.
I already did this some time ago, but results was terrible. Too much threads, too much options, too much already implemented memory/cpu optimizations on one place .... result was always a mess and problems with incorrectly shaded tiles. That's why I'm now doing shading directly on ready-to-display map tile even before it's visible for the first time. So it's now about "I don't want". It's about "I already did it, but first attempt some time ago was disaster".
Quote from: joeloc on March 11, 2016, 09:04:55
Oh... to end with something positive... the brightness/darkness is totally OK now :-).
fine
Quote from: joeloc on March 11, 2016, 09:16:57
This is one way to look at it... and I have a hunch that your own Locus installation is basically similar... almost always almost clean... with just a few tracks and very few points.
Another suggestion, that is probably more likely to give results, would be for YOU to personally always use Locus with a 50MB database and at least 100 enabled tracks and 5000 enabled points... worldwide... no excuses. I can almost guarantee that you would start looking at things differently :-)
Well, my current database waypoint.db - 17 MB, tracks.db - 68 MB. I use it daily, not just behind the desk. Device? Three years old Sony Z1C. Why should I display so much points and tracks around whole world? It's not common case of usage I believe. Every app has it's limits. Well, you already know limits of Locus. Anyway I'm aware that slowdown comes in these cases directly in list of points/tracks. This is probably due to incorrect structure of SQLite database. Quite hard to solve now ... anyway in near future will be maybe needed another conversion of database, same as few years before.
@balloni55: hmm cache for hillshading tiles is stored in private app directory on SD card, usually android/data/menion.android.locus(.pro)/cache/maps/shader/hill. Anyway if you have disabled shading, I'm sure it should not be visible in any case. What about some overlay map or enabled WMS maps?
Quote from: menion on March 11, 2016, 14:49:26
I already did this some time ago, but results was terrible. Too much threads, too much options, too much already implemented memory/cpu optimizations on one place .... result was always a mess and problems with incorrectly shaded tiles. That's why I'm now doing shading directly on ready-to-display map tile even before it's visible for the first time. So it's now about "I don't want". It's about "I already did it, but first attempt some time ago was disaster".
Disaster sounds terrible :-).
Anyway.... what I just did for testing was: Use Locus to download hill shade tiles from the server mentioned above into an offline map. Zoom 13 is enough, the tiles don't seem to be more detailed anyway. I believe the whole alps will fit into 1.5GB at zoom 13. Using this offline sqlite map as a Locus map overlay on top of a vector maps, the results are simply AMAZING:
Reasonably pretty hill shading with almost no delay. The overlay seems to be rendered "independently" from the vector tiles, it appears first, long before the maps forge data is actually rendered. Thats exactly how things should work... giving us a "blank screen time" of nearly ZERO. Locus instantly feels speedy and snappy and fast... I LOVE IT.
Compared to this experience, Locus own hill shading is really only bearable as a last resort :-(.
Yes yes... I know... I compare pre-rendered tiles to custom smartphone magic from raw altitude data... bummer... but seriously:
+ you have the data (hgt).
+ you have the algorithm (beta hillshade prettiness).
- you run it at very unfortunate time in an unfortunate way (blocking tiles, maximizing blank screen time & sluggishness).
Nothing prevents Locus from translating HGT files into sqlite maps right after download (or on first use) automatically and then use the map overlay engine for display. Yes... some minor issues would have to be sorted... like auto-switching the overlay across htg borders... what to do with other overlays... doing the conversion "in the background" without disturbing the user... keep or delete original files... etc... but nothing here sounds unsolvable. And the difference in usability compared to the current "realtime render" implementation could not be greater. IMHO, this is the only proper way to proceed... unless you magically find a way to speed up the shading algorithm by two orders of magnitude or implement 100% bitmap caching of every single rendered shading tile at every zoom level. A few percent here and there won't do...
Sorry for always having such strong opinions :-).
Quote from: menion on March 10, 2016, 09:18:26@gynta: hmm really nice issue. It's there also in latest public version and this issue should be there since exists shading. Problem is that on that tile are no data in vector map. Result is empty tile and well .. no shading.
hm ok but what about missing tiles on vector maps?
-> https://www.dropbox.com/s/n29z3t17pf5exm0/clip0433.avi?dl=0
editLocus caching vector maps?
whatever - clear locus data in system helps*
(http://s9.postimg.org/c9i1ijcbv/2016_03_11_180425.jpg) (http://postimg.org/image/c9i1ijcbv/)
*)
hint: backup your settings
Update for usage of external SD card under KitKat - SRTM in particular
Hi all,
following the guidance from
http://docs.locusmap.eu/doku.php?id=manual:faq:use_sdcard_on_kitkat&do=login§ok=ea111e6e0396dfbd1215ceb613941744
option C like, I have the working directory on the internal SD, except the vector maps on external SD card in /LocusMapsVector, and the SRTMs next to those.
Adding elevation files on the fly has been a mess, though! Always need to switch to default, download, then copy to external SD by the Samsung File Manager (only one that can do that on non-rooted device).
Today I tried something new (new at least for myself): leaving all critical working directories on internal SD, leaving the vector maps in their place. But I moved the SRTM directory to the /Android/data/menion.android.locus.pro/files.
I have been delighted that this gives me what I want: working data on internal (safe place in case of de-install), vector maps on safe place on external SD. And R/W access for SRTM on external SD (with loss risk, though).
Most of latest posts were focused on hillshading as well as my work over weekend. I believe your push was successful and you all will find hillshading nice looking and also fast enough, in current new 3.16.0 version. Enjoy it.
And @michaelbechtold: KitKat is worst in this case and I'm glad you find useful solution ;). Damn SD card access ...