Geometry Nodes

[thinsoldier]

How can I shade smooth the object on the right?

[Xeofrios]

You have to connect a positive value to the group ouput and name the ouput as shade_smooth in the modifier

[Xeofrios]

It works in my build from 2-3 days ago, I’ll check in the latest

[Poligonete (Isaac)]

@zeauro

I don’t understand how this node is supposed to work.
Are people able to obtain something from it ? The screencapture on patch page does not help.

Yes, it seems broken. I just filled a bug repport.
 
 

@thinsoldier

How can I shade smooth the object on the right?

 
I’m not sure if this is the propper way but…

We can now capture and output attributes with the Attribute Capture node. So we can create one and connect it to the Group Output.

This makes possible for us to choose a name in the the Modifiers Pannel. If the chosen name exists we’ll be changing that attribute. In the image ‘shade_smooth’ is a reserved name so we’ll be changing its value.

In the last video shared in the thread Dalai explains that we can even put the names of Vertex Groups here and change their values directly with geo nodes. And that’s preeetty cool

I guess that an autocomplete feature is planned and also being able to use attributes exposed here in the Shader nodes in Eevee (we can use attributes made in GN in the Shader Nodes only in Cycles for now).

[BD3D (Dorian B.)]

@Poligonete

We can now capture and output attributes with the Attribute Capture node. So we can create one and connect it to the Group Output.

Isn’t there an “Attribute get” node that outputs a field already?

Also, there was an attribute input node in here from the field prototype, i suppose that it will come soon right?

These two ways to grab an attribute would resolve the shade_smooth problem from above.

i’m sure they will be re-introduced soon

[SteffenD (Steffen Dünner)]

I’m pretty sure this will come soon.
I hope in the end there will be “Get Attribute” and “Set Attribute” nodes which are able to read and write arbitrary (i.e. attributes that you create and name) and “factory” attributes (like “position”, “normal”, “shade_smooth”, …) just like in the software with the big “H” (where they are called “Bind” and “Bind Export”) or in the good old software with the “S” that got killed by “AD” some years ago where these nodes were called “Get Data” and “Set Data”.

[BD3D (Dorian B.)]

@SteffenD

“Get Attribute” and “Set Attribute”

Yeah i want “Get/Set” naming too, so elegant and simple

i think they really want their “Store/Freeze/Capture/Persistent” terms.
we can always create our own nodegroups or change the label i guess

[SteffenD (Steffen Dünner)]

On a side note: I’m using nodes in real production since about 15 years now (in S and H ) and I still don’t understand what that “Attribute Capture” node is supposed to do.

[zeauro]

OK. My mistake was to write “shade_smooth” as name of output but not as the output itself in the modifier.

So, attribute capture node is not necessary. Boolean can be specified in Group output.

[BD3D (Dorian B.)]

@SteffenD

“Attribute Capture” node is supposed to do.

I think it’s like an attr get followed by an attr set.

[Poligonete (Isaac)]

@BD3D

Isn’t there an “Attribute get” node that outputs a field already?

Also, there was an attribute input node in here from the field prototype, i suppose that it will come soon right?

I’m sure devs are aware of things like these. I guess they’ll try to commit all the changes as soon as possible.

Not only because Blender 3.0 will be released in December but because in November there is the nodevember challenge

@zeauro

So, attribute capture node is not necessary. Boolean can be specified in Group output.

Oh I didn’t now that, thanks!

[zeauro]

I think I got it.
If you set the attribute socket only on Group Output node, all geometry is smoothed.
But if you use attribute capture nodes, you can set different values for different portion of geometry.

[Xeofrios]

From the wiki

The Attribute Capture node stores data from its input on a geometry so it is carried forward to other nodes, allowing the use of the same data in a different context

So for example if you rotate your mesh using a transform node and then want a mask using the position coordinates before the rotation, you would “capture” the position data from the previous geometry.

Earlier the node was named Attribute Freeze in the prototype which I personally think was a better name because many confuse “capture” with something like “store” or “set”.

Have a look at this post from devtalk

Fields and Anonymous Attributes [Proposal]

[BD3D (Dorian B.)]

@BD3D

Also, there was an attribute input node in here from the field prototype

Yeah i confirm that

These two nodes are not yet implemented in 3.0

[Charles_Weaver (Chuck)]

Here are some notes from the 2021-08-09 geometry nodes sub module meeting that explain the choice of naming a bit more:

• Attribute Freeze
  • Attribute Freeze This implies it is not interpolated afterwards, i.e. it wouldn’t change
  • Attribute Lock Same as above
  • Propagate Value as Attribute “Value” sounds single
  • Propagate Attribute A bit vague, and propogation happens anyway, without the node
  • Attribute Snapshot It implies it is frozen in time
  • Attribute Store Was strongly considered, but the node only temporarily keeps that data, store may be misleading
  • Attribute Keep Same problem as “Store”
  • Attribute Hold / Hold Attribute Keep it out, doesn’t work well enough as a metaphor
  • Attribute Catch Implies motion, feels very physical
  • Attribute Capture / Capture Attribute

2021-08-09 - 2021-9-03 Geometry Nodes Sub-Module Meetings

[Poligonete (Isaac)]

Just a quick note for anyone trying the (field) Proximity Node: looks like recents changes made all geometry an instance by default. This means that in order to work you need to put a “Realize Instances” node before this node.

Edit: I’m not a native english speaker but… is “Realize” correct? Because “Realize Instances” sounds like the dev trying to say that the node is “Making real instances” but the verb “realize” means something different in english afaik

 
 
This doesn’t work

 
 
This does works

[Charles_Weaver (Chuck)]

Oxford says:

give actual or physical form to.

“the stage designs have been beautifully realized”

Though it is technically valid (by the third uncommonly used definition), my personal opinion is that “make instances real” sounds better. One particular reason is that it is already used as the name of a blender operator that does the exact same effect. Why change the name if people are already used to it?

I’m not too worried about it though. Naming can be difficult and give annoying results, but I’d rather have other annoyances like the dashy lines fixed.

[Hadriscus]

That makes sense. However it goes against the new guidelines of “verbs first”. It should probably be “capture attribute” instead.

[Xeofrios]

Yeah, people get used to the naming and it does not generally become a problem in the long run. Because we all are acquainted with the previous attribute workflow and the prototypes, we are confusing the Attribute Capture with Attribute Store. I don’t think it will be a problem in long run or confuse newcomers.

[hillsville]

Hi,

I’m using a MacPro (2013 version with 24 gb, and the AMD FirePro D700 6 GB graphic card).

I’m using Geometry Nodes to populate large fields of plants, i.e.,

corn, wheat, etc.

It brings the computer to it’s knees – click and spinning beach ball.

Do you know if more ram would help?