You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently using the simplest possible 3D Tiles refinement algorithm, where we won't refine a tile until all of its children (visible or not) are loaded and able to be rendered. This prevents any LOD-skipping, and requires loading a lot more tiles than are actually rendered, which is inefficient. The main advantage of this algorithm (other than simplicity) is that we'll never find ourselves with holes in the mesh.
We should implement the selection algorithm from CesiumJS's terrain engine. It allows skipping any number of levels (and therefore much less loading) and will never allow scene geometry to disappear with camera movement (which looks terrible). But if the camera moves such that not-yet-loaded sections of model are now visible, those parts of the model will be missing entirely. The CesiumJS terrain engine renders "fill tiles" in this scenario, which will be very challenging for the more general case of 3D Tiles. For many 3D Tiles tilesets, though, it will be acceptable to simply render nothing until the new tiles are loaded.
Configuration options should allow the user to select between a guaranteed-complete mesh (current algorithm) or faster loading (this algorithm).
The text was updated successfully, but these errors were encountered:
We're currently using the simplest possible 3D Tiles refinement algorithm, where we won't refine a tile until all of its children (visible or not) are loaded and able to be rendered. This prevents any LOD-skipping, and requires loading a lot more tiles than are actually rendered, which is inefficient. The main advantage of this algorithm (other than simplicity) is that we'll never find ourselves with holes in the mesh.
We should implement the selection algorithm from CesiumJS's terrain engine. It allows skipping any number of levels (and therefore much less loading) and will never allow scene geometry to disappear with camera movement (which looks terrible). But if the camera moves such that not-yet-loaded sections of model are now visible, those parts of the model will be missing entirely. The CesiumJS terrain engine renders "fill tiles" in this scenario, which will be very challenging for the more general case of 3D Tiles. For many 3D Tiles tilesets, though, it will be acceptable to simply render nothing until the new tiles are loaded.
Configuration options should allow the user to select between a guaranteed-complete mesh (current algorithm) or faster loading (this algorithm).
The text was updated successfully, but these errors were encountered: