Grasshopper: "Solid Intersection" not actually splitting and discarding?

[swojtalewicz (swoj)]

Hi! I’m trying to use the “Solid Intersection” component in Grasshopper to essentially trim a custom pattern that I’m attempting to map onto an unrolled surface, that will then later be Sporph-ed back onto the original surface. However, the “Solid Intersection” component ignores some of the inputted Breps, while inputting the entire unsplit Breps for other inputs. I’m glad that it is at least ignoring Brep inputs completely outside of the boundary that I have provided, but still want to discard the split outputs that fall outside of the intersecting boundary box that I have provided as well (I made this ‘intersecting boundary box’ that I refer to by just extruding the unrolled surface, since the provided Brep pattern is 3D and wouldn’t work with a simple “Region Intersection” component).

Screenshot of script + actual grasshopper file included below:
240826 Brep Intersection Fail.gh (1.1 MB)

[piac (Giulio Piacentino)]

@swojtalewicz , could you provide the definition with the result of “brep unroller” internalized into it?

I don’t get that component to show up, it must be third-party, and so I can’t try your definition.

[martinsiegrist]

The Brep input for that unroller is just a single surface. You can use orient to orient the surface in the XY plane. Not quite sure about the rest of the definition…

Your breps aren’t solids or closed polysurfaces so the use of Solid Intersection is maybe not quite adequate.

surface-split.gh (1.1 MB)

As the file name says, I used surface split.

[swojtalewicz (swoj)]

Of course, I think it might have been a lunchbox component – I don’t remember exactly. Either way, here is the same script with the “Unrolled SRF Internalized”
240826 Brep Intersection Fail.gh (1.1 MB)