-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rendering sometimes stops in Nautical view with Depth contours #20857
Comments
|
@RZR-UA please reproduce as long line issue is fixed now |
The simplest way to reproduce this issue is to zoom in to level 15 at the ocean near Lisboa and keep Nautical depths enabled (Europe Contours + World Contours maps). The problem is that contour lines in binary map objects are bloated (long and highly detailed at the same time). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Hi,
I've noticed that in the nautical view once you enable depth contours the rendering becomes very slow and sometimes just stops rendering tiles alltogether. This has been going on for a few updates now (I've seen the same behaviour on 4.7 and 4.8)
This seems strange as my device has no trouble rendering much more complex contour lines for standard elevation.
While looking at the logcat data, there was around 3000 errors like so:
Steps to reproduce
go the the Nautical view profile (boat profile), download and enable the Depths contours in the settings, span, zoom and roam around the map, notice the slowdowns and errors in displaying the tiles.
Actual result
Rendering in general is much slower than other profiles, and notice at the end that osmand stops rendering tiles alltogether (and required a restart to start functioning again). The screen was responsive, you could span around and interact with the UI but no map was loading
screen-20240916-110518_H.264.mp4
Expected result
Rendering is smooth and doesn't stop loading tiles.
Your Environment (required)
WARNING Crash-Logs MAY contain information you deem sensitive.
Review this CAREFULLY before posting your issue!
The text was updated successfully, but these errors were encountered: