The docs for Object3D state:
Quote
public Object3D(float[] coordinates,
float[] normals,
float[] uvs,
int[] indices,
int textureId)
uvs - the texture coordinates [u1,v1,u2,v2,...]
When in fact it seems to read ws too (thus being u1, v1, w1, u2, v2, w2...).
Well...no, it doesn't. jPCT has no concept of w? when it comes to texture coordinates.
They made more sense when I added them, though, if still not perfect.
But that would just screw up the coordinates. I'm using the array as u1,v1,U2,v2...etc. Adding a w to that will just mix the uvs wildly.
I've already solved it by re-working the format. The bones thing is getting really close (except for the mysterious weights thing).