- Welcome to Locus Map - forum.
Locus Map - forum
Recent posts
#1
Troubles & Questions / Re: Higher memory usage (possi...
Last post by Menion - Today at 09:22:01Hmm, consumed memory itself is not a problem. The problem is if this slows down your system and the app.
Is this still happen to you? And still even only during common usage as moving an OAM (TOTM theme) map and nothing special. No recording, no navigation, live tracking, etc?
I made many 3-hour tests with various parameters and even basic movement of the map in zoom level 16 cased no problems. Maybe I should try also OAM maps and this specified theme ...
Is this still happen to you? And still even only during common usage as moving an OAM (TOTM theme) map and nothing special. No recording, no navigation, live tracking, etc?
I made many 3-hour tests with various parameters and even basic movement of the map in zoom level 16 cased no problems. Maybe I should try also OAM maps and this specified theme ...
#2
Locus Map / Re: [APP] - version 4.23.+ ( 0...
Last post by Menion - Today at 09:13:32@Andrew Heard
you still have some problems with installation .. sorry, but nothing has changed in the way how I generate apk files. No idea, sorry ...
Impossible to hide an empty bottom panel in the route planner > yes, it is an intent.
Crash when going online/offline > I think I've got it. You have edited one shared track and a moment later deleted it (probably). The app still tries to work with edited shared track, but it has already been deleted. I'll publish the fixed Beta tomorrow.
@T-mo
full-screen > do not use it, if it does not work. It is a hacky unreliable system. That's why it was removed and will not come back. Thanks for understanding.
you still have some problems with installation .. sorry, but nothing has changed in the way how I generate apk files. No idea, sorry ...
Impossible to hide an empty bottom panel in the route planner > yes, it is an intent.
Crash when going online/offline > I think I've got it. You have edited one shared track and a moment later deleted it (probably). The app still tries to work with edited shared track, but it has already been deleted. I'll publish the fixed Beta tomorrow.
@T-mo
full-screen > do not use it, if it does not work. It is a hacky unreliable system. That's why it was removed and will not come back. Thanks for understanding.
#3
Troubles & Questions / Re: Magnetic/program compass a...
Last post by Menion - Today at 08:47:29Hi,
it should be most probably affected by the "True bearing" settings. Check the app's Settings > GPS & sensors > Use true bearing and disable this option in case, you want to get identical results to your physical compass.
it should be most probably affected by the "True bearing" settings. Check the app's Settings > GPS & sensors > Use true bearing and disable this option in case, you want to get identical results to your physical compass.
#4
Troubles & Questions / Re: Hiding map bounds box
Last post by Menion - Today at 08:44:21@Jakice , what version are you using? Regular from the Google Play?
#5
Troubles & Questions / Re: Hiding map bounds box
Last post by Jakice - Today at 00:44:30There are no borders on the maps, they are generated from map tiles and are in a Rmap database.
#6
[DE] - deutschsprachiger Forumsbereich / Re: Wie Entfernung zum nächste...
Last post by tobser - Yesterday at 22:46:24Hallo
Das kommt dem was ich möchte schon sehr nahe. Kurze Frage: wie setzt man einen Shaping-oder Via-Punkt? Geht das in der Locus-App? Einfach einen Punkt in die Route setzen oder anders?
Grüße von Tobias
Das kommt dem was ich möchte schon sehr nahe. Kurze Frage: wie setzt man einen Shaping-oder Via-Punkt? Geht das in der Locus-App? Einfach einen Punkt in die Route setzen oder anders?
Grüße von Tobias
#7
Troubles & Questions / Re: Hiding map bounds box
Last post by michaelbechtold - Yesterday at 17:21:17I just tested with a Discovery_Walking_Guides map and can tell you that you can be lucky with your view.
Above map has a solid white border, all legends - like a scan of a paper map. Which definitely is not created by Locus, but rather integral part of that map itself.
Can you test your case by displaying one of your maps exclusively, alone (i.e. no overlay mechanics of any kind) and check how it looks like at its border.
If there is such border like in your screenshot, then it would smell like my experience with DWG maps - only "nicer" ...
Above map has a solid white border, all legends - like a scan of a paper map. Which definitely is not created by Locus, but rather integral part of that map itself.
Can you test your case by displaying one of your maps exclusively, alone (i.e. no overlay mechanics of any kind) and check how it looks like at its border.
If there is such border like in your screenshot, then it would smell like my experience with DWG maps - only "nicer" ...
#8
Troubles & Questions / Magnetic/program compass and a...
Last post by 8850 - Yesterday at 13:04:21Where does the error lie? What am I doing wrong? Why are LocusMap maps showing the wrong azimuth?
I am standing on a hill, LocusMap shows to the second hill azimuth in a straight line of 250 degrees. The compass in LocusMap shows a different azimuth - to the second hill as much as approx. 263-282 degrees. Smartphone is level vertically and horizontally. The compass built into the smartphone's firmware shows the same value as the compass in LocusMap. I aim through the magnetic physical compass in my hand and it shows the same value as the smartphone's compass. Why are LocusMap maps showing the wrong azimuth? The difference varies from 10 to 25 degrees of azimuth despite accurate aiming.
LocusMap Silver 4.21 (offline openstreet map - www.openandromaps.org)
GPS excellent signal (Glonass, Baidu, Gps).
Xiaomi Note 10 PRO smartphone
Physical compass on the hand made in Ukraine
OruxMap app also shows a different azimuth on the map to the destination than the built-in compass
I am standing on a hill, LocusMap shows to the second hill azimuth in a straight line of 250 degrees. The compass in LocusMap shows a different azimuth - to the second hill as much as approx. 263-282 degrees. Smartphone is level vertically and horizontally. The compass built into the smartphone's firmware shows the same value as the compass in LocusMap. I aim through the magnetic physical compass in my hand and it shows the same value as the smartphone's compass. Why are LocusMap maps showing the wrong azimuth? The difference varies from 10 to 25 degrees of azimuth despite accurate aiming.
LocusMap Silver 4.21 (offline openstreet map - www.openandromaps.org)
GPS excellent signal (Glonass, Baidu, Gps).
Xiaomi Note 10 PRO smartphone
Physical compass on the hand made in Ukraine
OruxMap app also shows a different azimuth on the map to the destination than the built-in compass
#9
Troubles & Questions / Re: Hiding map bounds box
Last post by Jakice - Yesterday at 13:02:06Here is a screenshot of the boxes I would like to hide. Thanks.
#10
Locus Map / Re: [APP] - version 4.23.+ ( 0...
Last post by Tapio - Yesterday at 10:19:04Quote from: Andrew Heard on May 17, 2024, 17:04:06Has anyone else experienced this?Not a problem here.