Rafeek Rahamut

wanglifu
Could you see the video?I think it's clear enough.

I was able to reproduce it by following the video. It appears to be specific to Indie Edition.

mgbaker
Hello Experts,
...
In either case, the primitives come in with a list of named parts and a list of paths to materials for those parts. I would like to associate those materials with the primitives, but I'm not sure how best to do that.
...
Should I instead use the material SOP? But I'm not sure how to point it at the materials on disk by pathname.

Hi Mary, this is a great question.
The basics of what you need to do are:

1. Reference the material on disk. The assetreferenceLOP is the easiest way to do this, but you'll need a separate LOP for each reference made. The "Parent Primitive Type" is typically 'Scope' for materials. The more generic referenceLOP will allow you to do multiple references in a single LOP but is a bit more complex to use.
   
2. Assign the referenced material with the assignmaterialLOP. This LOP will let you do multiple assignments in a single LOP.
   

I hope this helps.

-- Rafeek

It could be because of collections?

The Transforms tab doesn't understand collections the way the Sliders and Attributes tab does. Instead, it expands a collection's contents and shows the light, regardless of the presence of transforms by the lightmixer node. So if in 18.5 you had a collection for all your lights moved in to the Sliders/Attributes tab, you'd see a listing of all the lights in the Transforms tab.

Both 18.5 and 19.0 (should) work this way.