# skipLevelOfDetail?

**URL:** <https://community.cesium.com/t/skiplevelofdetail/14665>\
**Category:** CesiumJS\
**Created:** [August 2, 2021, 1:54pm UTC](https://community.cesium.com/t/skiplevelofdetail/14665 "2021-08-02T13:54:59Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![TomPovey](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/tompovey/32/1987_2.png) [@TomPovey](https://community.cesium.com/u/TomPovey)\
**Post date:** [November 27, 2023, 11:08am UTC](https://community.cesium.com/t/skiplevelofdetail/14665/21 "2023-11-27T11:08:31Z")

</div>

this is the relevant PR for anyone interested:

> <https://github.com/CesiumGS/cesium/pull/11167>
>
> This PR splits \`Cesium3DTilesetTraversal\` into two separate classes: \`Cesium3DTi…lesetBaseTraversal\` and \`Cesium3DTilesetSkipTraversal\`, which, along with \`Cesium3DTilesetMostDetailedTraversal\`, are all implementations of the \`Cesium3DTilesetTraversal\` \_interface\_. This new structure has the following advantages:
> \- The flow is simpler: branching (based on the tileset.skipLevelOfDetail flag) is done once per frame, instead of several times throughout the traversal
> \- The code is more understandable: each class is easier to read
> \- The new interface is more extensible: to implement new traversal logic, simply add a new class \`Cesium3DTilesetNewTraversal\`
> 
> The traversal type is now selected in \`Cesium3DTileset.prototype.getTraversal\`, instead of being fixed inside \`Cesium3DTilePass\`.
> 
> The changes in the traversals themselves are probably easiest to understand by comparing \`Cesium3DTilesetBaseTraversal\` and \`Cesium3DTilesetSkipTraversal\` to the original version of \`Cesium3DTilesetTraversal\`&mdash;in this view, each new class is a simplified version of the original.

[Previous page](https://community.cesium.com/t/skiplevelofdetail/14665.md?page=1)