Invalid requests sent out for voxel content

[javagl]

What happened?

CesiumJS is sending out invalid requests for voxel data. It is requesting data that is not available (even when it is declared to not be available!), resulting in 404s.

Reproduction steps

• Open the "Voxels" Sandcastle at https://sandcastle.cesium.com/index.html?src=Voxels.html
• Select "Box - 3D Tiles" from the menu (or any other "3D Tiles" flavor, FWIW)
• Look at the console. It will result in several messages GET https://sandcastle.cesium.com/SampleData/Cesium3DTiles/Voxel/VoxelBox3DTiles/tiles/1/1/0/1.json 404 (Not Found)

I started zooming into that, and think that it is likely related to this line: https://github.com/CesiumGS/cesium/blob/6c462b7c02ed81bbc5475b03b03fec9884ab3530/packages/engine/Source/Scene/Cesium3DTilesVoxelProvider.js#L457 : It is checking the tile availability with tileIsAvailableAtCoordinates, and based on that, it is requesting content with getVoxelContent (but that's only a hunch, and has to be confirmed).

(A similar issue was fixed via https://github.com/CesiumGS/cesium/commit/f1b5f8dbd9ececb4fe5a4f8427cbfed15e831168, but I don't know in how far this is related)

This came up via the forum at https://community.cesium.com/t/3d-tiles-1-1-voxel/32239

Sandcastle example

See above

Environment

Browser: Any CesiumJS Version: 1.117 Operating System: Any

[ggetz]

@jjhembd Could you please triage?

[ggetz]

Hi, @jjhembd – Just a reminder to please take a look and triage this issue.

[javagl]

Things change. The tileset-based examples are now in https://sandcastle.cesium.com/index.html?src=Voxels%20in%203D%20Tiles.html (the others are "Procedural").

What may be more important: I don't observe the issue any more.

Closing for now.