It's currently difficult to know why a mesh is not valid after calling CheckValidity - can it provide more detailed errors than just a bool? Even if it's only on the exception message in FailMode.Throw.
For example Expected mesh to have equal number of vertices and normals, but it has # vertices and # normals.
It's currently difficult to know why a mesh is not valid after calling CheckValidity - can it provide more detailed errors than just a
bool? Even if it's only on the exception message inFailMode.Throw.For example
Expected mesh to have equal number of vertices and normals, but it has # vertices and # normals.