Hello, you can often don't care much about that type of error on the merge node.
Anyway, why this happen? Because you merge two nodes that haves different attributes. In your case, the right input node comes with a “N” attribute, while the left input node comes without it. So what does the Merge Node do when it comes to merge everything into a single geometry? It needs to create the missing attribute for the left input node, and initialize it to 0. You can't have NO attribute for a group of points, and have an attribute for the rest of the points of the same geo.
Furthermore, how did you ended up with the “N” attribute attached to the right input node? Because in the copy to points node you have checked the “copy point attributes” toggle. This toggle is responsible of copying all the specified attributes from the source points onto the instanced geo. If you uncheck it, you fix the warning message on the merge node
Andr Hello, you can often don't care much about that type of error on the merge node.
Anyway, why this happen? Because you merge two nodes that haves different attributes. In your case, the right input node comes with a “N” attribute, while the left input node comes without it. So what does the Merge Node do when it comes to merge everything into a single geometry? It needs to create the missing attribute for the left input node, and initialize it to 0. You can't have NO attribute for a group of points, and have an attribute for the rest of the points of the same geo.
Furthermore, how did you ended up with the “N” attribute attached to the right input node? Because in the copy to points node you have checked the “copy point attributes” toggle. This toggle is responsible of copying all the specified attributes from the source points onto the instanced geo. If you uncheck it, you fix the warning message on the merge node
Hi Andr!
Thanks alot for the reply and sorry for the slow reply back. That worked great and you explained it so simply as well
Andr Hello, you can often don't care much about that type of error on the merge node.
Anyway, why this happen? Because you merge two nodes that haves different attributes. In your case, the right input node comes with a “N” attribute, while the left input node comes without it. So what does the Merge Node do when it comes to merge everything into a single geometry? It needs to create the missing attribute for the left input node, and initialize it to 0. You can't have NO attribute for a group of points, and have an attribute for the rest of the points of the same geo.
Furthermore, how did you ended up with the “N” attribute attached to the right input node? Because in the copy to points node you have checked the “copy point attributes” toggle. This toggle is responsible of copying all the specified attributes from the source points onto the instanced geo. If you uncheck it, you fix the warning message on the merge node
Hi Again Andr,
I have moved on a fair bit through the tutorial and have got a similar issue again except this time it's not related to the “Copy Point Attributes” Toggle. If you have the time i'd love it if you could explain in simple terms whats gone wrong in such a way that it explains whats going on and then I can see if I can fix it without you telling me exactly what to do if that makes sense (I'm new to houdini so want to try as hard as I can to solve bugs etc to learn )
I think I have found the issue I went to the Copytopoints node and ticked “Pack and Instance” and it seems to of set things right. Is this the correct thing to do? Why did it do that?
I think I have found the issue I went to the Copytopoints node and ticked “Pack and Instance” and it seems to of set things right. Is this the correct thing to do? Why did it do that?
I think I have found the issue I went to the Copytopoints node and ticked “Pack and Instance” and it seems to of set things right. Is this the correct thing to do? Why did it do that?
Oh sorry i thought i put the error message haha the message im getting is:
A mis-match of attributes on the inputs was detected. Some attribute values may not be initialized to expected values, e.g.: uv, roofProp, Cd, randCol, rot, …
A miss match of attributes on a merge node means that some nodes come with different attributes. So you need to do something about it before the merge. It's suggested but not always mandatory that two branches of the network should come with the same attributes.
Regarding merge4 node the problem is very easy to fix, you should be able to see how you create that miss-matched “shop_material” attribute. Use middle mouse on the nodes or the geometry spreadsheet to see at which point of the newtwork that attribute is being generated.
Regarding merge3 node, I can't really tell because I don't have the geo files you load from disk. But again, I can see you want to merge together different nodes with different attributes. Also, what's the difference between the uv attribute on foreach_end1 and the uv attribute on foreach_end2?
