Grasshopper not being very helpful here :
250217_PROG_Vertices shuffled.gh (8.1 KB)
Now let’s have fun un-tangling this mess…
Grasshopper not being very helpful here :
Now let’s have fun un-tangling this mess…
Hey there, Osuire
Does this help?
That is not true
You’re right. It isn’t.
I guess I jumped to conclusions when I looked at your first branch and saw 5 vertices for a 4 sided figure. Maybe it is a seam?
Does using discontinuity help?
Only questions from you, never answers.
Do you mean me?
No, @osuire, who has probably been using GH longer than any of us. In this case, I’m sure it depends on the brep - how it was created, the nature of its faces. I’ll take a wild guess that bounding boxes are always consistent? I know their faces are predictable.
It looks like what it’s doing is preserving the vertex order of the original brep. For example, face 1 of the original brep uses vertices 1, 4, 5, and 6, so those locations get mapped to vertices 0, 1, 2, 3 of the exploded face.
Try this python script for a non-shuffled point list.
250217_PROG_Vertices ordered.gh (18.6 KB)
import Rhino
face = face.Faces[0]
corners = [trim.StartVertex.Location for trim in face.OuterLoop.Trims]
When questions are answered, they become answers for other people having the same question.
Thanks !
While I now have a solution to my problem, I’d like McNeel to consider changing how “Deconstruct Brep” outputs the lists of vertices
They already have. Given the discrepancy between R7 and R8, are you really sure you want them to do it again?
Not sure what you are talking about.
I’d like the lists to make sense, that’s all.
We don’t need to resort to scripting for this.
I would be interested to know how or why the difference in starting point results.