Can the component index be added to lineIntersectsSurfaces returned array?
With this change, the new returned arrays would be:
[pos, normal, proxy, parent, selections, bisurf, index]
The reason I ask is because when there are many intersections, it's difficult to say which intersections belong to the same part.
By "component index" I mean the "_forEachIndex" (iteration index) of:
- Convex Component for FIRE/GEOM/VIEW LODs (because they use convex components)
- Plane for ROADWAY LOD (though I don't care about this, because they have no thickness anyway, so you can just return -1 for this case)
E.g. let's say I want to know the thickness of a wall that is between points p1 and p2 and calculate a penetration value for it, so I perform 2 intersections, one p1-p2 and one p2-p1.
The problem is, if there are multiple intersections, I can't tell which one was the exit point. Also around sharp corners lineIntersectsSurfaces sometimes misses the exit/entry so I can't pair them up correctly. So getting the wall thickness is very unreliable right now.
A simple example in 2D, where you have 2 convex parts as rectangles:
And this example shows a missed intersection near that sharp corner which means you can't pair intersections anymore:
