1. every selected theme render different tiles. So there should be separate cache for every theme (this is crazy) or Locus should automatically delete all cached tiles when theme is changed

2. when auto-loading is enabled, many map tiles are firstly rendered from single maps and later for any additionally loaded. Anyway when map tiles will be cached, Locus do not know, which already cached tiles this new loaded map cover. So caching of vector tiles + auto-loading is really pain ...

so please, take this topic more as discussion. I personally do not agree with vector map caching. My opinion is "use vector maps without caching. If you device is too slow, sorry - wait or don`t use". Anyway if all three points above will have good explanation, I as usually say "never say never"

Re. 1) I come from a very practical view, hence I am fully with you that a sophisticated cache management is overkill. When I am on a hike or a trip, I typically have one scenario (street, mountain, ...), which does not switch every 10 mins. So having the cache deleted when Theme switches is a logical and sufficient step I feel

Re. 2) this may depend on the coding of the tile file names. If you encode the name by geographic coordinates of the resp. tile, then you can completely ignore which map they came from

- People could even argue that SD cards are cheap enough today to have a new one every year

- Smartphone characteristics are very different

- SD card speeds and sizes are very different

- Personal preferences and tradeoff assessments are very different

Adding a switch for vector map cache on/off (default on), and the max level (default 10) empowers the users to follow their believes and taste and needs, and ends diverging discussions with you in the middle ;-)

Hello, I think that added the option to enable cache or not, by default it should be disabled, not to alter the current operation. If someone wants to test whether improved performance in your device, you have to enable it.

ad 1.: as I already mentioned caching must be per theme, why is this crazy? It`s strictly logical

ad 2.: I think we`re talking here about vector maps only, nothing else. The cached tiles should cover a certain area _independent_ of the current map. A user would anyway only see the tiles of one map in an area which is covered by more than one map.

ad 3.: As Peter wrote in the initial post, it`s about caching of map tiles in low zoom levels. I personally would set the limit somewhere in the range of zoom level 9 which would result in I think less than 100 tiles for Germany. How much space would that make? I think not too much. Zoom levels below that would cost even much less. Dependent on people`s need (some only use the vector map only in a local area), others may like to get an overview over thousands of kilometers the max zoom level for caching can be configured.

I hope something like this can and will be done soon because for high zoom levels Locus reached now a "good" speed in rendering but for low zoom levels rendering still feels like ages.

yes, sure, I have recent files in this folder. And from load times I can confirm that zoom 10 and below are fine, once you have been there, but level 11 to 12/13 are problematic and annoyance, even on a Galaxy Note.

Depending on device type and theme you use, up to level 12 is slow and 13 not really fun, so caching makes sense fo those for sure. But again - GIVE IT A SETTING, SO EVERYBODY CAN DECIDE HER/HIMSELF !

When it comes to the lower levels, the best solution is either optimized vector maps for overview only (Menion mentioned that) or you can have the whole world on a tile DB in 1.4 GB at level 10. Again, people should have the choice to switch to a generic map of whatever kind at a level they can define.

In summary: alternate map (vector or tiles DB) for the lower levels, caching at medium levels. Total of 3 additional parameters. End of religious discussions.