Mark Tucker

I would suggest an explore variants node (to create an instance of the asset for each variant selection combination) and an animated prune LOP to change the visibility of the variants so that only one is visible at a time. This follows the rules of USD (visibility can be animated, variant selection cannot be) which means you could even write this to a single USD file and render it all as a sequence.

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.

We are not planning on tackling this in the upcoming release cycle.

I would strongly recommend figuring out a way to have your camera prims created at the top of your graph.

Why are your camera nodes time dependent? Can you use a Cache LOP to eliminate the time dependency?