Embarking on a journey of workflow transformation is never a decision made lightly. It all started when my post-grad requirements came in the mail, I had tried using Grasshopper in the past but to no avail. Coming from a background of Dynamo, I began to realize the potential benefits of exploring other tools or certain limitations between the software packages. This blog post chronicles my transition from Dynamo to Grasshopper and Rhino 7.0, a decision that would ultimately reshape the way I approach the Architecture Industry.
Why I Chose to Make the Switch:
To cut to the point the main reason that I decided to ultimately switch my entire workflow is the improved functionality and extended reach of additional software packages and their capability to branch to every aspect of imaginable field. The decision to transition was driven by a combination of factors. Grasshopper and Rhino 7.0 offered a seamless integration of parametric modeling and visual scripting, providing a level of flexibility and precision that Dynamo couldn't match. Additionally, the extensive plugin ecosystem in Rhino allowed me to tap into a broader range of tools and resources, making complex tasks more manageable. Not only that you can develop micro scripts to then save, and create an ecosystem of scripts that can work in tandem supporting the most complex simulations possible only available through a Grasshopper and Rhino pathway.
Getting My Rhino 7.0 License:
I had never had a license from Rhino because the trial was short it seemed when I was younger but One month is enough. But finally I decided that it was time to get my license and so I checked the original price and remember there maybe resellers so check them out for an additional savings also for being a student you get a discount.
Adapting to Grasshopper:
Adapting to Grasshopper was initially a learning curve, but with persistence and the right resources, I began to see significant progress. I found that i would come across certain issues i didn't know how to solve or couldn't find the correct node and watching Youtube videos or commenting in the community forums and reading through similar problems the solution would always come about. The community forums were invaluable in providing specific details key to process that lead to more complex ideas. I would say I still relied on the way I though or approached learned from Dynamo was applicable and transferable in this case. It was essential to approach it systematically, breaking down complex tasks into manageable steps and gradually building on my knowledge. Also I learned through my post grad studies that it was easier to create separate specific scripts that could correlate and created synergies when combined. You have to admire the way that McNeel and his team of scientists, data analysts and mathematicians including Physicists were so accurate in their approach to designing Rhino and Grasshopper as an ecosystem. Because they act like they are linked and Revit and Dynamo still struggles to deal with this particular issue.
The Benefits of Using Grasshopper and Rhino 7.0:
The transition to Grasshopper and Rhino 7.0 brought a multitude of benefits to my workflow. One notable advantage was the graph mappers and attractor's functionality, it seems it is more feature rich and just executes alot better in Grasshopper than Dynamo. This allowed me to develop small scripts that then added key features to certain scripts but that can be customized in many ways in order to suit the needs of each alteration. Additionally, the seamless compatibility between Grasshopper and Rhino allowed for a more fluid design process, resulting in a complete sustainability and environmental analysis to be run from within Grasshopper.
Special Mention
A special mention has to go out to Group 7 of CPROEN. Together we made this project using Rhino 7.0, Ladybug tools, Radiance, Open Studio, Energy Plus, and many other plugins in order to create every part of the design seen below.
Comments