Hi everyone,
I’m trying to trim a surface using a set of curves. The problem is that the “Trim” (or Split) operation isn’t cutting the intended surfaces (Surfaces 6 and 7).
Additionally, on Surface 7, the same fragment is being repeated three times, and an unexpected cut appears on Surface 17. I have checked the data structure and it seems that the inputs for the Split component have the same tree structure, but it’s still failing.
Could anyone help me out with this? Thank you in advance!
Dear John,
I have been studying your file now for about 1/2 hour or so. And I see a lot of good stuff, but also several combinations what will not work together and the error of the first goes into the second etc.
To simplify for myself I did two things:
- listed only the two surfaces you need, so I do not get confused by the others.
- checked the extrusions. And saw that splitting the two surfaces with the 9 extrusions, will run OK for about 6 extrusions + 1 surface. The others have the issue that they do not cover the complete surface(s), so a split will be just partly. And that gives a strange open brep instead of 3 nice cutted surfaces.
I understand you were trying to find an approach two cut all in x panels (18); sort them out and; combine them again.
The extended curves were a trial to connect the splitting extensions?
First thing I thought of, I would do to solve this:
- join surfaces where possible (Join Brep)
- Connect the cutting extrusions. For example: Take two (close together) cuttings extrusions, ruled surface in between; join brep, what will turn it into 1 brep.
And hoped this would give better cuts.
But did not, somehow the combined breps do not split the surfaces correctly.
Alternative (what did the job):
- Use the extrusuions to split multiple breps SplitMul
- Using only the problematic surfaces + extrusions, this gives 6 parts as output
- flip matrix (there is your question/answer about the ordening of lists/sets)
what gives a nice result.
Hopefully the result you need
Regards, Eef
Forum_EW.gh (13.6 KB)
Dear Eef,
Thanks a lot for your reply!
Sorry for not adding comments to the code, I should’ve made it easier to follow.
I’m going to take a good look at what you wrote. Thanks again!
Mark a solution.