What is the working principle of loading, how to reduce the range of tiles I see, I only need to load in my field of vision, can I modify the source code to achieve
We’ve discussed internally the possibility of allowing the user to customize how and where tiles are loaded in this kind of way, but for the time being you’ll have to modify cesium-native to implement these changes. Specifically, look at Cesium3DTilesSelection::Tileset::_visitTileIfNeeded. This is the method that performs tile culling, and you can add new culling steps or modify the behavior of the existing frustum and fog culling steps to achieve your goals!
need to compile the source code first for cesium-native?
I only want to render the field of view tiles, how do I modify this
Yes, you’ll need to compile cesium-native. You can take a look at the developer setup guide for Cesium for Unreal to see how to get it building locally. Though if all you’re looking to do is render tiles within the field of view, that’s what the default algorithm should do - it renders tiles within the view frustum. Is there some other kind of behavior you’re trying to get it to support?
1 Like
I did make some optimizations in the source code, but I wanted to ask this “OrientedBoundingBox” What range of boxes is it？
I’m not sure I understand your question. Are you referring to the tile’s bounding volume?
yes, i dont know how to work?