1. A concise explanation of the problem you're experiencing.
Hi, We are trying to publish a city environment in cesium using 3DTiles. We have tried firstly to create a single 3DTiles file using only buildings (not including surface). Total file size of our 3DTiles is about 100 MB and contains about 27000 buildings. Our first tests on local Apache server is not bad, but it is not well optimized for internet usage. http://nrw.virtualcitymap.de/ is a good sample for optimizing a 3D city model and dividing (i guess its called as culling) a city into 3DTiles. Also we want to make a similar app using 3DTiles children and grant-children elements.
3. Context. Why do you need to do this? We might know a better way to accomplish your goal.
We need to publish 3DTiles on web without any performance decrease. Do you suggest any standard size for culling 3DTiles for large cities? (For exp. we are trying now a 500 x 500 meters 3Dtiles with 2000 x 2000 meters parent content.)
4. The Cesium version you're using, your operating system and browser.
Cesium version 1.39 on Google Chrome and Firefox browsers