algorithmic modeling for Rhino
I am trying to use the index integers from the 3D Proximity Component to create mesh faces. When I define the mesh faces with the given indexes, the algorithm structure I a using seems to be creating at least one face per set of three points. I am want exactly one face per set of three points.
I have attached a demonstration of what I'm talking about. I use a few weaverbird components to show the problem clearly
I can think of two ways of solving this:
1. Find a way of defining the mesh faces which does not cause redundancies.
2. Delete redundant face definitions
a. i can check for redundancies in the sets of index integers used to define faces. This could be easiest in that i would be comparing sets of numbers
b. i can check for redundancies in the set of face representations of the output.
Any suggestions would be great. Thanks!!
Best
--
Kero
Tags:
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by