Bryan Ray

I've just replied to your first message: https://www.sidefx.com/forum/topic/103266/?page=1#post-454809 [www.sidefx.com]

First, ensure that your Component Geometry is set to author time samples. In the Attributes section, set Author Time Samples to "If SOP is Time Dependent". That ensures that the animation is converted from a Houdini node time dependency (indicated by the green clock icon in the network view) to USD time samples. You can verify that you have USD time samples by examining your prims in the Scene Graph Details pane. Light green text indicates time samples.



However, just authoring time samples doesn't break the time dependency -- you should still see green clocks on the nodes downstream of Component Geometry. If you examine the USD layer produced by Component Geometry, you'll see only one sample has been authored on each frame.




Append a Cache LOP after the Component Geometry and set it to Always Cache All Frames. That will author every time sample of your timeline, regardless of which frame you're looking at. Obviously this may take some time to calculate the SOPs geometry for the entire timeline. When you examine the layer created by Cache, you'll see multiple time samples present instead of just the current frame's, and the green clock icon will no longer be present on nodes below the Cache (unless you've animated something downstream of it, of course.)

Saving from the Component Output should now result in an asset containing your animation.

It looks like you haven't started the command prompt with the Houdini environment. You can do so using the Launcher by clicking the little down arrow next to the Launch button and choosing "Command Line Tools," or you can run hcmd.exe from that bin folder directly, which will do the same thing.

Once the command prompt appears, you can test for the environment by running the command echo %HFS%

That will display the HFS environment variable, which should be the simplified Windows path to your Houdini program folder (something like C:/PROGRA~1/SIDEEF~1/HOUDIN~1.550).

With the environment set up correctly, you won't need to enter the entire path to the utilities. The bin folder will be on the system path, so it's easiest to browse to the location of the image you want to extract stats from and run the command from there.

edit: Or, I suppose you could just look at the first few lines of the command prompt and see that it's been configured: