This approach also enables you to benefit from the entire capabilities of the CADiNP syntax. So bypassing the “bake”-process by direct scripting a CADiNP input file (Teddy) for SOFiSTiK is the way to go. When intending to create highly parametrised models with Grasshopper – I recommended keeping the link to maintain the generated structure. Any updates happen in Grasshopper must be updated again by “baking”. As the elements are “baked” from Grasshopper, the active link between Grasshopper and McNeel Rhinoceros is disconnected. The “baked” geometry within McNeel Rhinoceros is now available to process further (meshing + generate elements into SOFiSTiK). McNeel Rhinoceros (creates Rhino object from Grasshopper input). Elements created in Grasshopper can be “baked” into To achieve a more efficient workflow generating structures with McNeel Rhinoceros – combining the SOFiSTiK Rhino-Interface with the Grasshopper-Interface is possible and widely used for less parametrised models.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |