Kym watts

ok.

so what you have here is a multi root level prims.
a reference is designed to bring in one root and bring it into a path.
a sublayer will allow you to bring in multiple root prims, but you cant change the prim path.

i would suggest for your set , that you make sure all your assets live behind /set, so grid3 lop's primpath should have `/set/grid3` etc.
so ideally in your scenegraph tree, you want to see that you only have one root level prim called `/set`.
once you save this usd out , you can reference in the set usd and nest its prim/primpath under `/shot/set`.


hope that helps.

edit: i added a test scene to show the setup im trying to explain.

A Houdini engine license is required on your license server. It's not always consumed, but seems to be a requirement that it exists.

Some thoughts to add to this thread, in case it helps .

If you don't mind bringing the alembic in via a sop context like a sop create, you can specify on the alembic sop to keep transform/shape hierarchy.

AD products are notorious for saving attributes out side of the abc spec locations.
We found that using the python module _alembic_hom_extensions that comes with houdini we could get these attributes and put them in the correct locations.

If you have some ownership or control of what is getting exported, ie a pipeline of sorts. On the exporter,, they usually have a way to promote attributes from your mesh to the top alembic primitive. I would highly recommend writing any of these attributes to json and reading them back in on the hou side.


Hope this helps.