hi Marco13.
The problem was solved when I manually set geometricError and boundingVolume to child subtrees in tileLoad event. This at least means that there will be problems when the geometricError、 boundingVolume of the child subtrees and tile are inconsistent. Looking forward to adding this feature to child subtree metadata in the future?
Finally thank you and Cesium Team
This should not be necessary. And I’d like to emphasize the possible drawbacks of this approach: When you load a different tileset, or a tileset where these values are supposed to be read from the tile metadata, then manually setting these values may lead to wrong or unexpected results.
(It might be acceptable in your case, or a reasonable workaround for a first test. But let’s hope that the reason for the unexpected behavior can be found soon. We’re actively working on the validation of subtree data, and I’ll schedule to create an example in the 3d-tiles-samples repository that actively uses implicit tiling with tile metadata. Again, it’s hard to give a timeline, but we are aware that there is a demand for that by people who want to implement this functionality)