I have a scene in which I'm generating a dozen or so procedural trees. At the moment, I lump all these trees together in one SOPnetwork; each tree has a path like:
When I do a SopImport to bring all these in, I see the USD heirarchy I expect, tree_01, tree_02, etc.
I'd like to write all of these out to disk, to use them elsewhere. At the moment, I put them all in one USD file, trees.usd. When I import this file elsewhere, my heirarchy is preserved and everything works fine.
However, I 1) would like to animate my trees, and 2) suspect that lumping everything into one file isn't very USD-like. I'm aware of the concept of layers, and see some options in the USD export node in LOPS that suggests that if I have a layer save path specified, I can generate one top-level file that contains N references to layer files. So, it seems like I should consider having:
trees.usd tree_01.usd tree_02.usd etc.
I can't tell if there's an attribute I can set on my tree geometry to help split them all into separate layers though; the sopimport has one layer save path attr...can this be varied somehow based on a geometry attribute? Or, is there another way I could accomplish this splitting?