Oliver Hilbert

OK so it seems this is governed in some way by Preferences > Lighting > Collection Primitive Path

If I change this location, I can put my collection in that new location and %env works.

So it seems like % = /<PrefCollectionPrimPath>.collection:

Is this how it works?

So what Im meaning is (in your example) when you write out sphere.usd and reference that back in (as you would be bring that into a shot) - its will always behave like a payload, regardless of the reference Type parm setting.

It makes sense in a way, because the file you are referencing inside of sphere.usd (payload_geom_file) was set to payload when it was written. But it also means we have a parameter on our sphere.usd reference, that we can choose reference or payload, yet always behaves like a payload.

I feel like reference should envoke referencing of all dependencies too perhaps?

Hello!

Probably just a simple one. Im using collections to organise geo for renderpasses, and seem to be hitting some issues when I try and get organised with the scene.

If I create a collection node, It places the prim at /collections. Then in a any node like a render geometry settings, I can just call my collection:

%env %cars %veg %etc

If I move where my collections in the scene (like putting it in the /Render folder). This no longer works and to use them I have to target the collections like this now:

/Render/passCollections.collection:env /Render/passCollections.collection:car /Render/passCollections.collection:veg... etc

Readablity is gone. Is there a way to keep the clean pathing and use of %, before I moved the collection prim?

I did get results with wildcards but it feels like a bad way to go eg:

*:env


Many thanks in advance!