OmarShehata
commented
4 years ago We're migrating the issues in this repository to consolidate questions, Cesium ion feature requests, and bug reports on the Cesium community forum, that way there'll be one place to search for answers.
We're tracking this internally and plan to have more learning materials explaining this! In the mean time, for any questions, please post on the community forum.
We do our best to make sure tilesets on ion, loaded into CesiumJS are as optimized as they can be by default. With that said, as a user, it's helpful to understand how to tweak screen space error parameters, whether that's because you want to understand when the highest level of detail is loaded, or to tweak high much detail is needed in a scene.
So it would be great to have a guide on this somewhere. In the mean time, here are a collection of tips I've written in emails/forum posts etc.
What is the screen space error (SSE) ?
Intuitively, you can think of SSE as a measure of close a given level of detail is to the original, source resolution. The lower it is, the closer it is to representing the original data accurately.
Each tileset has a maximumScreenSpaceError property in CesiumJS that you can tweak to change the client's tolerance for error. Setting it to a low value like 4 will load higher resolution at greater camera distances (so you don't have to zoom in all the way to trigger the higher levels of detail). Setting to a high value like 32 will make the tileset load a lot faster, but lower levels of detail will load until you zoom in closer.
Setting it to 0 will force the highest level of detail to load, regardless of how far away the camera is. This is not recommended in production.
Use the tileset inspector to tweak SSE
The easiest way to tweak the SSE at run time is using the tileset inspector. Under the Update tab you'll see a SSE slider.
Here's a Sandcastle example where you can try it.