trimesh.bounds.oriented_bounds is slow for NumPy array input.

[guystoppi]

Hello,

While using trimesh==4.5.0 to compute the minimum volume oriented bounding box of a mesh, I noticed the following bug. Running the below code seems to take an extremely long time:

torus_mesh = g.trimesh.creation.torus(major_radius=5, minor_radius=1, major_sections=512, minor_sections=256)
trimesh.bounds.oriented_bounds(torus_mesh.vertices)

But running this similar piece of code completed in ~7 seconds:

torus_mesh = g.trimesh.creation.torus(major_radius=5, minor_radius=1, major_sections=512, minor_sections=256)
trimesh.bounds.oriented_bounds(trimesh.Trimesh(vertices=torus_mesh.vertices))

My best guess is that, in the first case, the computed convex hull's face adjacencies seem to be wrong although I'm not sure how exactly. Line 253 in bounds.py computes 139156 edges that need to be checked, which doesn't seem right. In the second case, only 516 edges are checked.

I noticed that, in the first case, the convex hull is being computed by trimesh.convex.convex_hull(..., repair=False) and, in the second case, the convex hull is effectively being computed with trimesh.convex.convex_hull(..., repair=True). This PR makes both cases use repair = True. Hopefully the solution is indeed that simple.

Thanks for the great library!

[mikedh]

Good catch, and thanks for the fix!! Yeah it looks like with repair=False the hull early-exits before removing zero-magnitude faces and other stuff.