algorithmic modeling for Rhino
Hi David,
Just a note to say m+2 is really useful! Thought you might be interested in this example I put together trying to figure out how things work. When I did something like this back it the day it was a bit of nightmare - this is much more streamlined.
I must admit, matching face edge angles w/ ea face edge midpoint was a bit of a noodle baker (hence the sorting operations to get everything uniform).
Maybe I can streamline some more...
http://www.grasshopper3d.com/forum/topics/mesh-offset-by-face-norma...
Tags:
BTW, any future plans to allow turtle/plankton mesh compatibility for n-gon mesh faces?
That's the plan for the next iteration, it will make alot of things MUCH easier, particularly ngon based subdivision.
I'm going to move from user objects to a full .gha so that referencing libraries will be easier, etc.
Also planning to implement a Rhino side version as well.
Probably going to wait for Rhino 6 / GH 2 to see what the native meshing capabilities are going to be though.
For right now, I'm shifting emphasis to the next version of bumblebee, based on alot of work Konrad Sobon has done on the Dynamo version.
And got something new on the horizon as well that I hope to kick off at the AEC hackathon.
Cool, good to hear! I was taking a poke around under the hood (since your code is exposed...) and I can see everything is set-up for quads and tris.
Now I remember why I had to use ngon surfaces back in the day (but very sloooow).
Good luck with BB.
Welcome to
Grasshopper
© 2024 Created by Scott Davidson. Powered by