Thank you! I will take a look.

Pete

I really like the KineFX (pre-APEX) elephant setup https://www.youtube.com/watch?v=shGXQxx8du8 [www.youtube.com] presented by Esther Trilsch.

I've been attempting to convert this elephant setup over to a human - and I'm close but there are few problems.

I thought I'd ask and see if anyone has already done it with KineFX (no APEX). It'd be good to look at.

I want to make it work with KineFX. I need to stay in Houdini 20.0 (project can not upgrade to H20.5). Please don't suggest to me to use the superior APEX system.

Actually I'd really like to study any (pre-APEX) KineFX human setup.

Pete

I disabled redshift via the houdini.env.
Started H20.5 (not loading a file) and I get.

HDK Warning: GUI_PrimClusterMeshHook and GUI_PrimClusterMeshHook have the same priority (0)
HDK Warning: GUI_PrimClusterMeshHook and GUI_PrimClusterMeshHook have the same priority (1)

I'm getting this warning when loading at H20 scene into H20.5

HDK Warning: GUI_PrimClusterMeshHook and GUI_PrimClusterMeshHook have the same priority (0)
HDK Warning: GUI_PrimClusterMeshHook and GUI_PrimClusterMeshHook have the same priority (1)
HDK Warning: GUI_PrimClusterMeshHook and GUI_PrimClusterMeshHook have the same priority (0)
HDK Warning: GUI_PrimClusterMeshHook and GUI_PrimClusterMeshHook have the same priority (0)
HDK Warning: GUI_PrimClusterMeshHook and GUI_PrimClusterMeshHook have the same priority (1)
HDK Warning: GUI_PrimClusterMeshHook and GUI_PrimClusterMeshHook have the same priority (1)

Can not find any info on this. I am having problems rendering (with Redshift) though. Is it related - no idea.

Any ideas?

Pete

Here's the simple/basic code to get the usd path. This is in a Python SOP inside a SOP Modify node. This is after a Material Library and Assign Material.

node = hou.pwd()
geo = node.geometry()

prims = geo.prims()
for primN in prims:
val = primN.attribValue('usdmaterialpath')
print( 'val', val )

Within a SOP_Modify I'm using a python node to access the usdmaterialpath attribute of imported geo. This gives me the material path as a lop/usd path (/materials/materialName).

I would like to access that material (within this SOP_Modify) to query a few parameters of that material.

How do I resolve that path to that node within a SOP_Modify? How do I access that LOP material node's attributes via python within a SOP_Modify?

Thanks for any help.

I would also really like a 'Skip Rendered Frames' option added to husk. Simple idea but very useful.

Pete

Another excellent approach. Thanks j00ey!

For any of these methods would I need to export a usd frame range sequence to get the animated values or are the expressions preserved in the usd file?

I'm going to test it both ways but I thought I'd ask to help confirm results.

Pete

This is very helpful. Thank you goldleaf!

Pete

This might be a very basic question - but I'm stuck.

In Solaris I have set up lights. I want to cycle the light colors over time.

Is there a way to set up a ramp/cycle for the Color on the Base Properties tab that will affect lights?

I see Light Filters on the Base Properties tab. That seems to work to tint lights for Karma. But it doesn't affect the lights for Redshift.

What's the best way to animate the light color that will work with Karma/Redshift/etc?

Anyone know of a tutorial or documentation to explain how to do this?

Thanks!
Pete

I'm having the same problem. Seems to be related to USD activities (though my testing is still early).

I understand that it's a bug but are there conditions that flipping from an Indie Edition to a Non-Commercial Edition would happen normally?