I have this geometry, and a standard “Fillet Edge” node—with edges connected via “Edges from Points”—is causing both Rhino and Grasshopper to freeze. I had an idea to identify the problematic edges using a script:
Then, I wanted to remove those problematic elements using “Cull Index,” but the script requires the node to execute first—and right now, it just hangs.
I really hope you have some ideas on how to create a rounded edge on this model
Grafting the Brep list allows Grasshopper to correlate each Brep with each branch of the point tree. The original script was likely orders of magnitude more computationally expensive to run because it was applying each branch of the point tree to the entire Brep list.
Your current script is somewhat flawed because the FilEdge component is looking for the indices of the edges to fillet, not the curves. Luckily, you’re already getting the indices from the exact same component, so the fix is simple. You can also reduce the complexity of your script in pretty simple ways to make the computation faster.
Unfortunately Rhino has issues with filleting in general (just browse the forums for a bit and you’ll see what I mean), so Grasshopper has the same issues because the native components use the same backend.
Smaller fillets, dynamically choosing fillets based on the edge, choosing different filleting options like rail distance or rolling ball, or repairing the broken fillets after the fact are all options you may be able to pursue. Something I’ve heard of people doing for shoe design is to create a parent hexagonal element, fillet that, then copy and deform it repeatedly to fit the pattern of the sole - some food for thought.
