Hi, I am bringing my tiled dataset into unity and compiling for Android, on first look all seems well but as you rotate the camera around (when you are close to the geometry) the app crashes wondering if any one else experiencing this, or is there a optimisation setting I am missing?
There are settings in the
Cesium3DTileset you can use to affect loading behavior and memory usage. However, I want to make sure that this is not a bug first. Are you able to consistently reproduce this crash? If so, can you describe the steps it takes to make your application crash?
The crash happens - when you are close the tiles, so maybe something to do with the memory when the tiles are at their highest quality. If the camera is fully panned out the model seems to hold - if you zoom in and rotate the camera the app hard crashes. FYI you get the same response if you try and view the web version on mobile devices - through a share map link.
The map is quite large over 400 acres and around 3.5 GB on upload, originally uploaded 225 separate tiles but Matt from your team though it may be best to upload the whole map and let cesium do its thing.
Can you try modifying the settings on your
Cesium3DTilesets and seeing if that helps? In particular, the Maximum Cached Bytes and Maximum Simultaneous Tile Loads settings may need to be lowered to values a mobile device can handle, especially if multiple tilesets are in the scene.
That seemed a lot more stable, will keep testing it and let you know how I get on.