TypeError: t.value.slice is not a function when loading animated glb

CesiumJS
1

I’m trying to load an animated glb object in Cesium and I’m getting this error:

An error occurred while rendering. Rendering has stopped.
TypeError: t.value.slice is not a function

TypeError: t.value.slice is not a function
at GEe (http://127.0.0.1:8080/mapas2023/js/Cesium.js:1558:43734)
at new nm (http://127.0.0.1:8080/mapas2023/js/Cesium.js:1558:45214)
at N2e (http://127.0.0.1:8080/mapas2023/js/Cesium.js:3562:14085)
at Tl.buildDrawCommands (http://127.0.0.1:8080/mapas2023/js/Cesium.js:4429:5855)
at lUe (http://127.0.0.1:8080/mapas2023/js/Cesium.js:4429:36864)
at go.update (http://127.0.0.1:8080/mapas2023/js/Cesium.js:4429:34943)
at Os.update (http://127.0.0.1:8080/mapas2023/js/Cesium.js:5306:108009)
at a0e (http://127.0.0.1:8080/mapas2023/js/Cesium.js:8701:33746)
at Zg (http://127.0.0.1:8080/mapas2023/js/Cesium.js:8701:30566)
at Li.updateAndExecuteCommands

I’ve created this object using blender and I can successfully open it using any 3d viewer. I’ve also validated it with glTF Validator and it says it’s a valid glb file.

I’ve exported it disabling the animation, so it doesn’t move, and I’m still getting the same error when I try to load it in Cesium.

The object has a cylinder and a plane (it’s a flag) and it weights 457KB (it’s not that big). I’ve been able to load more complex objects in Cesium, so I don’t understand what I’m doing wrong.

Any help will be really appreciated.

2

If you could share that GLB file (attached as a ZIP here or via a private message), that would certainly be helpful for debugging.
Otherwise: Is the glTF using any special extensions?
(Out of the core features of glTF, I think that sparse accessors are not supported, that could explain the error, but is only a guess for now)

3

To close the loop here: One part of the problem was that the model used a huge number of morph targets (and this is, to some extent, tracked via Render gltf model with morph targets failed · Issue #10810 · CesiumGS/cesium · GitHub ). An outdated version of CesiumJS might have contributed to the error, but this is still being investigated.