I’m debugging a custom 3D Tiles 1.1 QUADTREE tileset in CesiumJS that shows visible gaps/holes unless the geometricError values are set extremely high.
This is a custom-generated tileset (not Cesium ion output) using:
-
3DTILES_bounding_volume_S2 -
QUADTREEimplicit tiling -
.glbcontent -
.subtreefiles -
REPLACErefinement
The configuration that renders best so far has:
-
top-level
geometricError: 99999999 -
root
geometricError: 99999999 -
child
geometricError: 99999999
I also tested by commenting out my custom CesiumJS tileset viewer settings, and the gap behavior was basically unchanged, so this seems more like a tileset-generation / hierarchy / geometricError issue than a viewer-setting issue.
Questions:
-
Is needing extremely large
geometricErrorvalues a sign something is wrong in the tileset hierarchy? -
For an implicit QUADTREE tileset like this, what would a more reasonable
geometricErrorsetup look like?
