algorithmic modeling for Rhino
the mesh(+) user object set has been significantly updated repairing several errors, clarifying component structure and adding new component types.
Updates for v1_02 include:
-version 1_02 introduces new nGon components which duplicate the functionality of the mesh face Subdivide and mesh face Effect components, but allow for vertex inputs of more that 4 points. Inputs are a list of points which should generally be arrayed around a center point for best results. Normals are calculated by using the clockwise points in a sequence to determine a plane from which the z axis is extracted. These are then averaged. The center point is determined by the averaged sum of all the points in the set. Each “face” should be defined by a single list of points.
- major overhaul to all components structure, reducing redundancy and unifying an approach to vertex creation using a loop structure, which is much cleaner and easier to adapt.
- all component inputs have been restructured for consistency and clarity.
- component icons have been color coded by type
- new component prefix n(+) indicated that the components inputs are point based to distinguish from mesh face based inputs where there is redundancy in effects between the two.
- unification of mesh vertex sequences and face directions across all components. Activation of mesh face normals, which were previously absent.
Comment
cool!
ok thanks ill try
That may be the issue.
The components are tested for grasshopper 0.9 revision 14, the last release for rhino 4.
grasshopper 04
Which version of grasshopper are you currently running?
fracmostofi,
Ive just tested a component from each set in Rhino 4 and it seems to be working.
Can you give me more information about how it is not working?
Are you using the latest (and last) version of grasshopper for rhino 4?
Did you place the user objects in the user objects folder?
thanks
my mesh(+) is not working is this problem about rhino 04?
sweet!
Cool stuff, David!
Have you thought about using Turtle to handle ngons? It would be easier to move out from point lists and you'd use a data structure that is more suitable for the task. Also, users would not need to know the difference between n(+) and mesh inputs. Otherwise, it's great stuff here! :)
Welcome to
Grasshopper
© 2024 Created by Scott Davidson. Powered by
You need to be a member of Grasshopper to add comments!