Відео

Never mind i found out hehe

Hi, yes I also noticed this recently. I have added some new node graph images to the community section of my channel with an explanation.

Thanks, glad you like the tutes! Are you trying to get many variations within the one geonodes graph, or do you have several independent objects using the same network that need variations?

@@redjam9 second, I would like to model one wooden plank, put GN in it, and then after duplicating that mesh to get slightly different variations. Ive managed to make something semi acceptable with Self Object, and Obj info

@@SrdjanPavlovic11080 that is just a matter of connecting as many sockets into the main group input as you need. So for instance noise scale, position offset, displacement amount, mesh resolution etc. That way all of these show up in the modifier as sliders. Each time you duplicate the object, just tweak the sliders to get a different result. All the "plank" objects will use the same geonodes network, but the end result is different since the inputs are different. You are essentially creating your own custom modifier that can be reused.

The Vector(0, 0, 0) in the distance node in the shader node can be changed or animated, but this is still in world space. SInce this is an old tute, we didn't have instance coloring back then. To get more control, you would be better off creating a custom color attribute in the geonodes itself and use the distance calculation using the self object node position to each instance. This custom attribute can then be referenced in the material. This way the distance will be in local space.

@@redjam9 Thanks a lot for your reply. That makes total sense.

cheers! I think the only way to get what you are after is to use circle packing which is a much more advanced technique. Have a look on blenderartists for a post by Higgsas who has a project file.

Did you solve this? I need a more randomized pattern :C

@@_ZEIT_ Take the Random Value Node (change it to Boolean and play a bit with the Probabilit value) and put it into Selection in the Merge by Distance Node. Hope this helps

@@cookiemonster_xx thaaaaanks! Gonna give it a try!

​@@_ZEIT_ i got excellent results following the first half of this tutorial ua-cam.com/video/a6oMMzRBIfo/v-deo.html

@@cookiemonster_xx Thank you, I knew something must have changed the behavior. I did as you suggested, and it was better. I went a little further, followed the dual mesh with a triangulate, followed by yet another dual mesh. This produced a result much closer to how it looks in the video.

Get a vector by subtracting the position of the last point to the second last point. Normalize this vector and feed this into the align rotation to vector node.

It really depends on if you have either a coding or math background. Geonodes really are just a visual way of programming, so needs to be approached from that viewpoint. It is generally a lot of vector maths, so understanding that is vital. I would actually recommend learning 2d vector math before 3d. You could try the Daniel Shiffman videos on youtube or his free "Nature of Code" book on his website.

cheers! Keep in mind that a lot has changed in geonodes since I made this video, but it should still work.

thanks, I appreciate your feedback! Good to hear that you found it helpful :)

I have already discussed this in the comments and posted a graph to do this in the community section. It depends on your needs, since in a gamedev situation you want as little geo as possible and won't see the back faces.

If you use a mesh to points node in face mode after the dual mesh you will get a point in the middle of each face that can be instanced onto. You can also use a capture attribute to get the face area to then scale up each instance to the size of each face.

thanks! Yes you can get get the island colors into the vertex colors, but the workflow is a bit clunky. You need to store the named attribute of the color to an attribute called "Color". You won't see it in the viewport though until you apply the geonodes modifier. You can use a material with the color attribute to preview the result as I did in this tute..

@@redjam9 I will give it a try thx for pointing me in the right direction :)

the noise is originally in a 0 - 1 range, so by subtracting 0.5, it puts it into a -0.5 to 0.5 range

@@redjam9 thank you

thanks :)

should be fine. Some of the node names may have changed though...

@@redjam9 Thank you for getting back to me!

the layout is different in 3.4 search for what he's using instead.

cheers!

me sirvio !

cheers! If you look in the spreadsheet you can see that most (all?) noises are in the 0.3-0.8 range or thereabouts. I usually remap them to the 0-1 range as you then get a more even spread of values...

thanks. Yeah I have lots of issues with noise, and what you are hearing is the noise cancellation cutting in and out....