I am new around here and need some tips on how to “correctly” model streamline/teardrop geometry in Rhino. I am working on a small architectural project and i can’t for the life of me model these geometries (after many attempts) or even know how to approach them correctly. From my own experience, i see 2 ways to approach this process :
Model all the geometry with sharp edges/rough edges and then try to fillet everything
or
Rely heavily on the “streamline” isocurves to inform the geometry by Sweeping e.t.c or use isocurve sections and “surface from network of curves”
Or maybe i am approaching the process in the completely wrong way.
Also, I always manage to get something close to what i envision when i am trying all these methods but i tend to end up backtracking due to some fundamental issues in the geometry and design process.
What are there some fundamental design rules one should follow when you are handling such complex geometries to stop having to backtrack ?
Would be great to get some insight from people who have handled these sort of shapes/geometries before.
Thank you!
Crappy sketch is an early ideation sketch for the pavillion.
Hi Elbert - I think rule #1 for this sort of shape is to keep your surfaces and curves as as simple as you possibly can - the devil is in the details of the design of course, but big swoopy surfaces are often best made with a very low point count if possible and shaped by direct point editing of the surfaces. I’d shy away from Sweep2 and NetorkSrf unless you really have the design pinned down - these tend to make surfaces that are tricky to edit. History can help, but I’d start with Lofting as few and as simple curves as will get you close, and then point editing.
