This object is in archive!
Map rendering with hill shading too slow
Solved
Hello, I recently updated Locus Map Pro to a new version 3.16.0, now i noticed I cannot use hill shading any more, because the map renders too slow in this new version on my device (Galaxy S3, offline vector map Germany). It takes up to 30 seconds until all tiles on the screen are rendered. Is there a way to get the old hill shading back? Any idea how to improve the speed?
Regards
Sebastian
The same problem 
Good day Sebastian,
is same "slowness" happen in all zoom levels? What HGT files are you using, the one downloaded directly over Locus together with map or big 1'' files?
Unfortunately there is no way back anyway basic hillshading should be almost equally fast as before. Anyway 30 seconds is way too much for some high zoom levels, but it's possible that it's so slow for 1'' files in zooms around 12, 13. This should be improved in next version little bit.
Good day Sebastian,
is same "slowness" happen in all zoom levels? What HGT files are you using, the one downloaded directly over Locus together with map or big 1'' files?
Unfortunately there is no way back anyway basic hillshading should be almost equally fast as before. Anyway 30 seconds is way too much for some high zoom levels, but it's possible that it's so slow for 1'' files in zooms around 12, 13. This should be improved in next version little bit.
I had not heard of HGT files yet, I just downloaded the data via Locus. When zooming out it is slower and takes up to 50 seconds. When zooming in to a point where I see 1-4 villages, it is a bit faster (20 seconds). The strange thing I found out now: In some areas the tiles render almost instantly with shading, but when scrolling over an "invisible border" the rendering becomes extremely slow. Going back to the first location: fast again. Going back to the second location again: slow again. That's really strange.
I had not heard of HGT files yet, I just downloaded the data via Locus. When zooming out it is slower and takes up to 50 seconds. When zooming in to a point where I see 1-4 villages, it is a bit faster (20 seconds). The strange thing I found out now: In some areas the tiles render almost instantly with shading, but when scrolling over an "invisible border" the rendering becomes extremely slow. Going back to the first location: fast again. Going back to the second location again: slow again. That's really strange.
Sebastian, only method I may do something with most of issues, is to simulate same issue on own device. Unfortunately "first area", "second area" etc. is useless here. Please write me more about which map you currently use, zoom level value, coordinates from where I should start scroll to which direction, which coordinates. So I may simulate exactly same situation as you have. Thanks for understanding.
Sebastian, only method I may do something with most of issues, is to simulate same issue on own device. Unfortunately "first area", "second area" etc. is useless here. Please write me more about which map you currently use, zoom level value, coordinates from where I should start scroll to which direction, which coordinates. So I may simulate exactly same situation as you have. Thanks for understanding.
Ok I'll try to give you an example. Locus Map Germany North, zoom level 14 from N54°23.867' E9°48.383' (smooth) going east, it gets very slow when I reach about N54°24.063' E9°57.383'
Ok I'll try to give you an example. Locus Map Germany North, zoom level 14 from N54°23.867' E9°48.383' (smooth) going east, it gets very slow when I reach about N54°24.063' E9°57.383'
Another example, zoom level 13: Going north from N51°48.710' E9°39.031' (smooth) to N51°55.314' E9°38.796' (slow)
Edit: Third: Going west, zoom level 13, from N52°35.344' E12°12.733' to N52°35.353' E12°02.398'
Another example, zoom level 13: Going north from N51°48.710' E9°39.031' (smooth) to N51°55.314' E9°38.796' (slow)
Edit: Third: Going west, zoom level 13, from N52°35.344' E12°12.733' to N52°35.353' E12°02.398'
My 2c: when you find the srtm folder (that is where the hgt files with the elevation information sit) under /locus/data (via a file manager app), then sort by date/time, reverse order, and make a screenshot of those hgt files. incl. their time stamps for Menion. Then sort by name and show the files around N49...hgt, N50..., N51. N52, N53 with another scvreenshot.
My 2c: when you find the srtm folder (that is where the hgt files with the elevation information sit) under /locus/data (via a file manager app), then sort by date/time, reverse order, and make a screenshot of those hgt files. incl. their time stamps for Menion. Then sort by name and show the files around N49...hgt, N50..., N51. N52, N53 with another scvreenshot.
No sure if screenshot helps here. I'm testing what you wrote. Moving from N54°23.867' E9°48.383' to east is just on border of N54E009.hgt and N54E010.hgt files. So I may only suggest to check if these two files are in Locus/data/srtm directory. With some online MapQuest map or other offline map, issue is same? What about vector map without shading, no problem?
No sure if screenshot helps here. I'm testing what you wrote. Moving from N54°23.867' E9°48.383' to east is just on border of N54E009.hgt and N54E010.hgt files. So I may only suggest to check if these two files are in Locus/data/srtm directory. With some online MapQuest map or other offline map, issue is same? What about vector map without shading, no problem?
I tested with a different Germany offline vector map and with Mapquest Classic online, same problem. With shading disabled there are no problems. Should I delete the HGT files and download them again?
I tested with a different Germany offline vector map and with Mapquest Classic online, same problem. With shading disabled there are no problems. Should I delete the HGT files and download them again?
You may try it, anyway if there should be an problem in file, it should not work at all. Weird ...
Anyway if it won't help, suggest to wait on next version (probably tomorrow). I did some more improvements, so may it will help a little bit here.
You may try it, anyway if there should be an problem in file, it should not work at all. Weird ...
Anyway if it won't help, suggest to wait on next version (probably tomorrow). I did some more improvements, so may it will help a little bit here.
I re-downloaded the map and hgt files, but the problem is still there. I now found out that it occurs regularly when scrolling the map. This means smooth -> very slow -> smooth -> very slow when scrolling in one direction. Maybe every time the app needs to access more than one of these hgt files at once?
I re-downloaded the map and hgt files, but the problem is still there. I now found out that it occurs regularly when scrolling the map. This means smooth -> very slow -> smooth -> very slow when scrolling in one direction. Maybe every time the app needs to access more than one of these hgt files at once?
Good day Sebastian, did you please tried shading with latest Locus Map version 3.16.1? I hope it will be better now.
Good day Sebastian, did you please tried shading with latest Locus Map version 3.16.1? I hope it will be better now.
Hello. I tested the map with hill shading enabled and the new version seems to be faster. Thank you very much! When scrolling, the "invisible borders with extreme loading time" seem to have gone. Generally here is what time it took to load a full screen of tiles (in seconds, not totally exact):
With shading:
Level 9: <10s, level 10: <7s, level 11: <5s, level 12: <3s, level 13+: <1s
Without shading:
Level 9: <6s, level 10: <3s, level 11: <2s, level 12: <2s, level 13+: <1s
Hello. I tested the map with hill shading enabled and the new version seems to be faster. Thank you very much! When scrolling, the "invisible borders with extreme loading time" seem to have gone. Generally here is what time it took to load a full screen of tiles (in seconds, not totally exact):
With shading:
Level 9: <10s, level 10: <7s, level 11: <5s, level 12: <3s, level 13+: <1s
Without shading:
Level 9: <6s, level 10: <3s, level 11: <2s, level 12: <2s, level 13+: <1s
Good day Sebastian, sounds good, perfect. I still have some places that
should be improved (to reduce required time), but this later. For now, I think that case closed.
Good day Sebastian, sounds good, perfect. I still have some places that
should be improved (to reduce required time), but this later. For now, I think that case closed.
Thanks again :)
Thanks again :)
Replies have been locked on this page!