Hi, I was messing around with the Magic Market Scene from
https://www.sidefx.com/contentlibrary/market-scene/ [www.sidefx.com] in H18.5.462
I just brought the full scene onto the stage with a default Sublayer node.
/stage/Sublayer(File = /path/to/LOPS_DEMO_FILES/Library/Layout/FullScene.usd) -> NULL|TO_SOPs
Everything looks to check out in the Scene Graph View, nice Assembly/Component Kind.
Now when I pulled this scene into Sops with a default LOPImport
/obj/geo/LOPImport(LopPath = /stage/TO_SOPs, Primitives=*)
and 'Unpack USD to Polygons' on the Table, I happened to notice that I had 5 overlapping sets of table by repeatedly blasting over one of the table faces.
So I started messing around with the various traversal options, and while the paths change a bit, I still seem to get additional packed geo for every entry in the path. This seems odd to me as I would expect assembly hierarchy to be empty until the leaf.
Maybe I'm missing something?
I did a usdcat on the usd file to have a look at the usda, and there looks to be single Table reference there.
Perhaps there's something I'm overlooking wrt how this usd scene was created?
At any rate, I thought id share a little code I was using to debug that prunes out some of this additional prim path geo prior to unpacking in a couple of vex vs python hdas -- if only because I love the new Versioned Digital Asset Interface.
Well done; simple, elegant, and should enlighten many in the way of the hda!