CesiumGS
Erroneous "Tile has a bounding volume that does not include all of its content" with Mercator quantized-mesh terrain
As reported here: https://community.cesium.com/t/warning-tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/25460
Hello @kring ! We tested another 3D Tiles : https://ctod.beta.geodan.nl/tiles/layer.json. We're using the 1.7.1 cesium unity. We have the same problem as declared in the issue above, did you find any solution ?
No we haven't specifically addressed it. Are you seeing any actual problem, or only an annoying message?
https://github.com/sogelink-research/ctod/issues/16
Hey I am getting the "Tile has a bounding volume that does not include all of its content, so culling and raster overlays may be incorrect" warning as shown in the output window for terrain tiles 0/0/0.terrain and 0/1/0.terrain and 1/2/1.terrain and because of that I am not able to see the globe correctly as shown in the pic 2 and pic 3. after some zoom level tile completely disappear and it shows artifact where imagery is stitching.
Hi, Same problem here, we're using the latest Cesium-Unity version, and sometimes tiles are missing and the log file is full with the "Tile has a bounding volume that does not include all of its content" notification 😔 @kring any update?
@asafMasa (and anyone else seeing this message), please tell us a bit about the tileset you're using when this happens. This message could be caused by a bug in cesium-native, particularly with quantized-mesh terrain with a Mercator projection. However, it perhaps more frequently indicates a problem with your tileset, not a bug in cesium-native. You can use the 3d-tiles-validator to see if there's a problem with the bounding volumes in your tileset.
@kring In my app (Unity), sometimes I receive the following message while loading WMTS layer with terrain (not from 3dtiles).
"[TilesetContentManager.cpp:476] Tile has a bounding volume that does not include all of its content, so culling and raster overlays may be incorrect: https://*****.terrain?v1.1.0&extentions=octvertexnormals upsampled ..."
and as a result the tile is empty... same as above...
But it's inconsistent as when I refresh the app, the same tiles are shown..
Do you know why?
So @asafMasa you have a WMTS server that is serving up quantized-mesh .terrain files? Presumably along with a layer.json? If so, and if that terrain is using the Web Mercator projection, then you are indeed most likely running into this bug. A possible workaround in that case is to serve your data in a Geographic projection instead of Web Mercator.