likangning93

It might be better to use the actual code that crashes for the triangle degeneracy check. Right now I'm using this for culling bad triangles in my prototype mesh processing...

We found another issue. When to triangles share vertices but have opposite winding order, the smooth normal computation for the shared vertices can cause this normalization problem:  If we...

I think it's still worth implementing a winding order correction stage, but perhaps it should also include a documented toggle to switch between winding order correction and vertex duplication. Most...

Not really something we expect to effect every day users - models that large shouldn't be optimized for vertex cache because they aren't really drawable anyway and should be split...

Heads-up that we may also be able to reduce instances of the string limitation by binning buffers, iirc `obj2gltf` tries to generate a single output buffer, but there's tons of...

I'll take a look at modularizing the geolocation code soon so we can add some lights relatively easily.

It looks like the error is coming from the part of the glTF pipeline that generates vertex normals, it might be trying to generate normals for a triangle that has...

I'm not getting errors from the obj2gltf command line tool with this one as-is either, so I think it might be the translation thing. Have you considered using the node...

@JakeDluhy sorry for the extremely slow response. This case can happen if your model's winding order is inconsistent, see here: https://github.com/AnalyticalGraphicsInc/gltf-pipeline/issues/242#issuecomment-280711872 For now, if you can get your model imported...

Ah. Looks like the Draco documentation may be a little bit outdated, but their cmake checks for an `IE_COMPATIBLE` flag (toggleable as `DIE_COMPATIBLE=true` on the command line, which is amusing)...