Ok, that’s actually pretty neat.
It’ll take a moment to get used to it.
The new component basically eliminates the need to press a button to bake an object.
Any chance that when selecting the Grasshopper Bake Content component, the selection could be moved or manipulated right away with the gumball?
Probably. All of the elements are being tracked so theoretically we could have a right-click menu item to say select all objects (or something like that).
Selecting the Grasshopper component currently highligths the objects in the viewport but the parts need to be selected again to be able to manipulate.
Right. Selecting a GH component just changes the display color but doesn’t actually select them in the document because GH objects by default aren’t in the document. But the baker is a little different and we could probably add a “Select all tracked elements” menu item. However, the baker works on all data types (not just geometry, but layers, materials, annotations, blocks, etc). So I don’t know how the selection system would work with that. I’ll need to think through weather this is some feasible or used to add.
Thanks for the reply, Andy. It might be confusing that the highlight is a Rhino highlight… Maybe just don’t have it highlight any geometry. I mean when you bake a layer, the layer isn’t highlighted. So it would be consistent to not highlight anything.
I just noticed the Grasshopper block preview shows the block plane. Very nice!
Hi Martin, in the meantime you could use the latest elefront version which has a node allowing you to select a document object either with a button press on the node or with a fed in boolean value.
So essentially you could bake with the new Rhino bake node and the same boolean set to true that enables live baking could be wired into the elefront select in document.
I’m away from my computer but I think this would mean each time it rebakes it would select it in Rhino at the same time.
May be worth looking into
Thanks Michael, I’m not necessarily looking for a select feature through Grasshopper. I don’t like inconsistencies so I think as written above I’d almost prefer if the component wouldn’t select the object in Rhino. The object looks like it is selected but you cannot do anything with it. I think it is going to confuse a lot of people.
I’ll take a look but to be honest, in the long run, my goal is to get rid of EleFront completely. I’ve used it extensively over the past few years but I was always looking for a native solution.
Oh yes I understand what you mean now thanks for reiterating. Yes Elefront is great but native components are my preference as well!
Hi @kike ,
The Query Model Objects works for blocks that are not nested in other blocks.
And I also could not query blocks by their “names” as it is not populated in the Object name field.
I tried with the elefront reference component as well, but I am getting errors when I try to apply to nested blocks. Does this now work in the developer build? I have attached the files where I am testing this out.
block_bake_cc.3dm (46.6 KB)
block_bake_cc.gh (11.2 KB)
Hi @AndyPayne , thank you for the file and update. I have updated my Rhino WIP just a few hours ago. Your file works fine on my end. However, I am referencing the blocks from Rhino.
When I try to use the updated Bake component, it does not apply the key/pairs to the nested blocks.
Ah. Now, I think I know what you mean when you asked your question about selections. You’re referring to the yellow selection highlight showing up in the .gif I posted… correct? That gif is more of a diagram to show how the different modes work. But you’re right, the baked geometry isn’t actually highlighted when it gets baked. The gif I showed above was part of a presentation I made in powerpoint :)… so it’s not a direct screengrab from Rhino/Grasshopper. Sorry if I misunderstood you’re original question about the selection.
Hi @AndyPayne Andy, looks like a very useful improvement 
Does the baker have an input to specify the layer to bake on? How does that work?
You would just assign the layer using the Model Object Attributes component and the feed the output of that into the baker.
May I ask what else is still in the planning in terms of components for the Rhino 8 release?
For the 8.0 release, we don’t have a lot left to finish. We are working towards an Import and Export Model components which will let you import or export a .3dm file (and eventually other file formats). Also, we plan to go through and modify some of the class names to make them a little less verbose before the SDK freeze date. But, those are the only two major items we have left.
There are still a few more data types/features we expect to add even after Rhino 8 ships, but those can be added at any point.
Hi @AndyPayne
I tested the user text component for the latest WIP, and it seems not able to attach/assign the user string to grasshopper-generated objects to bake with.
Will there be another component that supports the function in the future?
To expand on this, is it possible to bake with block attributes using the same defined userstring assignment at one click?
This should be fixed in the latest WIP and you can now properly assign the User Text attributes prior to baking.
Hi @eobet ,
You can attach a “Deconstruct Plane” component to the T output of the Block Instance Component.
Vector Display of Model Block Instance Z Axis:
Thank you, and as I suspected nothing to do with this new feature! 
(Never used a “transform” output before, so it confused me that the tooltip said it was both a point and a plane.)
