Really clear, concise, easy to follow. It worked for me. Best part is you made it short and simple. Looking forward to more 10 minute tutorials! Great work !
I tried this technique like you say, similar to plexus effect if you do it with random points, and you have to use a For Each Element inside another For Each Element. I will do the second part of this tutorial to show it with random points. But if you want to learn how to connect all the points at the same time, here you have the tutorial 👉 th-cam.com/video/8FVMIUxUAbc/w-d-xo.html
Thanks for the great tutorial! Just a small tip: using *0.1 instead of /10 can be faster because multiplication is simpler for the CPU to process than division. It might not matter for a single value, but in larger node setups, the performance gain can add up!
Muy bueno el tutorial. Lo único que sucede es que algunas de las líneas que se generan se duplican. Si hay dos puntos aislados, unidos por cercanía, el método hará una línea por cada punto y se duplicarán. No sé muy bien cómo se podría solucionar.
Si quieres eliminar los Splines extras (líneas) puedes agregar, después de For Each Element, los nodos: Curve to Mesh > Merge By Distance > Mesh to Curve. Esto convertirá las curvas que estén muy cercas en una :) Puedes comprobar en el Spreadsheet la diferencia entre el antes y el después de aplicar este método. Te dejo una imagen para que lo veas: freeimage.host/i/2GnHbFR
Outstanding tutorial. Keeping the video under 15 minutes (as you do) is a great idea. There's already enough here to go practice and acquire something useful. May I suggest you retitle the video by replacing 'in Blender Geometry Nodes' with "With the Blender For Each Node"? Among all the nodes used here the new For Each Node is the most important.
I try to keep my tutorials under 20 minutes, but sometimes achieving complex effects, like the Self-Collision effect, requires more time. I prefer to explain things thoroughly rather than just saying, "Do this, and you'll get that." I want to help viewers understand why we do certain things, which can make some tutorials longer. Regarding the title: You might be right, but I prefer this approach because people often search for phrases like "How to do something + Geometry Nodes." That’s why I usually include "Geometry Nodes" or "Simulation Nodes" in the titles-it makes them easier to find. As for the description, I did include "For Each Element," so I think it still works as a searchable term on TH-cam :)
@@Xan3D The Blender documentation is terse by necessity. The Blender team supports at least 25 spoken languages so each change or introduction of new features likely adds 25 tasks to the release worklist. This terseness leaves a void for Blender video content producers like yourself. Your 'explain', 'help', and 'why' words in your first paragraph anchor your production philosophy. Don't change that philosophy - keep doing what you are doing. Thanks.
Really clear, concise, easy to follow. It worked for me. Best part is you made it short and simple. Looking forward to more 10 minute tutorials! Great work !
This channel is pure gold
Another instance where you are on point and right on time. I needed to figure this out today. I don’t even need to leave the house now
incredible for motion design!
Wow! Ducky It's nice to see you here 😃
Thank you
Very helpful cordial newbie friendly tutorial,
Thanks for sharing ,
I really understood the difference between before and after using the ForEach node! Thank you!
I have understood all geometry nodes only after Xan videos 🙂
Perfeito
This is beautiful! Thank you. I have an idea of what I would use this for too!
Thanks
nice❤
how can I do this but all the points connect a line to each other, which would mean each point would have several lines coming from each line
I tried this technique like you say, similar to plexus effect if you do it with random points, and you have to use a For Each Element inside another For Each Element. I will do the second part of this tutorial to show it with random points. But if you want to learn how to connect all the points at the same time, here you have the tutorial 👉 th-cam.com/video/8FVMIUxUAbc/w-d-xo.html
And if I want to connect single point into multiple closest points? how can I adjust this setup?
It's a bit more complex. I will do a tutorial to show it soon :)
Thanks for the great tutorial!
Just a small tip: using *0.1 instead of /10 can be faster because multiplication is simpler for the CPU to process than division. It might not matter for a single value, but in larger node setups, the performance gain can add up!
Muy bueno el tutorial. Lo único que sucede es que algunas de las líneas que se generan se duplican. Si hay dos puntos aislados, unidos por cercanía, el método hará una línea por cada punto y se duplicarán. No sé muy bien cómo se podría solucionar.
Si quieres eliminar los Splines extras (líneas) puedes agregar, después de For Each Element, los nodos: Curve to Mesh > Merge By Distance > Mesh to Curve. Esto convertirá las curvas que estén muy cercas en una :) Puedes comprobar en el Spreadsheet la diferencia entre el antes y el después de aplicar este método.
Te dejo una imagen para que lo veas: freeimage.host/i/2GnHbFR
Outstanding tutorial.
Keeping the video under 15 minutes (as you do) is a great idea. There's already enough here to go practice and acquire something useful.
May I suggest you retitle the video by replacing 'in Blender Geometry Nodes' with "With the Blender For Each Node"?
Among all the nodes used here the new For Each Node is the most important.
I try to keep my tutorials under 20 minutes, but sometimes achieving complex effects, like the Self-Collision effect, requires more time. I prefer to explain things thoroughly rather than just saying, "Do this, and you'll get that." I want to help viewers understand why we do certain things, which can make some tutorials longer.
Regarding the title: You might be right, but I prefer this approach because people often search for phrases like "How to do something + Geometry Nodes." That’s why I usually include "Geometry Nodes" or "Simulation Nodes" in the titles-it makes them easier to find.
As for the description, I did include "For Each Element," so I think it still works as a searchable term on TH-cam :)
@@Xan3D The Blender documentation is terse by necessity. The Blender team supports at least 25 spoken languages so each change or introduction of new features likely adds 25 tasks to the release worklist. This terseness leaves a void for Blender video content producers like yourself.
Your 'explain', 'help', and 'why' words in your first paragraph anchor your production philosophy. Don't change that philosophy - keep doing what you are doing. Thanks.
⬇ Download all my projects and watch exclusive tutorials on my Patreon www.patreon.com/Xan3D