Tom Vujnović

Thanks for coming back to me with this.

I will a bit later. I just want to check one more thing suggested by a colleague of mine.

Undelyng ocean surface is animated, and he suggested that instead of exporting one spectra for the whole animation, I should export a sequence of spectras.
I'm not sure if that is the case, but I'm testing it now.
If that does not work, I will share my scene gladly.

Maybe it's not same cause, But I'm also having issues with Ocean procedural.

I have camera that is animated and ocean. During test renders (with static camera) everything was peachy. I fine-tuned my ocean and rendered several previews, nice.

Now I animated the camera, and suddenly I realized that the renderer is using the camera position from frame 1 for dicing for all frames.

I tried with a camera from USD, recreated the camera in solaris, nothing works. I always get dicing only in areas visible in frame 1.

Tom Vujnovic

… at least for me.
I know that some parts of houdini python implementation require UI (like timeslider) but is there a way to execute .clickButton() method without UI?
I'm writing pipeline script that transfers assets from maya to houdini. I'm exporting everything from maya in alembic files and importing them into houdini.
Since I need full hierarchy in houdini I have to use alembicArchive, not alembic node.

Is there a way to force parm().clickButton() to work without UI or is there a workaround for this?

thanks.

edit:
of course that i meant pressButton() method instead clickButton … lapsus.
Also I found that I can call calback script on this button (item.hdamodule().BuildHierarchyRoot(item)) or do i via hscript's “opparm -c” but that also does not work without UI … so I'm still on square one.
I know that there is a possibility to build alembic hierarchy myself, but I would like to avoid that if possible.

SOLVED!
Problem was in path to .abc file (node.parm(“fileName”))
I was expecting that houdini will throw an error on invalid path. Instead, it just kept working …