Thank you for sharing this info with us, this is exactly the project I need to learn the geo nodes stuff I've been putting off.

Man, You are good at what are you doing. Thanks!

It’s like sorcery. You sir are a wizard 🧙‍♀️. Thank you.

So many good tips! Thanks :D

Thanks for the heads up! I'll definitely say hi if I find you over in Vancouver.

Great video I am new to geomety nodes and found this so helpful and your clear explanations really cemented my learning thanks.

Thank you! So inspired!!

I learned more about geo nodes from this than all other intro to geo nodes videos that ive watched

no time to finish this video damn it .. I need to study more about nodes i really like it ;)

Click on 'type' in the node editor's group input properties (the N key), and you'll see you can switch from float, to integer, to vector, etc. You can change the type in the Geometry Node Group editor's properties panel under 'inputs'. It's right over the 'name' field. 'type'. It's a drop down.

This is amazing! :D

Great Tool, Great Tutorial !

wicked, thanks 🙇‍♂

This is actually cool.. Nice video..

you don't need to use a colour node to make a 0-1 output field. you can change the type to float and use min of 0 and max of 1.

This is so unimportant but I can actually give a pretty clear answer on the "fill-ay" - "fill-it" debate (at least in the US). While British English can vary, in American English they are almost certainly two different words. The etymology is already so messy with fillet in a culinary context that it really makes no sense to even try and relate them in any other way than context. The traditional explanation for the etymology is that the word fillet for thinly sliced meat comes from the way string is tied around the meat (There is traditional wear that includes a fillet band which is worn around the head). It is also argued that it could just come from the fact you are making thin slices of things like a band, which is more akin to a leather fillet, however that is pronounced "fill it." I've even seen people say the culinary technique is called sush because of how the meat that is used in such a cut wraps around the animal. Every single person I have ever asked who is going through or went through and engineering program at university agrees that a fillet in the fabrication sense is pronounced "fill it," furthermore I attended university for engineering and that is almost solely where I learned the distinction from. Now, I found some evidence because I was once again tumbling down the rabbit hole of this problem which is far too interesting to me: On a post from a language forum someone included a response from an editor at Mirriam-Webster. "...In response to an email I sent to the editors of the online Mirriam-Webster Dictionary, I received the following reply (in part) 'In the case of "fillet", I would argue that those are actually two different words. They may have the same etymology, but in current English they are homographs and heteronyms.' Joshua S. Guenter, Ph.D. Editor of Pronunciation" I also found someone talking about it from their educational background as well: "As a mechanical engineer, the word "fillet" is always pronounced "Fill-it" when talking about machining and modeling purposes (at least in the US). In this sense, it is the act of machining off a sharp external corner (chamfers are also common, whereas fillets are rounded corners, chamfers are a flat cut). Fillets also describe the material left in an internal corner usually cause by pockets cut by ball end mills (the profile is circular, so cutting a sharp internal edge is generally a difficult and expensive procedure)." To conclude, it appears this is a very understood thing by engineers, fabricators, manufacturers, etc. in the US, however the rest of the world might not agree- which is new to me as of researching this today. I don't think it really matters, I just like having two different words that clearly denote the two very different operations at hand. Furthermore, I do sometimes end up using the two pronounciations side by side if I'm referring to adding a fillet (round) to something so as to not cut into a fillet strap (wrap) that is holding it together. Super niche though. Okay I'm done. *unpushes glasses up*

nice tuto my firt model unsing GN Thank you I wait have more

you can mask out the top face and convert it to a curve

I ran into problems with the leg placement when trying to use Map Range → Subtract; if the underlying cube was too big, the subtract wouldn't be enough to place the legs under the tabletop. Obviously if you're working with tables that are within sane real-world scales it's not an issue, but I ended up changing the Subtracts to Multiply, and mapped the 0-1 roundness range to 0.9-0.7, because making the leg points rectangle vary from 90% to 70% of the bounding box made more sense to me. I also ended up putting the tabletop thickness into a variable, because manually putting in 3cm in various locations offended my programmer's sense of style.

I loved the tutorial, geometry nodes is amazing, congratulations to everyone involved. Well, a small doubt, when I transform it into mesh, the legs disappear, leaving only the body of the table. I tried to put a "curve to mesh" in some parts of the nodes, but I didn't get a result yet :(.

i am really impressed from your work. Please guid me system and led requirements for blender.

Is it possible to set up the legs so that you could procedurally generate lathe turned legs?

cool!

realy helpfull

For the Map Range, wouldn't a simple Math node set to multiply also work? Especially when the roundess input is already limited from 0 to 1. On a small example project like this I agree that the difference is negligible, but I can imagine in large and/or complex projects it could become a significant performance increase to use Math multiply instead. My reasoning is that normally a math multiply should translate to only a single cpu operation, while Map Range is more complex but gives the same result in this case, thus adding unneeded complexity.

It’s easy when you do it… but don’t think I would’ve came up with it on my own. Mind you, this is first time I’m looking at nodes lol.

this is a parametric gold for arcviz

Anyone know how to add the float curve node to the input group so we can access it to change the edge bevel from the modifier?

Leaving the radius of the corners in centimeters would be better for designing purposes.

Nice tutorial but it'd also be helpful if you explained what each node actually does

Great tutorial. I do however get lost at 10:14 when try grab the sides and change the size. Mine looks good as long as its larger than my origional cube, but it doent go smaller than the dimensions of the origional cube. i went back and made sure i had everything set up right. im fairly new to blender so this could just be a noob issue. any help i would appreciate. im running 3.2

at minute 9.84 how you did it make the mix rgb the radius

So when we apply the modifier, we loose the legs , because they are instances? how can we make the table into a full mesh object now?

To create a shape you realy need to build a whole city trafic sistem is crazy

19:39 It’s not really an “editor”, since you can’t “edit” any of the numbers.

Is it me, or is the audio cutting out periodically? It feels like some sentences are either incomplete, or they start at a weird point. (great tutorial regardless, just this thing made it a little weird)

Quite-a-bit to do just to make a table. To me it is way easier to model one and texture it. I am new to nodes so I appreciate the share. :O)

This is torture tho, and a time killer. Appreciate you showing how tedious nodes are.

learning this is brain pain :-)

9:33 I found another way to do it: change the type of that input to “Integer”, then back to “Float”, and it loses the distance units.

noob problem but ctrl+shift+D doesnt work for me. Using 3.2.1 and node wrangler is enabled.

What's the right way to pronounce "fillet"? Captain?

Well, that looked promising at the beginning, but on the 100th node I went back to FreeCAD for my parametric needs 😀

I am extremely weak with geometry nodes, so it is possible I am missing something. I do get the impression that geometry have their use. Like randomizing something that has a large count so it doesn't look so uniform. This table took 30 minutes. If you had used traditional methods, you could have made a better looking one in half the time.

but why?

Hello 🍪

🤣🤣🤣 its been after 8 years I've visited cg Cookie But blender not 3ds max Btw where is the Guy who taught 3Ds max on cg Cookie I think I am really missing his accent Cheers

it is very hard stage, please arrange lower stage for learner

after watch this video we don't need easy way right now for modelling...

I do NOT want to play a game where a creepy worm spider like 1:16 crawls around the level. Ewwwwwwwewweeeewwww

Why not just use houdini? I feel like this is trying to fill a need that is already fulfilled.

sad to say it but they are years if not a couple of decades behind sidefx and their node systems :s

I hate geometry nodes, they blow my mind.

While the preview looks decent, the topology the wireframe shows is atrocious.

its look like over complicated ..

Why do something perfectly usable in 3 minutes when you can do it in 30 with geometry nodes that is at the same time unusable outside of blender? hmmm...

this is why i dont want to do geometry nodes, it is overomplited for a simple object. not the right tool for that job.