When playing with the light linker I found out a counterintuitive behavior regarding the include Rule.
Let say you have twos shots and a context variable to be able to switch from one to the other one:
-first shot contains a sphere and a grid example "/sphere1" and "/grid1"
-second shot only contain the grid
If I create a light , a light linker with a rule to only lights the sphere so I write '/sphere1' into the include rule .
Only the light is lit by my light.
If I switch my context to the second shot (you can byPass the sphere node creation if you want to mimic/test on your own), the light now lights everything, in that case the grid.
If I check the "collection:lightLink:includes" from the light in the geometry spreadSheet , it's empty in the second shot.
For me it would be more logical that the light will not light if the path from the rule is incorrect, no?
Or maybe I'm missing something, does someone has a solution? Because in a movie/sequence context example you could have many shots and the hierarchy can change often regarding the shot , if I want to share some lights for every shots before doing any override per shot.
It's the same issue using collections but a workaround will be to include a permanent prim into th collection (let's say a scope or an xform) , in that way collection:lightLink:includes will be never empty.
I will dig a bit in the python , maybe simplier to do a workaround.
Image Not Found
Thank you in adavance.