# How to load a series of 3dtileset **URL:** \ **Category:** 3D Tiles\ **Created:** [July 24, 2024, 9:16am UTC](https://community.cesium.com/t/how-to-load-a-series-of-3dtileset/34027 "2024-07-24T09:16:34Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![zhouyy](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/zhouyy/32/24881_2.png) [@zhouyy](https://community.cesium.com/u/zhouyy)\ **Post date:** [July 24, 2024, 9:16am UTC](https://community.cesium.com/t/how-to-load-a-series-of-3dtileset/34027/1 "2024-07-24T09:16:34Z")
I created a very large scene in RealityCapture, then used a script to split them into many small pieces and exported each block as a separate 3dtiles. How should I load them all in cesiumJs and restore the scene. Does loading separately affect performance? I used the tool to merge the json files of these blocks, and it was no longer able to load successfully in cesiumjs. Anyone has the same experience,please give me some advice ---
**Author:** ![Marco13](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/marco13/32/2757_2.png) [@Marco13](https://community.cesium.com/u/Marco13)\ **Post date:** [July 31, 2024, 1:22am UTC](https://community.cesium.com/t/how-to-load-a-series-of-3dtileset/34027/2 "2024-07-31T01:22:07Z")
There are several engineering questions involved here. These include (but are not limited to) how large the full data set is, how many ‘small pieces’ you created (and how large each of these pieces is), what the level-of-detail structure of each tileset is, and how you intended to combine them at runtime. (Further, more detailed technical questions might depend on the answers to the first ones). But as an attempt to get an idea here: When you have a _single_ tileset, and load this _single_ tileset in CesiumJS, then there is usually the assumption that the tileset is structured in a way that allows _streaming_ the data, and supporting _hierarchical level of detail_. Some details about the technical aspects are explained in the [3D Tiles Reference Card](https://github.com/CesiumGS/3d-tiles/blob/main/3d-tiles-reference-card.pdf). A rough summary: CesiumJS will usually first load the ‘root tile’ of that tileset. This root tile will contain a very coarse (simplified) representation of the geometry data. Depending on the available memory and user interaction, CesiumJS will then load the child tiles of the root. And these child tiles will contain more detailed geometry. And it will keep loading additional data and refining the geometry, until a certain stopping criterion is met. Now, this works fine when you have _one_ tileset, and the root tile of this tileset contains maybe 5 MB of geometry data (the coarse, simplified one). But when you say that you broke a large scene into ‘many small pieces’, then it’s not clear what that means. When you now have, say 1000 tilesets, and _each_ of them contains 5 MB geometry data in its root node, and you try to load them all at once, then this would mean that you’d have to load 5 GB of data to even see the first, coarse geometry… Properly structuring large data sets for efficient streaming is not entirely trivial. So just to get a better idea, can you give a few rough numbers, about _how many_ tilesets you merged, and _how large_ each of them is? (BTW: I assume that you merged the JSON files with the `3d-tiles-tools`, namely the `merge` or `mergeJson` functions - is that correct? And I’m also curious how you did _split_ the original data into pieces. Cesium ion should be able to process pretty large models, so maybe some of the trouble could be avoided by uploading the data to Cesium ion and rely on its capabilities to create a good, efficient, well-structured tileset to begin with) ---
**Author:** ![zhouyy](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/zhouyy/32/24881_2.png) [@zhouyy](https://community.cesium.com/u/zhouyy)\ **Post date:** [July 31, 2024, 2:10am UTC](https://community.cesium.com/t/how-to-load-a-series-of-3dtileset/34027/3 "2024-07-31T02:10:37Z")
Hello, Marco13 In Reality Capture, I recreate a real-life scene using photos taken by a drone. However, due to the large size of this scenario, the program will crash due to lack of memory during the rebuild process. So I used a scripting tool to break it down into a lot of chunks, and you can refer to [https://www.youtube.com/watch?v=utvCIyQs44M&t=352s](https://www.youtube.com/watch?v=utvCIyQs44M&t=352s) about the use of this tool. Each block is exported as a separate 3dtileset, which contains a root JSON file and some sub-JSON files. But there are 60 such 3dtilesets, so I need to merge them into a single root json file, like assembling branches on a stump to form a new big tree. I achieved this by using 3d-tiles-tools, [GitHub - CesiumGS/3d-tiles-tools](https://github.com/CesiumGS/3d-tiles-tools) In the end, I was able to adjust 'maximumScreenSpaceError: 'to achieve the desired effect ---
**Author:** ![Marco13](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/marco13/32/2757_2.png) [@Marco13](https://community.cesium.com/u/Marco13)\ **Post date:** [July 31, 2024, 11:11am UTC](https://community.cesium.com/t/how-to-load-a-series-of-3dtileset/34027/4 "2024-07-31T11:11:14Z")
> [@zhouyy](#): > > In the end, I was able to adjust 'maximumScreenSpaceError: 'to achieve the desired effect Does this mean that the issue itself is resolved now? What the `3d-tiles-tools` `merge` function is doing is very simple: It is just taking the given tilesets and creates a new top-level tileset JSON. And creating a top-level tileset JSON that has 60 (!) child nodes could already cause trouble: When trying to load this, then CesiumJS will have to request all these 60 tilesets at once, and load (at least) the root node of all these tilesets at once. It might still be OK, but probably not ideal. Beyond that, there are many degrees of freedom, even in this simple step (but the details would already depend on the exact tilesets and their structure)