Video

Incredibly helpful. Thank you my guy

Incredibly well explained! I'm glad I found this as my introduction to geometry nodes. I'm still a total beginner with Blender, but I'm amazed at what it can do.

greg, this is an extremely valuable video, i find it really useful. you truly dive deep into the holes and present the findings so clearly and elegantly. as a severe RHS patient myself, i salute you, greg, thank you.

Some pointers with displacement, bump, and normal maps. Displacement: Can be height field (like a bump map) or a vector displacement map, which connects to the material output. So all shaders will be affected by it. You don't *have* to use true microdisplacement to use it (there is a setting for bump only), but I would recommend it; if the height field texture map is to be used as a bump map, you can use microdisplacement to find the ideal displacement height and use that as bump distance (bump effect always 1). Bump maps: Can only be a height field map, but the result is plugged into individual shaders instead of on the material level, so you can have a bumpy substrate with a smooth topcoat, impossible with displacement without additional model for the smooth part. Ideally you should only use Bump Strength 1 and adjust Bump Distance (or the height input) instead to obtain ground truth normals that reflects what a displacement would do. Adjusting Bump Strength below 1 tend to introduce some weird clipping of the input. Bump maps requires on the fly *CALCULATIONS* of the new normals, something a normal map provides by simple lookup. Because of that, it is scale dependent. More on that below. Bump maps require no UV layout and less prone to brake (i.e. box mapping), are way more flexible to mix and match, and using the microdisplacement trick (above) you can find out the distance to use or spot if there is any math functions that break down easily. Bump maps are best used for small details because stepping issues will be less visible, but does add computing time. Normal maps: These provide the normal offsets by simply looking up the color. However, to work properly these require a UV layout, are tricky as hell to mix and match (correctly), and can be prone to errors (box mapping). The angles in a normal map are *NOT* affected by texture density, as the color lookup remains the same. It's as if it's the height of the mountain was automatically reduced to maintain the angles, compared to the bump map where the height is maintained (producing steeper angles). Make a triangle wave and array it. Scale on all axis gives you what normal maps do. Scale on x axis only give you want bump maps do (without accounting for it, anyway). Normal maps are preferred by game engines, since angles don't have to be computed (by the bump map slopes) and thus impact performance less. They are also better used for large details like large chamfers since it's done with a single color indicating that angle instead of a gradient. Which means you typically get away with smaller maps and 8 bit (per channel) instead of large 16/32 bit floating point maps to handle gradients (if stepping is a problem) for bump maps.

Note that under object data properties there is a texture space tab. Using generated (and/or object) texture coordinates you can adjust the position and size of the bounding box that is used. If using XYZ tangents for anisotropic shading and it looks off from what you'd expect, chances are the texture space has been automatically updated to something less than ideal. Generated will use 0-1 in XYZ for the bounding box, whereas Object will use origo and allow negative coordinates in unclamped space. The old modulo math function was prone to breaking with negative numbers, so had to account for that, whereas the new (truncated?) fixes those issues. Generated also accounts for some modifiers like bending. Object coordinates are great for box mapped objects, but we have to adjust the coordinate orientation to change how the mapping aligns, as there are no way to rotate the coordinate system with nodes prior to be used for the image texture node.

Use case for strings I'm constantly using, is showing a bunch of information related to the object. I'm working with blended projectors and LCD/LED video walls, and some of the information I show are: Aspect ratio, overlap (pixels, projectors only), individual image resolution (per cabinet), total resolution (per video wall), calculated pixel density/size (to determine readability), lens shift and throw calculations (within physical limitations?), and what projector screen is being utilized (may vary with size due to production limitations). Snapshots of this is then used internally to discuss around the solution, and maybe sent to gfx to prepare pixel perfect content to be used in the final renderings (although I use UV vector snap to force anything pixel perfect anyway). Sometimes things are used for communication purposes rather than rendering. One problem is since having to use nodes for separators, concatenations, and special characters, it can get really messy really fast, so all this is dropped into a separate node group. I wish there was a more elegant way of doing this using a multiline expression interpreter.

the yv map node works correctly when baking?

this... is the BEST geometry nodes vídeo for begginers i ever seen!!

God bless you for this

VERY HELPFUL TYSM

damn, this video is a gem. the best I've seen about r3f fundamentals, really helpful

This is soo good 👍 thanks 🙏

Every sec of the video was worth watching

Thank you for that video. Learned a lot from it. Though what I was really hoping was that you'd show how to make a node that would stitch around a shape, rather than just being a circle

Drei is 3 in german - so i believe it would be pronounced "dry" in english :)

13:00 hey, might be bit late, but wanted to point out that you can also unstage selected ranges in vscode, so you could just stage the full file and unstage things you wanted to keep for next commit

part 3 boss! please and thank you!

Thank you for covering a lot of sub topics without going deep too much! I learned a lot

.

Exactly. I never found any tutorial showing me which nodes to use when and why...

Man, you are the reason why CZcams is such an awesome platform. Thank you so much for this golden course!

i'm a beginner in 3D art and design world, i've chose Blender, so i'm a beginner in Geo nodes and these information are very useful to me, i git the concept, thanks sooooooooo much

What everyone else has been saying: don't stop making videos like these. I'm here for any and all tangents.

🥰Excellently explained.

Thanks my friend you saved me

PG Vector is good, last I heard ankane is working with AWS to integrate PG Vector with sql databases on AWS RDS

if you want "search" in GN without having to click with the mouse, after Shift+A, click "s" , then type what you're looking for.

@ the end: I'm not certain, but I would assume material index refers to material slots per object. You can have multiple materials on separate parts of a single object using material slots. One thing that would make sense is to put the material selection as a group input, so the user can add whichever material they want right in the modifier.

Yes! The "why" is super important!

This is absolutely the best explanation of embeddings I have ever seen. Thanks so much for this excellent video!

Thank you, Mr. Professor!╰(*°▽°*)╯ I've watched many videos, and each of them varies in style. I couldn't replicate what I did because I kind of mixed what I learned from them, which confused me. This opened a window that I was passing by every time. I didn't learn basketball by imitating Michael Jordan; I realized at a later age that the key was to understand and master the fundamentals. Thank you for sharing the fundamentals. I'm subscribed. 😍

This is a lovely introduction! I love that you compared the two libaries side by side. Your explanations are concise and effective. Thank you!

Sir. What about using this in JS and MongoDB

Something that I think missed is "performance"

awesome! as for now, we can use open ai assitant to simplify all these?

Amazing video! Thanks. It was uncanny how questions would be popping in my head and you'd answer them in the next sentence lol. Thanks again

Great video with awesome explanations... well done

So I'm trying to make the results of the geometry node stitching pattern into an editable mesh (just to understand the process). It can't be "applied" if the underlying geometry is a curve that is the basic reference point (it comes back with an error "Cannot apply constructive modifiers on curve. Convert curve to mesh in order to apply.)" If I convert the curve to a mesh first, the geometry node doesn't produce the correct result because it was based on operations from a curve. I'm stumped on this one, if anyone has a suggestion.

Very helpful tutorial. Learned a great deal as a Geo Node beginner! Thanks!

too much mumbling, lightning fast mouse moves, no explanation of what you're doing. Added to differences in blender versions (I'm working with blender 4.1) I have to conclude that this video is NOT FOR BEGINNERS 😭 And since I'm a beginner, I'm not able to follow along. Applying the texture to the flatten cylinder was my breaking point. I couldn't even get that done. The sides of the cylinder wouldn't be textured (after Shade Smooth) and after that almost all options used were not in my blender version... disappointed 😦 for instance: around the 13:00 mark, when adding the Bézier segment, how in heave's name do you get to see that in the 3D viewer ? Nothing is shown in mine.. Also, your 3D viewer shows material even when in Solid mode ??? I don't get it. I know blender has a steep learning curve, but this is discouraging :(

Thanks for making these. So many videos show how to do a thing, but don't explain why. I've always just kind of messed with nodes to see what I can do with them. Having a background in software development definitely helps

This was crazyyy useful. Not a software or web developer, but trying to use embeddings for academic research. Really great walkthrough!

Something worth mentioning about multiple UV maps is that .obj export does not support multiple UV maps per object. This drove me crazy for hours.

if anyone is looking at this auto smooth is gone from data in 4.1

this is the way to explain mindset the philosophy about it not just click , thank you

Did they change the way shading happens within fiber? It seems I now have to set an intensity to achieve a similar result.

I love that I know just *barely* enough about Blender to work a little ahead of the early stages of this tutorial. It's great.

Very good video. I just implemented a semantic search engine in my app and it works like magic

Thank you Just...Thank you

Love you man, thanks for coding and making this tutorial in JavaScript/TypeScript.