Should rendering custom mesh attributes in Cycles still work in current master? The examples in Blender Archive - developer.blender.org render in black in material preview for me (and same for my own test with a custom attribute).
1 Like
Material Preview is not Cycles but Eevee, where attribute rendering is not supported yet.
Ah, sorry, the rendering is so quick in those clips I didn’t notice the sample indicator (and forgot the patch was for Cycles only). But I had also tried in Cycles Rendered view, which also results in a black surface.
It works here, maybe check again.
Indeed, I seemed to have made some mistake somwhere, thanks
Suppose I wanted to color the point instances generated by the geonode graph based on the custom attribute set on each point. Looking at node_geo_point_instance.cc the only way to do that would be to use the id field set on each instance and use that in the shader to somehow link up with the values set in the geonode graph. Before I look further into this, is this even possible?
There’s no support for that in geometry nodes and Blender currently, instances don’t have attributes. They only have different transforms and a unique ID to generate random numbers.
Cycles has internal support for such attributes per instance, but it’s waiting on Blender to expose them.
Sorry for reviving this old thread, but has this situation improved with the 3.0 release? I.e., is it now possible to specify a color for each individual instance in a GN tree? I can see it’s possible to output custom attributes through the Group Output node, but using them in a shader does not seem to work.
Ah, seem to have found a hint myself in the release notes of the upcoming 3.1 version:
Geometry Nodes instance attributes are not usable in shader nodes yet.