https://communities.bentley.com/members/481cbbed_2d00_3b01_2d00_4183_2d00_b909_2d00_c47fbd2831e1MATAN Ben-Moshe's recent activityen-USTelligent Community 12https://communities.bentley.com/achievements/460ac7df-7ccc-4c42-a204-9e05eef3be09Sun, 19 Mar 2023 07:42:06 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:19f2aac1-3b53-4fd8-b712-c2afc55420f8Ask a question in a forum.https://communities.bentley.com/products/3d_imaging_and_point_cloud_software/f/contextcapture-descartes-pointools-forum/243078/cesium-3dtiles-maximumscreenspaceerrorSun, 19 Mar 2023 08:30:38 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:0eacd71b-ddaa-44a0-badb-3c6fd528eab0MATAN Ben-Moshe<p>When producing a 3DTiles model via CC it optimizes the model for maximumScreenSpaceError = 1, while the default value for CesiumJS and other viewer is 16. This causes the model to load LOD levels incorrectly, resulting in a low-poly model unless fully zoomed in, which isn&#39;t practical for viewing.</p> <p>While in CesiumJS this can be avoided by manually setting&nbsp;<span>maximumScreenSpaceError to 1 when loading a tileset, not all viewers expose this setting.</span></p> <p><span>Is there a way to export 3DTiles for the default value of 16, or convert the exported tileset to 16 after the fact?</span></p><div style="clear:both;"></div>