draco
draco copied to clipboard
1.5.x RuntimeError: 'Error: Draco encoding failed.'
Hi,
I'm experiencing this issue when using gltf-pipeline.
Npm packages:
[email protected]
[email protected]
How to reproduce it:
Run gltf-pipeline -i test/test.gltf -o test.glb -d=true --draco.compressionLevel=10 --stats
This is probably due to some problem on the gltf, but I can't share it in public. Could you please give me an email address where I can send the gltf? so you can reproduce the bug?
Thanks
@jlledom: Replied directly to you off thread.
I sent you the gltf
Well, this is embarrassing: This one definitely fell off of my radar. Is this still an issue with the latest releases?
Hello, yes, I just tried with [email protected]
and [email protected]
and I see the same error
Thanks for checking. I'll try to get you some more information about what's going on by early next week.
Hi @tomfinegan, do you have any update on this? I also have several files with exactly this error.
@Ben-Mack Do you have a file that can be shared publicly that reproduces a similar error?
The error reported in this issue could be many things, but it would help if there were a shareable file that reproduces it. I haven't had a chance to dig into this problem, and a file that reproduces a similar error without sharing restrictions would help accelerate a diagnosis.
After closer investigation, my cases are caused by mesh with zero surface area. Removing them fixed the error for me.
guys, I have an example of the file in glb format, with the same error. I hope it's going to help to fix this one: eec63d72504d-Underwater_with_Manatee.glb.zip
HI, what is the progress about this problem now
i met the same problem
actually, in my case everything is really simple - I tried to compress an already compressed file :)
@dandingol03 maybe you have the same issue, can u share here your example?
After closer investigation, my cases are caused by mesh with zero surface area. Removing them fixed the error for me.
@Ben-Mack how did you removed the zero area shapes? can you help me with this?
@tomfinegan @FrankGalligan any update on this issue. I am too facing the same issue for some files.