@Benjamin Bass Currently it's not possible to set this up automatically unfortunately. This is a known issue and the solution needs to be properly designed still, as we want to have a better solution than how it is solved with shader nodes currently.

@Simon Thommes I was wondering about this too. As a workaround, could you do something like plug Object Info -> Location into your 'seed' of the random value node? Then if you were to duplicate the objects in various locations, they'd sort of have random starting values? I played with it a bit, and for a second I thought it worked, but my results were inconsistent.

@Tyler Bjarke The object info node still needs an object to explicitly be passed into it, so that would need to be set each time the node is used, which defeats the purpose. In Blender 3.4 (allpha) there is a Self Object node, which solves that issue. However proper randomization still needs to be done. The same approach that is used in shader nodes is purposefully not added to geometry nodes as it is quite flawed. The current plan is to enable reading out  custom object properties in geometry nodes an then adding a feature that randomizes a property when duplicating the object. That would allow controlling that seed value explicitly and is more stable.

@Mahesh Deshpande Yes, totally. You can use the Collection Info node to receive a collection as a geometry instance.

@Alexandros Hadjilaou Currently that is not possible natively. In the future there will be a node for that. But right now you can make a nodegroup that scatters points on a surface the scale of the bounding box. Move the points around so that they cover the volume of the bounding box and then delete all points outside of the mesh.

@Sorcière and grease pencil !!!

@schmutzer1 I'm not exactly sure what that means. For me the downloads seem to be working perfectly fine. The direct links work fine even without being logged in. You're saying ' tagged as moved or disappeared immediately after download', if it is after the download, that sounds to me like it would be something on your end.

@Simon Thommes Hello Simon, thank you for your support. You're completely right. It was a browser specific issue with Firefox. Fortunately it worked fine with Microsoft Edge. Congratulations again for your this great course and I wish you all a nice summer at Blender Studio.

@Katie Korwal correction 16:42

@Katie Korwal Float is a technical term for a number with a floating point. It's the same as what is just called Value in shader nodes. The reason I'm changing this here is that by default the input was a vector, but I only want to control it with a single value. Blender always implicitly converts between different input types when possible. So the float input that I give in is then converted to a vector by using it for every component of the vector.

@Michael Gembicki For me, opening the file with Blender 3.3 everything is working just fine. The seed being an input field sounds like the input was toggled to an attribute with the button next to the field. But I just downloaded the exact file in the description and opened it with Blender 3.3 and it's all fine. Can you check that again to make sure?

@Simon Thommes Yeah, redownloaded example and same issues.  This is my blend file saved from 3.3 https://drive.google.com/file/d/158sFbzycay3jrPzwDRaUAYPYIJ8MOP0T/view?usp=sharing

@Simon Thommes I tried it on a vanilla version of 3.3 and it worked just fine.  It must be one of my, way too many, addons causing it. Thanks for the response. I'm enjoying the course.

@Michael Gembicki Ah okay, yes that makes sense then. It seems strange to me how an addon would mess with this file so specifically, but that can happen. At least it doesn't seem to mess with the file itself. The one you shared also works just fine for me on vanilla Blender