Hi,

What's a good way to configure AOVs per render pass? Create a different product, or something else?

Thanks!

AOVs are _always_ controlled in USD via the render settings prim, which points to one or more render product prims, which point to one or more render var (AOV) prims. So if you want one render to have a different set of AOVs produced that another render, you must have a different render settings prim (or apply per-render overrides to the render settings prim). How this fits into your pipeline and render submission/farm system is going to quite dependent on how you initiate your renders.

Ok, got it, thanks! Until now we've been rendering passes by building separate USDs for each, I'll try to get the render pass system going so it's just different husk executions of the same USD.

I'm progressing, got to separate USD and husk executions, with husks picking up rendersettings and passes, render locally and on Deadline.

One thing that does sound strange is that there is no husk option to pick a product - only rendersettings. Wouldn't it be better if husk could pick up both?

Thanks!

Settings point to products. So picking a different Settings prim picks a different (set of) Product(s) implicitly. Providing an explicit product specification would be redundant. I think it's probably just as easy to do in your USD file by making a new render settings prim (referencing an existing settings prim) and overriding the Products relationship yourself.

Jumping in to give my two cents since I've been working on a tutorial covering this exact thing.

My approach has been to put down a karma render settings to create a base "global" scene render settings + product. Then duplicate those per render pass, overriding the orderedproducts, orderedvars and productnames.

That way you can update the settings on all of the passes from one place.

Also make sure to set the render source on the passes so you can refer to it for telling Karma which render settings to use. I have a python recipe on the "render settings" parameter of the render rop to set it automatically from the pass render source. My deadline submitter also picks it up.

mtucker
Settings point to products. So picking a different Settings prim picks a different (set of) Product(s) implicitly. Providing an explicit product specification would be redundant. I think it's probably just as easy to do in your USD file by making a new render settings prim (referencing an existing settings prim) and overriding the Products relationship yourself.

I wouldn't hate the idea of a --products flag for husk for when I'm feeling lazy and can't be bothered creating a separate rendersettings prim. Though I agree it would be a less clear/explicit/proper workflow that might not be good to encourage.

What I would love though is an option for the rendersource relationship to drive the rendersettings prim/s. It's a bit clunky switching between passes in the viewport when you also have to remember to switch rendersettings every time.

So, a render is defined by settings, product and pass. We can now pick pass and settings in husk but no product. It would be simpler to pick product in husk too, instead of having to clone the settings and attach a different product, and sometimes modifying the USD might not be handy. I can work with it as is, but it would be nice

Thanks!