Streaming primitive from LOP to SOP creates a path attribute that figures out where the data came from. In contrast, LOP allows using this attribute to place the primitives, which is pretty helpful.

However, the path attribute only reaches the level of the primitives at the moment. But in USD, it also stores the information of the variant selections.

For instance, importing a SOP with the path of “/root/sub{variant=base}” would be better to create a Mesh to “/root/sub” with an auto-generated “variant” set and its “base” selection.

It would be extremely helpful for us because editing a specific variant by SOP is quite common in our pipeline. Or maybe Solaris has an alternative solution which I haven't found out yet?