Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error with animated draco

See original GitHub issue

Hi,

So today I played some time with the new draco feature. Everything seemed to work fine, expect for when I tried to compress animated gltfs:

Without draco: without_draco

With draco: with_draco

The validator on donmccurdy’s viewer says the following error: Length of 0x004e4942 chunk is not aligned to 4-byte boundaries

When I export it as a gltf+bin (instead glb), the error is not showing up, but the visual artifact is the same. As well, as in the babylon sandbox. When I remove the -d from the command, the exported file’s animation works well, so I’m pretty sure draco has something to do with it.

The command I use: node bin/gltf-pipeline.js -i input/cube.gltf -s -d -b -o output/cube.glb

My files: animation_test.zip

Issue Analytics

State:
Created 5 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

FrankGalligancommented, May 1, 2018

So currently encoding a mesh with morph targets with default settings could cause errors as you observed. I’m going to make a change to gltf-pipeline to fix these types of files. The compression won’t be as good as I’m going to force sequential encoding which will preserve the order.

Later on, we will make changes to properly handle animation and morph targets.

0reactions

soadzoorcommented, May 1, 2018

Great, thanks guys for the quick fix!