-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Custom tileset rendering error #8678
Comments
Can you provide the style with custom tileset you're using? |
Style URL: mapbox://styles/patrickzenker/ciuton0ty00yv2hpbjgv5l4df |
Thank you -- I was able to easily reproduce the issue with your style. The cause of the aliasing seen around the edges of the opaque portions of the raster layer is that tiles from lower zoom levels are being rendered underneath the desired tiles. These low zoom tiles are overzoomed for rendering, producing undesired artifacts. You can see this more clearly when turning on tile borders: These lower zoom tiles are loaded by an overly-aggressive tile loading algorithm, which is detecting that some tiles cannot be loaded at the desired zoom (because they are outside of the bounds of the raster source and don't exist), and loads lower zoom tiles in an effort to fully cover the visible area. This is a bug; we'll need to either adjust what tiles are loaded in this situation or ensure that we clip out child tiles when rendering the lower zoom tiles. cc @kkaefer |
Might be addressed by #5394. |
Fixed by #9468. |
With
I still got the issue with Android (and iOS with latest version too). Am I doing something wrong when I convert my images to MBTiles (to upload them into Mapbox Studio)? If I watch the style with Mapbox Studio everything is fine. Update: With @5.2.0-beta.1 this issue is gone. |
Hey,
i've got a rendering error on several zoom levels with the latest SDK version (5.0.2).
With SDK version 4.2.0 I had no problems and if I style my Mapbox map everything looks fine (like the first screenshot).
Platform: Android
**Mapbox SDK version: 5.0.2 **
Steps to trigger behavior
Use a custom tileset
Expected behavior
Sharp maptiles on every zoom level like this:

Actual behavior
Black rendering boxes?


The text was updated successfully, but these errors were encountered: