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
You can get too many labels drawn that quickly disappear in fraction of second, but it looks ugly
Expected Behavior
I will not post images, as number of labels thins out obviously when tried.
Actual Behavior
I have achieved even worse results with my own data and style:
I guess this is example is overblown because data in .mvt contains too much data for that zoom level, but as this can be reproduced in streets-v9 i am posting it.
When used map.showCollisionBoxes = true it seams to me that collisions are ignored while labels are outside of visible rectangle, but then when panning occurs labels are drawn before collisions are reevaluated.
The text was updated successfully, but these errors were encountered:
The "skip fade" logic is actually for items that have been placed/collided, just while they were offscreen. It looks like what @watbywbarif is seeing is features entirely outside the collision index range getting placed, and then sticking around until the next placement happens (it'll happen as they get pulled on screen, but it takes time for them to fade out so you can still see all the overlap for a bit). That's actually a known issue (#5654) that we hadn't gotten around to fixing yet just because it didn't seem like it was too big a problem. Getting this report is a good incentive to re-evaluate that. 😅
0.44.2 but then reproduced this with official streets-v9 and older 0.43.0:
Steps to Trigger Behavior
Expected Behavior
I will not post images, as number of labels thins out obviously when tried.
Actual Behavior
I have achieved even worse results with my own data and style:
I guess this is example is overblown because data in .mvt contains too much data for that zoom level, but as this can be reproduced in streets-v9 i am posting it.
When used
map.showCollisionBoxes = true
it seams to me that collisions are ignored while labels are outside of visible rectangle, but then when panning occurs labels are drawn before collisions are reevaluated.The text was updated successfully, but these errors were encountered: