Shatter at intersections

Hello,

I try to intersect curves at their intersection points, but they split at other points. I use the shatter component. I don’t understand why it is not working.
Maybe someone can help me!


Neu 12.01.gh (501.6 KB)

missing

I can see this much geometry but it’s not obvious what you want to do.

The sprawling canvas with hidden wires doesn’t help.

1 Like

the Shatter components wants a Curve Parameter “t”, defined as single numerical value which identifies a point along the curve

instead of that “t”, you are giving it a list of 3D Points

you can take the shatter Parameters from the Multiple Curve Intersection component

this might be a way to do that, probably there are MUCH simpler ways to do the same that just don’t come to my mind at the moment :slight_smile:

Neu 12.01_Re.gh (491.0 KB)

maybe this is just easier to read, but it does exactly the same with the same amount of components :rofl:

1 Like

Thank you so much for the quick reply, it was realy helpful. Now it works for the vertical curves. They are split at the intersection points but the horizontal ones are still split at random points.

Neu 12.01.gh (496.4 KB)

I try to split the curves of the lines in this part at their intersections:

well, in my PC that is not happening :slight_smile:

please give a try to this:
Neu 12.01_Re.gh (486.8 KB)

here is what I see:

1 Like

Oh wow, okay then it is probably my PC… Thank you so uch for the solution!! I’m trying to fix the Problem with my Computer!

Thanks again!! :slight_smile:

it’s not your pc :slight_smile: in your last GH file the Curve input of Shatter is not grafted

graft it and it will work :+1:

2 Likes

It worked!!! Thank you :slight_smile: :+1:

1 Like

Hello to all!
@inno - I found your solution and thought it should be working for my problem as well - as it is basically the same. Since Rhino 8 does not support NGon anymore I had to change my code to shatter curves at their intersection points with regular GH components. I tried a few things and even experimented with a python component until I tried your solution. It seemed to work just fine, but in the last step, the shatter component fails. I don’t know where exactly my data structure is messed up, the only difference here is, that I have one set of curves which is not intersecting and one singular curve which intersects with most of them (pictures are added)
Do you think this can cause the problem?

Thanks in advance for any help and best regards, Clara :slight_smile:

here is my current file - (don’t mind the rest of the mess please :D)
shatter.gh (116.7 KB)

please right click on each of these parameters, select “internalise data” from the menu, save the GH file agagin and reupload it :+1:

1 Like

Ah sorry - yes that would have made sense!

Here you are - thanks for your quick reply!

shatter.gh (14.2 MB)

because you are in a “one to many” situation, where you have a single polyline to shatter many contour curve, I think using the standard CCX component makes more sense:

shatter_Re.gh (119.2 KB)

I have pasted those components in your original definition with non-internalized geometries, so it’s lighter and should just work fine with your Rhino file

2 Likes

Hello, thanks for your quick solution! The CCX Component is a great idea, thanks!
It helped to some extent, but I still cannot figure out, how you managed to split the curves from front to back. I still have circular contours, even after shattering.
What else did you do in your definition?


You need to start a new thread.

There aren’t any polylines intersecting the bottom contours, that’s why.

you might get better results by passing the Contour curves through a Join Curves first (which will bring the total amount of curves from 134 to 89) :

by the way, I’m on Rhino 8: it shouldn’t be, but it might be R7 is behaving slightly differently?

2 Likes

thank you @inno - I think indeed the join curves did the final trick!
It works perfectly now, I am really happy to be back at my patch surface with the splitted lines.
Idk about the difference betwen Rhino 7 and 8, I actually thought this happened just because I was missing the NGon components…

1 Like