ShynnSup
(Shynn Sup)
November 20, 2024, 7:21pm
3
That is super unnecessary and confusing. That is not what bake means.
In fact that’s not what this bake does.
Nor this one.
Purge - Removes the referenced objects from the Rhino document. This can include normal Rhino objects, but also document level objects such as block definitions, layer definitions, annotation styles, and material definitions. Like Rhino, only elements that are not “in use” can be purged. For instance, if a layer contains objects it cannot be purged until those objects are deleted or moved to another layer.
Pull - Pull Rhino objects into Grasshopper. Included in the Pull is the object’s ID, which can be used to edit, replace, or update the specific object later by Grasshopper.
Push - This takes the object and pushes it into Rhino. For instance, a classic geometry type will be placed in the Rhino document. By default, Grasshopper will continue to track this object, so any future updates will replace the object instead of duplicating it.
Bake - This will take the Grasshopper contents and create them in Rhino, but then forget about the objects. This can be used to create new Rhino objects each cycle. This differs from Push in that Bake will also create duplicate objects in Rhino.
The only reason I “turned it into a model object” is because that is the only way that I know Rhino components allow the user to assign a layer to an object.