Hi,
I am trying to gather the intersecting points with CCX and for some reason it keeps missing a certain area, even though, when I bake out the geometry the intersection via Rhino works.
See attached images. *
ccx intersect bug.gh (347.0 KB)
*
if you flatten one of the inputs the missing points appear, so the data is all there, just organized in a way that does not work well:
in particular, Curves in B are not properly branched by their Z value:
so, please, edit and remove the word “Bug” from the title of this thread, as this is clearly not a bug
2 Likes
Sorry I didn’t realize that was the case. It just seemed unusual that it would be doing one thing and then another thing entirely when done manually, hence why I wrongly assumed it was “a bug”
I appreciate your guidance and detailed insight. thank you.
Looks like there was a good surface and intersection planes at some point in the process but things got all fouled up somehow. I reverse engineered the geometry by rebuilding the horizontal curves (purple group) to reduce the number of control points per curve from 149/268 to just 35. And reconstructed 19 intersecting planes (white group).
intersect_2024Sep25a.gh (370.9 KB)
Don’t know your objective but clean geometry might help, eh?
1 Like
yeah I found the culprit, I had a bad path remap up the chain away from where I internalized the data at the problem junction. cleaned up the data trees. 
Hope I didn’t waste my time? Keep the geometry clean 
Hope you noticed the PCX at the bottom right (white group)? Planes are in the yellow group.
1 Like
yes, Geometry is clean as can be 
Just a compound surface tower thing I’m making, doing some metal printing, so the goal is to turn this into toolpaths.
Curve intersections are not as robust as plane/curve intersections IMHO.