You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the latest nightly (4.9.0#3211m, released: 2024-09-17),
the gpx track line is not shown on the map, while the split-interval numbers are correctly displayed.
The track is possibly rendered behind some layers, but I could not figure out which ones because disabling all the overlays (3D relief, contour lines, etc.) did not make the track appear.
Steps to reproduce
Import a new gpx file: no track is displayed on the map
On appearance, set split interval 500m and colour red: red numbers appear, but the track is still invisible
Click edit track: the whole track appears as a dashed line (so the gpx is correctly recognised by the app)
Actual result
It is not possible to follow the gpx track
Expected result
The track should be displayed on top.
It happened in a previous version (few days ago) that the track customisation was lost upon closing/reopening the app, possibly related to what described in the following, so the issue may be caused by very recent changes to the rendering code. #20855
The bug has been reproduced. To reproduce it, create a track and view it on the map.
You'll notice that the track line is missing; only the icons, including the start and finish points, are displayed on the map.
Description
In the latest nightly (4.9.0#3211m, released: 2024-09-17),
the gpx track line is not shown on the map, while the split-interval numbers are correctly displayed.
The track is possibly rendered behind some layers, but I could not figure out which ones because disabling all the overlays (3D relief, contour lines, etc.) did not make the track appear.
Steps to reproduce
Actual result
It is not possible to follow the gpx track
Expected result
The track should be displayed on top.
It happened in a previous version (few days ago) that the track customisation was lost upon closing/reopening the app, possibly related to what described in the following, so the issue may be caused by very recent changes to the rendering code.
#20855
Your Environment (required)
The text was updated successfully, but these errors were encountered: