I wanted to create a simple dummy objects to mimic instances used later, but these dummies tend to deplicate entire underlying mesh as well. While collection of proper instances doesn’t.
I understand that I can simply just make a collection with dummies inside it, but I’d like to understand why this doesn’t work, when it should the way I understand it.
Edit.: adding separated screenshots for better view
A hint about showing two 7680 pixels wide images when someone has to compare them on a “standard screen” with max width of 1920 pixels and also in the browser :
The nodes are almost undecipherable and the right image doesn’t really show that much info:
And if you force people to download it then they are still too big… (already the left half show at 50% fill my monitor)
So the changes to get prompt answers is increased when “preparing” the images to a better viewable/readable format…
…or…
This said: I’m ready to receive any big monitor donations …but then i also might need some more powerfull computer
)
…
Back on topic:
What i wonder is (maybe not “connected” to the problem… but): why does the content of your Collection 3 does change from: prop_rio.., prop_..cedar, test_tree to MD_MS.003..005 ?? And also the GN number of users changes from 2 to 5… ?
[ Because i’m a very analytic thinker i instantly see those differences in a “comparision” and wonder: why is this ?]
My bad. Have this monitor for short while and got very comfortable with it. I didn’t think of this. Thanks for the feedback! I separated screenshots to 4k images only in the first post. That should be enough.
why does the content of your Collection 3 does change from: prop_rio.., prop_..cedar, test_tree to MD_MS.003..005 ??
MD_MS is name of the original object instances are generated on. I have no clue how this works in general, hence the post here. I expected entirely different behavior.
And also the GN number of users changes from 2 to 5… ?
This might be due to other hidden objects that also use this modifier, if we’re talking about the same thing.
[ Because i’m a very analytic thinker i instantly see those differences in a “comparision” and wonder: why is this ?]
So am I, that’s why I keep wasting my time on this topic instead of just going with what works, lol
Ohh i know this why-doesn’t-this-work-but-it-should – situations…
And when coming back to this some hours (or days) later after i almost wreckaged my room interior not really … it’s simply because of… some nasty thing… i forgot to do in th efirst place…
Not sure I understand what you are trying to achieve.
The instance on points node will instance the collection on the points, there is no need to convert the collection to an instance as the instance on points node already does that.
It looks like you want to separate the children and then pick one component of the collection for each point but as you are turning the whole collection into an instance with the “geometry to instance node” you can no longer separate the children because you turn the whole collection into an instance (there are no longer any children to seperate.)
Also not sure what you mean by the title of the thread, what has converting a collection into an instance got to do with making instances real?
To stay honest, I haven’t slept much, so that might be a part of the problem when explaining.
I normally don’t have problems with instances. Just today, I wanted to do some quick tests with geometry primitives (dummy) converted to instances instead of creating new collections, new objects outside of my geonode tree.
But creating mesh primitive, converting that into instance inside the geonode tree AND making that primitive real didn’t behave as planned.
Ok now I understand why you treid using the “geometry to instance” node as the collection has an instance output but the dummy a mesh output.
I take it you then try object menu-make instances real and you get loads of duplicates.
I am not quite sure why that happens. The same thing happens if you use an object info node for the instances and do not check the “as instance” checkbox.
The only explanation I can think of is that dummy’s mesh data is considered “part” of the original geometry’s mesh data, so when you make instances real it sums the original mesh data with the instances mesh data. Not sure if that makes sense.