Thanks everyone, always nice when community is being so active in testing!
Cruiser GL has different map style than Kurviger, rendering more map data.
So seems that in very high resolutions (> FHD) the OSM nature polygon layers (under Vegetation in Kurviger) have rendering performance problems at small zoom levels.
Hi, just did a quick test: at full 3040 resolution it does not freeze up anymore however panning and zooming is still not very smooth, just acceptable i would say. The map is not pretty though, roads are very thick. I much prefer the cruiser map look. Will try to add screen shot below.
Would be difficult to apply extreme simplifications globally targeting only some
heavy countries or large resolutions, as it will affect in a negative way all maps.
Some compromises are necessary, still it’s nice there are not stops in use anymore.
Will think what else can be done in map engine or specially in such heavy map files.
Please create a separate topic for the map style appearance.
I’d like thinner lines too, but more users have to agree to that.
Perhaps open external map styles, so users can modify them?
Panning with offline maps at 3040 + hillshading + vegetation on gives “refresh rate” of 2~3 frames per second, which is OKish, better then I reported earlier today, and at least better than a Garmin zumo :).
However, the online maps provide a way smoother experience.
Interesting: opening the menu goes with the same “slow” 2 frames per second when offline maps are loaded. But with online maps activated, the menu is super smooth. Why is this? Should be a clue in here?
Because of the (in my opinion ugly) maps in Kurviger I again tried Cruiser at full 3040 resolution. Actually it DOES pan quite smooth, smoother than Kurviger Beta. Only panning to "new not viewed before parts of the map on overview zoom level shows slow (0.5 to 1 s) loading map tiles. After loading it is smooth panning again. Also the menu stays smooth, why is this? And why not use the Cruiser map “engine” (?) in Kurviger?
Different technologies, VTM is more modern with OpenGL acceleration, map rotation / tilt, etc.
But the fundamental reason for the problem here is not the engine, but the map data at those areas.
They should have categories per importance / size and not all nature data thrown together with same tags… then how map makers are supposed to filter them?
By the way would expect that GPU on such modern phones to be able to handle anything.
But then many phones with >FHD resolution, fall back to FHD for games, here is the answer.
VTM more modern? Cruiser GL does not handle 3040 resolution at all.
Cruiser is OK at 3040 and very ok at 2280, and looks good.
I would like to have the Kurviger route planner in Cruiser, or the Cruiser map experience in Kurviger.
Is this not possible somehow?
Thx.
Also bitmap maps are faster as they are pre-rendered on server.
Also online routing is faster than offline routing for same reason.
Does that make them more modern? Not really, if prefer online.
Not sure, but it seems that there is a technical issue that roads are rendered too thick on @Teun’s device? The regular Kurviger map rendering is thicker roads compared to the default VTM theme to make it easy to identify roads during navigation.
The netherlands map seems to be very demanding on the device.
There my phone also slows down to a frame rate of ~2-3 fps (with vegetation on).
And even the menue becomes slow when I view netherlands.map
Turning vegetation off makes a big difference here.
@Teun try panning around in the south German/Austrian area
BTW
Netherlands at similar zoom level as above looks “normal” here settings | about | info
Kurviger Pro 1.11.6
Android 8.0.0 (API 26)
samsung SM-G930F
1080 x 1920 (480 dpi)
Google location on
This will help: I just discovered that I only get the thick roads when increasing resolution from lower to 3040 WITHOUT restarting the app. When I close and restart Kurviger, it looks normal again. Sorry if I caused confusion.