Attribute node can support Vertex Group (weight)
Currently, you can use Attribute node add vertex color, but it's still not work for the vertex group, I think this is very useful for the weight animation, the vertex weight can made animation now, and we can use the vertex group in the modifier, if the cycles can support vertex group will more nice. although the dynamic paint can do something like through bake the texture, but Attribute node is one better way. ,
8 Comments
this would make a lot of hacky projects a lot less hacky and stable (think of needing to go through the efford of making one dynamic paint bake for vertex colors and one for weight paint for a displace mask). Also compressionmaps may get some attention after this is in blender since the best way to do them would be to make a modifier that outputs the compression as weight, and then that could be even more useful.
Any news on this request? It would allow for a wide range of things in combination with animation nodes.
If you have a set of vertex colors with one name and a vertex group that has the same name, how does Blender know which one you mean to use?
Hi, if have the same name, I think maybe blender can report one warning to warm the user multiple properties used this name, please change the name, than try again. . . or the Fac output use weight at first, and Color output use the vertex color at first :D
Rather than a pop-up/warning, wouldn't it just make more sense to split the functionality into separate nodes (vertex group and vertex color)? Or perhaps it should be a single node that has a drop-down where you can choose whether the node is referencing vgroup or vcolor data. In any case, I think a warning like you describe is really not in line with Blender's UI paradigms.
I know your means, but the attribute node different with other nodes, you know, in this node we can use the property from the smoke, and position, normal and many more,even the name from the UV map. Currently, if your vertex color name as same as the UV map, this node will output the uv, whatever you connect with color or the vector, and no warning tell you. this problem(same name) already exists, so I suggestion to add some tip, or blender can automatic analysis what you need at first, something like, if you link the Factor output will use the weight at first, and Color output will use Vertex color at first, and Vector output will use UV map at first, if have the same name, blender will automatic analysis from your output connect. the output only one to connected, there is a priority at here, separate to many node is not the good way to solve it, and drop-down menu maybe can useful ,but what the smoke, UV map, position or others, it will more complex to achieve, So automatic analysis your linked form the output to confirm witch one is should output is the good way to solve this problem, and not need to change the UI .
Bad english, bad explanation, sorry for this : (
I disagree. All of this indicates to me that the Attribute node is overloaded with non-obvious functionality. I'm not a fan of automatic analysis because it can incur some performance overhead (even if just a little) and invariably, it will guess incorrectly.
The better solution, IMHO, would be either to break up the Attribute node (because right now it's just a dumping ground) or overhaul it to make its features/uses more apparent.
* @Jason van Gumster * I agree with you, there should be a way to select the type of vertex map included in the attribute editor. I also think the tagging method should be based on the object ID, not the name of the item. Particularly since names are often revised in production.