Rhino Components Replacing instead of Baking

[ShynnSup]

I have a curve that is referenced from Rhino Model.

This is before baking: The curve is red and in layer ‘Default’

My idea is to duplicate the curve into a new layer, this is what baking is supposed to do.

This is after baking:

Not only is my original curve deleted and moved into Boundary Curve layer (now white), but it is also now being referenced into the Grasshopper!

Taking the liberty of tagging you guys.
@scottd @andyopayne

bake curve.gh (12.0 KB)
curve.3dm (46.6 KB)

[Japhy]

Correct, you’ve turned your Rhino curve into a Model Object and made the change. If you don’t want to change the original Curve you’ll need to copy it instead of turning it into a Model Object, something like this…

[ShynnSup]

That is super unnecessary and confusing. That is not what bake means.

In fact that’s not what this bake does.

Nor this one.

@scottd

• 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.

@Japhy

it instead of turning it into a Model Object, something like this…

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.

[martinsiegrist]

Don’t plug the curve into the Model Object input. What happens when you plug it into the geometry input?

[ShynnSup]

@martinsiegrist

Don’t plug the curve into the Model Object input. What happens when you plug it into the geometry input?

That works as expected, thank you!