Hello,

In the "usual" instancing workflow you put the points inside the copytopoints node. In this scenario everything works fine and I can also access any attributes on the points to for example affect the shading of the instances in a material.

But in the example above I am connecting the points to the left input and in this case using primvarreader in the material doesn't work anymore. So how do I access point attributes in this case?

I know I can easily use object merge or copy the whole network tree to bring those points inside the copytopoints to make it work, but I am trying to figure out why this approach doesn't work just to understand Solaris and USD better. Also there are some use cases where having the scene setup this way makes a bit more sense.

Kind regards,
Dima

It's a current limitation that we don't support copying primvars from USD points/prims, only from SOPs points. There isn't a fundamental reason this can't be made to work, we just haven't gotten to addressing this yet - but it is an open and known RFE on my plate for the future

Thank you very much for the quick reply. Makes sense now. I am also glad it is on the to-do list. As I already mentioned, this workflow would actually be preferred in some scenarios.

Have a wonderful day.