Thanks taz and Tomasz for your replays and links. I will use Daniel's Kangaroo. I thought there must be a possibility not creating the duplicate curves in the first place. The MetaBall component is quite slow, what is your experience?
so metaball isn't a slow solver. david did a really great work @ the development of that marching cube solver.
so i have updated your definition so that it is working without any duplicate curve and really fast
so the magic is to prepare the data structure in that way that it is sorted in z direction in your case
take a look on the attached image or file
greetings from innsbruck to munich ;)
the path mapper is used to clean or adapt the pathstructure
in this case i rebuild the structure from path created from lines to a data structure where each intersection plane @ z has is own path
so turning the points from vertical order to horizontal order
i hope this is a almost clear description
thanks for your compliments
what are you doing in munich?
maybe if you want you can join one of our workshops which we plan to host in the future
i've been having similar difficulties with the metaBall component [speed of solution etc.] i can see how the ordering of the path structure allows for better solution, but can't overcome this when working with a number of inter - connecting curves [as opposed to 'infinite' lines] [where not every plane intersects with every curve in the definition]. i can generate a solution where there are thousands of duplicates, but nothing as clean as the example above. if there are any suggestions how this might be done, it would be great !!
im working with this component for the first time now and downloaded your definition. How can you generate a clean surface with the output lines? As I see on your post at the bottom of your page, U used the plane component und simply extruded the srf. But it doesn't look clean. Is there another way? Thank you. Gruß, Andreas