Cesium 3D-Tiles problem

Hi,

I have 3d Tiles dataset produced by ion from a customer. I have to display it in 1.93/1.65, because of different reason.

The file is displayed but shrinked together - does anyone can help ?

I used the Cesium sandcastle 3D Tiles adjust height.

Regards

Rüdiger

The file is displayed but shrinked together

It’s not entirely clear what that means. (I see the screenshot, but don’t know what it is supposed to look like). Note that the geometry in the tileset should always be given in meters, so there should not be a reason for it to be displayed with a wrong size. And in order to provide further hints, it may be necessary to know more about the tileset itself. In general, you can modify the scaling factor of the tileset in the tileset JSON itself, or using the tileset.modelMatrix (but the latter may have unexpected effects, if the tileset JSON already contains a transform)

My guess would be that the 1.65 has some issue with some extension like KHR_mesh_quantization or EXT_meshopt_compression. Maybe you could tell customer to re-add dataset with compression options disabled

Hello Marco,

The Tileset is an Export from Cesium ion. In Both Cases I used the adjust height example from Cesium Sandcastle online change the url.

I used Word Terrain as dtm.

The Original dataset is a citygml.

Regards

Rüdiger

Hi, thank you for the top. The file is an Export from ion. Original is a citygml. In Both cases cesium 1.65 and 1.128 I used the sandcastle adjust height.

Can I See the Compressor somewhere in the bdm ?

Regards

Rüdiger

In theory, you can open a B3DM file with an editor (it’s a binary file, but the relevant part is some embedded JSON), and see whether it contains the strings ‘draco’ or ‘meshopt’.