First off, thank you for all the work on Cesium — it’s such a pleasure to use this amazing tool. The possibilities feel endless, and I keep finding new ways to explore and experiment every day, so thanks again!
I’ve noticed some incorrect tile rendering behavior when using SceneMode.SCENE2D. As shown in the attached screenshot, certain tiles are not rendered at the same zoom level.
This issue is easy to reproduce with any of the Sandcastle examples on the Cesium site (e.g. Cesium Custom DataSource).
Does anyone know if there’s a way to address this, or if it’s a known limitation?
Thanks for your post and for being part of the Cesium community. ImageryProvider classes in Cesium request tiles at specific LODs based on x, y and level of the camera.
It looks like the loading behavior is consistent between 2D and 3D, when I switch the SceneMode to SCENE3D for the example you referenced above.
Is there a specific use case you have in mind for which you are seeking better consistency in the zoom level of tiles - like potentially rendering out a scene?
Thank you for the quick feedback. Yes, I’d like to use both 3D and 2D maps for routing. However, in some cases we lose information because of the inconsistency in tile zoom levels.
I’ve taken a couple of screenshots where parts of the route are missing details — either roads or labels — due to this behavior.
Is there a workaround to ensure a consistent zoom level across all tiles?
