mtucker
You python code isn't correctly creating the CollectionAPI. To add a new collection to a prim, you need to call UsdCollecitonAPI::Apply (https://openusd.org/dev/api/class_usd_collection_a_p_i.html#a4c9c1226d01a049864cc0d437900c458). This adds the metadata to the prim indicating that the collection exists. The code you've written just creates some attributes that are associated with a collection with a particular name, but doesn't actually register the collection instance on the prim.

Mark Wallman
Hi. I am trying to automate the conversion of a LOPs USD camera to Alembic and export it out.

I know you can use a LOP camera import in obj and then go to file>export alembic. But is there a way I can automate this instead?

Many thanks!

Best. Mark

EDIT: well that was pretty easy.
-add a render ROP and just change the file extension to *.abc

williambrown
Yes, switching back to the OpenGL renderer is a good fallback for some new viewport issues
I would also try testing out a newer release, if that's possible
The newest production build is 20.5.370 and should include a fix for this issue, it looks like it was fixed in 20.5.238 specifically

adlabac
that means our HOUDINI_OTLSCAN_PATH environment literally ends with @/otls;&

eg.
@set "HOUDINI_OTLSCAN_PATH=tool_directory1;tool_directory2;@/otls;&"

A

adlabac

mabelzile
You could try to debug first locally to see if it's related to the shared folder (i.e. move the shared folder to a folder local to your machine).

I've tried both and it is working.
1. On my local machine set HOUDINI_PACKAGE_DIR to network share(same as farm using)
2. copied shared folder to local disk and then set HOUDINI_PACKAGE_DIR there

What do you mean by this ?

we have packages directory on the network share which is defined by HOUDINI_PACKAGE_DIR before render starts

It just means that this HOUDINI_PACKAGE_DIR environment variable was set properly before render command was started.


UPDATE:
after carefully comparing all the environments, I found the reason of the missing packages. I always thought that @/otls;& endings in HOUDINI_OTLSCAN_PATH were only needed within houdini.env and not supposed it is working in .bat files.

Now errors disappeared.

tamte
the link will be set up automatically if you promote the parms by draging the "Number Of Filters" parm into Type Properties window Parameters/Existing Parameters section

or from Parameters/Create Parameters/From Nodes section into the Parameters/Existing Parameters section

willlinks
Thanks for the reply, jsmack!
In that case, I guess I just need to extract the textures from the usd material and assign in SOP.