CreateMeshCollider() with no arguments?

[SpiderPig]

Does CreateMeshCollider() not need a mesh as an argument any more?    I may have missed something in one of the blogs...

[Josh]

Oh yeah, I changed the way this works. After creating the collider, call Collider::AddFace for each polygon / face. When you are done adding faces, call Collider::Finalize().

This gives you control over the exact number of vertices per face, and the finalize method also exposes the Newton optimize feature, which will attempt to merge adjacent coplanar faces.

[SpiderPig]

Ah awesome!  I had a little freak-out when it didn't compile, but that way sounds much better, thanks. 

[SpiderPig]

Can AddFace() only take 3 vertices in the array?

[Josh]

No, it accepts any number of vertices more than two.

[SpiderPig]

So I should take care to add them in a certain order?  Like a triangle_strip in GLSL, otherwise I might get overlapping faces...? 

[SpiderPig]

I think the answer is yes... would it be practical to add the ability to set the indices?  Just that going through this and adding vertices in order is going to be a headache to figure out.

[Josh]

They are added in the order you specify, and form a concave polygon. Typically this is just used for quads or maybe brush faces. What are you trying to do?

[SpiderPig]

It needs refining, but currently I create a collider per voxel.  This can be up to 5 or so triangles in total per collider.  It worked the old way because I was able to set the indices as well.

[Josh]

for (auto i : polyindices)
{
	points.push_back(vertices[i])
}
AddFace(points);

 

[Josh]

You could also just call entity::BuildMeshCollider() or entity::BuildConvexHullCollider().

[SpiderPig]

Thanks, I'll see what I can do.