What would happen with the Unity Cesium Package if Google decided to ship the 3d tiles with double the resolution and double the polygons overnight for example?
I know you guys work with them and know everything beforehand, but how would performance be on an Android app that’s already running at 60 fps in this imaginary case ?
Is the Cesium Package for Unity even going to work in this scenario ?
Finally, if it would work, what optimisations could there be made ?
Hi @Your_RainBoy,
This would probably depend on various factors, including how geometric error is assigned to the tiles, and how much 3D data is included per tile. Cesium for Unity would still work, but the quantitative increase in 3D data might affect how the highest level of detail is loaded.
Still, there are settings on Cesium3DTileset that you can use to massage performance! This includes:
- Maximum Screen Space Error. Lower values = higher levels of detail being loaded, and vice versa
- Maximum Cached Bytes. Decrease this value for devices with less memory (particularly for mobile)
- Maximum Simultaneous Tile Loads. Determines how many tiles are processed at the same time, decrease if necessary.
You can also Enable Frustum Culling to cull tiles that are out-of-view, and disable the Preload Ancestors or Preload Siblings settings.
I hope that helps! Let us know if you have any follow-up questions.