Perfect video. This makes so much more sense now and there's so much Grasshopper-type stuff going into it. That bit about nodes looking backwards is really interesting. It lets you reuse a group of nodes without having to duplicate it.
Yes! It took me a few days to work out why it was a good design decision but as soon as I started making tools it became very clear how powerful that is!
This is the ultimate video on fields & geometry nodes which has finally filled up the gaps in my mental model and made it click. Can't thank you enough for this video.
This is an excellent tutorial! Thank you so much for outlining everything in such a clear manner. I really like the delivery, warm and encouraging without dumbing down the content too much
I am just a beginner with blender, but this finesse (round/diamond sockets, with dot or not, wire dashed or continuous...) just surprised me. Very interesting and good to know...
Thank. You. Erindale! I was struggling with how everything fit together coming from the old attribute workflow and this video made a lot of things finally click in my brain.
No honestly it took me a while too. It was when I found out the input nodes are just references to the spreadsheet instead of actual data that I clicked with it.
What would I do without Erindale? Just run around in a field like a headless chicken. Great explanation, as always. Now I understand a little more. THANK YOU! Dg
Thanks for this!--is there a way to use "image texture" and control UV-mapping for displacement with these newer nodes (no more "sample atttribute texture?)..
It is simple. The position and normal nodes are attribute extractors. They look at your geometry and take the position and normal information from the geometry. All the input nodes in ox blood red, do same thing. The name 'input nodes' by blender is what is confusing, they have nothing to input they only have an algorithm that reads your geometry, that is why they can also output fields, because it will give an output based on what it reads which may be a vector, single value or a field (an algorithm).
Do you know why normal shows up in the spread sheet under the face domain if its not an attribute? I thought normals are derived data im a bit confused.
How can I use geometry nodes to actually build a mesh plane, control the position of each point, have the plane portions subdivided into many quads for cloth sim, and also build sewing threads to connect pieces of the object?
You can't create new edges or faces but you can delete faces to leave edges behind. If you're form is possible to make by manipulating a grid or other primitive, or by using the curve to mesh node, then you can delete faces to create sewing threads. In my last test, writing out a group for use as pins in my case didn't work though.
@Erindale If the count of your heads in the thumbnail indicates level of importance of this video then you could add few more :D , thanks mate, now I need some time to process the info... I'm a bit late on all the "Fields" stuff recently added and struggle a lot to get a grasp of it.
Hi Erin, just a stupid question, where do yo find the documentation for new version, I just grab the beta 3 and everything has changed in geometry nodes (just when i was beginning to understand the previous version) tx
The documentation is being updated at the moment and it should all be finished by the stable release of 3.0. I personally look at the developer commits if I need to understand something specific but otherwise I reach my own answers. Bouncing ideas off people in my Discord and directly asking developers in the blender chat have helped as well.
But how do you manipulate vertex groups of instanced geeometry using the "selection" socket? Nothing appears in the modifier properties :( It seems like it only work for the emitter geometry and can't be done for imported geometry.
Just type in the name of the group. The modifier can only query the active object but that doesn't matter. You're just providing a reference to a column in the spreadsheet so if you input the correct name, it'll work
Yes essentially. I think the developers describe them as functions and the attributes are the arguments that are passed in by the context that the function is computed in
Hm sort of. A field is just something that is sampled by the geometry. If it's a position field then it'll return the xyz coordinates of the vertex. If it's a noise field, it'll return the value of the noise formula. If it's an index field, it'll return the index of the geometry element
Buhhhh... Thank you for another tasty knowledge nugget. Btw it would be super funny and simultaneously helpful/professional if you moved your webcam footage off the hierarchy/outliner and put it in it's own reserved space in your Blender layout. Maybe even throw in a Metal Gear Solid-esque filter on the footage (made with nodes of course). I think it would be helpful for people to see the status of the outliner (even though it doesn't change that much) during the process and in general your virtual presence definitely deserves an upgrade given your accelerating notoriety. ;^)
I've binged watched your Geo Nodes playlist somewhat and to be perfectly honest, I've still no idea how Geo Nodes works. I am trying to scatter objects randomly with random rotation on a plane in such a way that, if any of the instances exceed plane dimension, they will be duplicated on opposite side. This is so that it produces a tiling texture effect. Another problem self-intersection. I've no idea how any of this works or how you understand all of this, is there a handbook I could download or something to better explain nodes and common use cases?
You can't check intersections between different instances that have been instanced at the same time. You won't be able to do a tiled scatter without doing something like a grid that you repositioned the points with some tiling noise etc. A lot of this stuff is hard logically because we don't have loops and we don't have an easy way to differentiate between instances after they're realised
@@Erindale So using Distribute Points on Face along with Instance on Points will generate Instances that I cannnot somehow differentiate based on their bounding boxes crossing the plane? What if I had 9 planes arranged as grid tiles? Middle plane would be used for the canvas and the other 8 would filll the boundaries of the canvas in such way that for example, left plane is simply an offset of right plane. This would produce a tileable effect? I will try to fiddle with this tomorrow. I would love if this were possible because baking objects to a texture would be so much easier than me manually scattering or using Particles then making sure everything tiles and deleting intersecting geometry.
If you instance a plane on a grid BUT DON'T REALISE instances then when you distribute points on that grid of planes, they'll have identical distribution patterns and therefore tile and you can instance your objects and realise or do whatever you want afterwards if that helps?
Probably required training here for geometry nodes beginners. If they don't get past this "context" concept, it will be impossible to understand - i didn't see it at first, but now I do. The way I would say it is something like this: A field's data is fed by the geometry data that is input into the green node currently being processed in the pipeline, and is specific to a vertex/point
A field is more like a function. When geometry evaluates the function it creates an array of values that exists on the geometry. For example a noise texture outputs a field. This noise texture is just a perlin noise function. Without vectors from the geometry, it’s not solvable, it requires the geometry to become meaningful. Functionally you’re correct, you’ll only ever see a list of values in the spreadsheet but it’s important to note that that array of values only exists because of the geometry. It cannot be disconnected from the geometry as you could create a list in Python or Grasshopper etc
I guess, if you're a programmer, then you recognize a field as a callback. If you're not a programmer, it's quite a nice way of teaching you what a callback is. 🤓
I don't understand why blender developers always want to reinvent the wheel. they could no longer be inspired by Houdini rather than complicate the workflow. same thing the nodes in c4d are a mess to use. as soon as you go above 50/60 nodes it becomes a mess. in Houdini after 200/300 nodes everything is very clear. congratulations anyway for the quality and clarity of your tutorials.
3.0 is now in Beta so make sure you grab yourself an up-to-date build!
@Astrid Alaniz You should have a Texture category on your add menu? You're definitely using 3.0 with the new Sprite Fright splashscreen?
Does your Toolkit work for Blender 3.0.0 Release as well? I've read it isn't yet possible to add nodes that can take inputs.
@@lajawi. it does! It now has 101 new node groups for the new geometry nodes
Now that’s a thumbnail
Hey cg matter do you have a discord server?
🤣
No half measures around here!
:D
Perfect video. This makes so much more sense now and there's so much Grasshopper-type stuff going into it.
That bit about nodes looking backwards is really interesting. It lets you reuse a group of nodes without having to duplicate it.
Yes! It took me a few days to work out why it was a good design decision but as soon as I started making tools it became very clear how powerful that is!
Dude.... that explanation of fields being in context of the geometry nodes finally made it click for me.
Thanks!!!
I'm glad! Making these videos really helped me pin it down too
This is the ultimate video on fields & geometry nodes which has finally filled up the gaps in my mental model and made it click. Can't thank you enough for this video.
Glad it’s given you that! Enjoy!
Your voice is very calming and easy to understand
OMG I can't wait for the next videos!
This is an excellent tutorial! Thank you so much for outlining everything in such a clear manner. I really like the delivery, warm and encouraging without dumbing down the content too much
I am just a beginner with blender, but this finesse (round/diamond sockets, with dot or not, wire dashed or continuous...) just surprised me. Very interesting and good to know...
Thank. You. Erindale! I was struggling with how everything fit together coming from the old attribute workflow and this video made a lot of things finally click in my brain.
Great to hear! The new system is really powerful once you find your feet
Thanks for the tutorials, really needed an explanation of the latest updates
If this is going to be a series oh boy it's gonna be fun
Getting through these great tutorials nicely...very useful indeed!
dude thank you so much. kept feeling like an idiot not getting what was going on in the new fields nodes but this really helped it click.
No honestly it took me a while too. It was when I found out the input nodes are just references to the spreadsheet instead of actual data that I clicked with it.
This is what I was looking for, the fundamentals! Thank you!
aaaah, best explaination of fields, or geonodes in general i've come over i think. Thank you!
Thanks so much! Glad it's of use
you're the Bob Ross of nodes
also right in time for nodevember c:
Gotta get people skilled up ready!
Best blender Geometry nodes tuts on the interweb
Thanks very much!
Erindale is the way. Got the course on Canopy. So Good. Will be definitely picking up other courses.
Thanks so much 🙌
Very well explained thank you. Fields is a really interesting development
What would I do without Erindale? Just run around in a field like a headless chicken. Great explanation, as always. Now I understand a little more. THANK YOU! Dg
Thanks Dg!
You made it crystal-clear to me! Thanks
I'm glad! Thanks Fabrizio
Fun stuff! Going to make a nodes video this weekend :D
Love the way you explained this thanks a bunch
Thanks for this!--is there a way to use "image texture" and control UV-mapping for displacement with these newer nodes (no more "sample atttribute texture?)..
It is simple. The position and normal nodes are attribute extractors. They look at your geometry and take the position and normal information from the geometry. All the input nodes in ox blood red, do same thing. The name 'input nodes' by blender is what is confusing, they have nothing to input they only have an algorithm that reads your geometry, that is why they can also output fields, because it will give an output based on what it reads which may be a vector, single value or a field (an algorithm).
This was a great tutorial, thanks for sharing your knowledge!
Thank you, fields calculations very well explained. You have addressed the need 😊
Thank you Abhay!
Do you know why normal shows up in the spread sheet under the face domain if its not an attribute? I thought normals are derived data im a bit confused.
Great video! Anyone should watch this before getting into geometry nodes!! Thanks a lot.
How can I use geometry nodes to actually build a mesh plane, control the position of each point, have the plane portions subdivided into many quads for cloth sim, and also build sewing threads to connect pieces of the object?
You can't create new edges or faces but you can delete faces to leave edges behind. If you're form is possible to make by manipulating a grid or other primitive, or by using the curve to mesh node, then you can delete faces to create sewing threads.
In my last test, writing out a group for use as pins in my case didn't work though.
@@Erindale also we'll be getting solvers soon.
Thank you for making these videos. they are supper handy.
Thanks! More to come!
@Erindale If the count of your heads in the thumbnail indicates level of importance of this video then you could add few more :D , thanks mate, now I need some time to process the info... I'm a bit late on all the "Fields" stuff recently added and struggle a lot to get a grasp of it.
Haha I've never liked faces on thumbnails but I wanted people to see these 101 videos 😂
This is incredibly well explained! Thank you so much! 🙂
Thanks so much! Glad it's useful
This is essential information! Thanks.
Thanks for confirming my assumption on how this works. Very well explained.
Thank you!
Thanks, brother! You're the man!
Hi Erin, just a stupid question, where do yo find the documentation for new version, I just grab the beta 3 and everything has changed in geometry nodes (just when i was beginning to understand the previous version) tx
The documentation is being updated at the moment and it should all be finished by the stable release of 3.0.
I personally look at the developer commits if I need to understand something specific but otherwise I reach my own answers. Bouncing ideas off people in my Discord and directly asking developers in the blender chat have helped as well.
@@Erindale thanks
Great explanation
But how do you manipulate vertex groups of instanced geeometry using the "selection" socket? Nothing appears in the modifier properties :( It seems like it only work for the emitter geometry and can't be done for imported geometry.
Just type in the name of the group. The modifier can only query the active object but that doesn't matter. You're just providing a reference to a column in the spreadsheet so if you input the correct name, it'll work
@@Erindale thanks, I would never figure that out😂👍
I'm learning so much 😄
great video!
Thanks so much!
You're amazing.
Spectacular thumbnail
Could you say that a field is like an algeritme it uses the data from the geometry to calculate the output value.
Yes essentially. I think the developers describe them as functions and the attributes are the arguments that are passed in by the context that the function is computed in
Some featutres I was hoping for since years!
Thanks! So generally fields in gn are same as in Sverchok?
Hm sort of. A field is just something that is sampled by the geometry. If it's a position field then it'll return the xyz coordinates of the vertex. If it's a noise field, it'll return the value of the noise formula. If it's an index field, it'll return the index of the geometry element
@@Erindale in this case I just hope they works more comprehensive than those in Sverchok.
That's exactly what I wanna know，Ty!
Great Great explaination
thank you man
Which Blender should I use so that I can use fields?
Blender 3 beta or 3.1 Alpha. 2.93 does NOT have them.
Buhhhh... Thank you for another tasty knowledge nugget. Btw it would be super funny and simultaneously helpful/professional if you moved your webcam footage off the hierarchy/outliner and put it in it's own reserved space in your Blender layout. Maybe even throw in a Metal Gear Solid-esque filter on the footage (made with nodes of course). I think it would be helpful for people to see the status of the outliner (even though it doesn't change that much) during the process and in general your virtual presence definitely deserves an upgrade given your accelerating notoriety. ;^)
Hahaha thanks! I should tweak my UI! I've always just relied on my procedural workflow being pretty minimal on new objects
oh, i remember u from the blender splash screen art work explainer vid, right??
That's me!
I've binged watched your Geo Nodes playlist somewhat and to be perfectly honest, I've still no idea how Geo Nodes works. I am trying to scatter objects randomly with random rotation on a plane in such a way that, if any of the instances exceed plane dimension, they will be duplicated on opposite side. This is so that it produces a tiling texture effect. Another problem self-intersection. I've no idea how any of this works or how you understand all of this, is there a handbook I could download or something to better explain nodes and common use cases?
You can't check intersections between different instances that have been instanced at the same time. You won't be able to do a tiled scatter without doing something like a grid that you repositioned the points with some tiling noise etc. A lot of this stuff is hard logically because we don't have loops and we don't have an easy way to differentiate between instances after they're realised
@@Erindale So using Distribute Points on Face along with Instance on Points will generate Instances that I cannnot somehow differentiate based on their bounding boxes crossing the plane? What if I had 9 planes arranged as grid tiles? Middle plane would be used for the canvas and the other 8 would filll the boundaries of the canvas in such way that for example, left plane is simply an offset of right plane. This would produce a tileable effect? I will try to fiddle with this tomorrow. I would love if this were possible because baking objects to a texture would be so much easier than me manually scattering or using Particles then making sure everything tiles and deleting intersecting geometry.
If you instance a plane on a grid BUT DON'T REALISE instances then when you distribute points on that grid of planes, they'll have identical distribution patterns and therefore tile and you can instance your objects and realise or do whatever you want afterwards if that helps?
@@Erindale Yeah, that actually might work!
Thank you!
Probably required training here for geometry nodes beginners.
If they don't get past this "context" concept, it will be impossible to understand - i didn't see it at first, but now I do.
The way I would say it is something like this:
A field's data is fed by the geometry data that is input into the green node currently being processed in the pipeline, and is specific to a vertex/point
that's one JUMBO thumbnail
Got to show I mean business!
Does your course have Vietnamese subscribers?
So basically field is an array of values, right?
A field is more like a function. When geometry evaluates the function it creates an array of values that exists on the geometry. For example a noise texture outputs a field. This noise texture is just a perlin noise function. Without vectors from the geometry, it’s not solvable, it requires the geometry to become meaningful.
Functionally you’re correct, you’ll only ever see a list of values in the spreadsheet but it’s important to note that that array of values only exists because of the geometry. It cannot be disconnected from the geometry as you could create a list in Python or Grasshopper etc
@@Erindale I see now, Thanks.
I guess, if you're a programmer, then you recognize a field as a callback. If you're not a programmer, it's quite a nice way of teaching you what a callback is. 🤓
I've never heard of that! I wonder if all this node work will have given me enough context to start learning programming
agree, i too was going to mention that fields are basically higher-order functions
In case someone searches for "Scale" node. Its in the "Vector" group --> "Vector Math" --> select in dropdown menu.
In 3.2 or higher you can also just drag off the socket and then search scale in the popup
Please make Aura, beam attacks and other anime related things using geometry nodes! That would be so amazing.
✌
What would be do without you :)
What a Clickbaity thumbnail!
Great video as always, Its ri8 on time for nodevember!
I literally just told Steph I wouldn't put my face on a thumbnail and I couldn't stop thinking about it 😂
@@Erindale works XD, it made me click it LOL
I don't understand why blender developers always want to reinvent the wheel. they could no longer be inspired by Houdini rather than complicate the workflow. same thing the nodes in c4d are a mess to use. as soon as you go above 50/60 nodes it becomes a mess. in Houdini after 200/300 nodes everything is very clear. congratulations anyway for the quality and clarity of your tutorials.