Why my penguin model with armature act glitchy?

[Fyrestar]

For this model DRACO is totally overkill actually.

@qweqwe_Flinstone

I simplified my mesh to be triangulated and i discovered that every face of my object was a seperate set of 3 verticies, so i merged them by distance to connect everything with each other and nothing changed with my animation

What do you mean by connected? You need to create a index, this might help:

BufferGeometry: toIndexed

Since i already posted the half snippet, this patches THREE.BufferGeometry with a function to create a indexed one from a non-indexed. A new BufferGeometry is returned. A indexed geometry reduces the data of all attributes and will generally perform better, also computeVertexNormals can be called only on indexed geometries to compute smooth normals.

I bet that problem is related to that draco which propably is trying to compress mesh of armature

I don’t know if the decompressed result is actually the same order as it’s original. But in your case it definetly got turned into a non-indexed geometry, both cases would corrupt the bone assignments and therefore the animation, when it got turned into a non-indexed anyway.