When using the mesh|curve intersect, not all intersect point will show. This is not an issue in Rhino 6, is this a know issue and will there be a solution? I know the geometry is far away from 0,0,0 but this worked in Rhino6.
I see that here and put it on the list as RH-62386 to be looked at.
For the time being, you could create a surface in the same position as the mesh and intersect the curves with the surface.
-wim
I’ll take a look at the first sample, and try to figure out who should look into this next. But I’m very interested in making Mesh|Ray work very well, also.
Are you using Rhino 7 SR3? This would be very important, because we have been tweaking this component to use the new intersector between SR2 and SR3. Please, if you have a sample that does not work, post it as well!
@pga Sorry, I must have not explained carefully enough. The Mesh|Curve component does not work well, and that’s something that is being explored. @wim kindly reported the issue. This is something related to some different work, not the New Mesh Intersector, because Mesh|Curve does not use it. I suspect some particular mesh tree changes. This can be tracked at RH-62386. As a todo item for me, I’ll check if it’s feasible to switch to the new intersector.
In the next message, you mention the use of Mesh|Ray fixes this particular problem, “but not all”.
I opened the file you attached and indeed it works always here. My request was particularly related to Mesh|Ray working “not for all”. I tested this in 7.3.21012.11001. SR3 is still changing every week, because it’s a Service Release Candidate.