Skip to content
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

Open
Guylby opened this issue Sep 17, 2024 · 4 comments · May be fixed by osmandapp/OsmAnd-core#812
Open

Rendering sometimes stops in Nautical view with Depth contours #20857

Guylby opened this issue Sep 17, 2024 · 4 comments · May be fixed by osmandapp/OsmAnd-core#812
Assignees
Milestone

Comments

@Guylby
Copy link

Guylby commented Sep 17, 2024

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:

09-16 11:14:17.385 10054 10054 W System.err: Rendering attribute route is not found !
09-16 11:14:17.494 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.494 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.494 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.494 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.494 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.494 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.494 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.494 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.494 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.494 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.495 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.496 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.496 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.496 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.496 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.496 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid
09-16 11:14:17.496 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is invalid

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!

OsmAnd Version: 4.9.0
Android/iOS version: 13
Device model: Sony Xperia 10 III
Crash-Logs: ?
@vshcherb
Copy link
Member

vshcherb commented Sep 24, 2024

  • Fix freezes
  • Extra task: output error line fix net.osmand.core:native: Path effect (1) with 1 intervals is invalid it's likely not related to rendering issue

@vshcherb
Copy link
Member

vshcherb commented Nov 5, 2024

@RZR-UA please reproduce as long line issue is fixed now

@RZR-UA
Copy link
Contributor

RZR-UA commented Nov 7, 2024

It is easily reproduced in the Android Studio Emulator:

Just load maps, enable Nautical style and Nautical depths (contours) and play with Zoom in/zoom out at the location near Lisbon. The Map of Portugal is not required for reproduction. Location to zoom in/out: 38.91718° N, 10.56903° W

PS. 09-16 11:14:17.494 10054 10258 W net.osmand.core:native: Path effect (1) with 1 intervals is in was absent in my logs

pt.mp4

@Andrewschenko
Copy link
Contributor

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).

@vshcherb vshcherb modified the milestones: 5.0-map, 5.0-backend Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants