Michael Dawson-Haggerty

Yeah I think there's no way of avoiding implementing a custom distance-based linker to do that. I might try computing the vector-along-the-segment from the outline, and doing a `scipy.spatial.cKDTree` query...

Hey, is that mesh empty by any chance? I.e. `len(mesh.faces) == 0`

Hey, the keyword arguments to `scene.show` are passed through to `trimesh.viewer.windowed.SceneViewer` constructor: https://trimsh.org/trimesh.viewer.windowed.html#trimesh.viewer.windowed.SceneViewer.__init__

Hey, yeah unfortunately embree doesn't make particularly strong promises: https://github.com/embree/embree/issues/188 https://github.com/embree/embree/issues/174 https://github.com/embree/embree/issues/181 I'm hoping at some point to get some of the variants/forks of https://github.com/mikedh/trimesh/pull/1108 merged, and the upstream embree-3...

Ah yeah I also see a ton of depreciation warnings with my applications for Shapely 2.0 from trimesh. Any idea when Shapely 2.0 releases?

Nice! I just briefly tried and failed to install Shapely2 to play with this haha, in the mean time I'll try to clean up the `DepreciationWarnings` when I see them....

Hey, `path.vertices` are not in a meaningful order, they are referenced by `path.entities[i].points`. You probably want `path.discrete`

I like the simple nature of this proposal! I'm not totally sure that the collision details ("has sensor", physics properties, etc) are necessarily the same as "I just want a...

Hey, you might want to look at the `section.paths` or `section.discrete` which are closed cycles. Entities aren't necessarily ordered or connected, it is a "curve soup": ``` In [1]: import...

Hey, yeah `section.paths` will be empty if there are no closed cycles in the curve soup. If the mesh isn't watertight there may not be any closed cycles.