Help with attractor perforation

[Vladyslav_Lutsyk]

Hi! I want to make perforation with crv attractor. It looks almost right, but when I zoom in, I see this, several circles in one. I know that its problem with tree, but I don’t know how to fix it. Can anyone help me?

[inno]

please post your gh file with internalized geometries

read this: Help Us Help You - #10

in particular this:

@DavidRutten

3. Attach minimal versions of all the relevant files
If you have a gh file you have a question about, attach it to the post. Do not expect that people will recreate a file based on a screen-shot because that’s a lot of pointless work. It’s also a good idea to remove everything non-essential from a gh file. You can use the Internalise Data menu option to cut everything to the left of a parameter:

Simplifying a Grasshopper network

If you are referencing curves or breps or meshes from Rhino, you can also internalise them so you won’t have to post a 3dm file as well as a gh file. If you’re unsure whether all the relevant data is internal to the gh file, try opening it in an empty Rhino. Does it work? Good. No? You’ll need to internalise more.

[Vladyslav_Lutsyk]

attractor perf 2025 01 15.gh (50.1 KB)

[Asger_Christensen]

attractor perf 2025 01 15.gh (53.3 KB)

Here is a more pragmatic and less laggy solution

[inno]

there are a few things going on
you first have created a triangular grid of cells, then have exploded those triangles to get their vertexes, but keep in mind that you have MANY overlapping vertexes

when you explode a closed Polyline, first and last point of the Polyline overlap
and if your Polylines are an array with all edges in common, then all the pairs of points of each edge are shared with the neighbor Polyline

original number of points is 125 thousands:

but the real amount of unique points is 15876, the rest are just duplicates of those:

this thing alone already brings the Point in Curve calculation down to 9 seconds from the 1.2 MINUTES it was before

but we can do more: by using Closest Point on the Boundary Surface created on your initial planar curve, the total calculation time goes down to 1.3 seconds

my suggestion is to not be tempted to use plugin components that do a lot of work for you (instead of you) like the Attractor component of Lunchbox, but to build it yourself, in such a way to become very familiar with the reason why things happen, and develop your own workflow, for instance:

attractor perf 2025 01 15_inno.gh (56.8 KB)

[Vladyslav_Lutsyk]

thanks!