#Rhino models code#

Finally, I wanted to mention that Revit is home to Dynamo, which is its code visualizer. These constraints can sometimes be frustrating to use but it leads to a more stable model that can handle a lot of different documentation data. The workflow in Revit is fairly rigid with features like constraints and reference planes. It uses a Breps-based modeling system which creates closed geometry. Revit on the other hand is hyper specialized in creating construction documentation with an end-goal of documentation coordination and BIM management.

All of these aspects make Rhino a really versatile modeling tool that can handle many different projects and file types. One of rhino's biggest pluses is that it's home to grasshopper which is Rhino's visual coder for parametric modeling. This modeling engine creates really accurate and precise geometry while having a light processing load on your computer. It's based on a NURBS modeling system which can create highly accurate, complex curves and surfaces. Rhino is a program that prioritizes design computation, which is great if you want to work through iterative designs of your project. This section will be most helpful for those who have a strong preference or experience level with just one of these programs. In this lesson, I'll cover both program strengths and weaknesses and when you might want to move between the two. Whatever your goals are, you likely have a general idea of how you want to use the Rhino-Revit workflow. Maybe you're an avid Rhino user that begrudgingly needs to use Revit for construction documentation, or you could be a strong Revit user that wants to expand your toolbox into Rhino. I imagine that many taking this course will have a preferred design program.

Rhino models