briankulig

Hey all,
I have an hda that has geo and a principled shader assigned in a hda which is being loaded into unreal. According to the documentation a material property of "metallic" should transfer over when HE makes the materials on the unreal side of things. All other parameters seem to come over, but metallic does not. I started with a principled shader and then tried a material builder to make my own with a metallic property exposed. The later triggered a metallic parameter to be made in the unreal shader, but it was set to 1.0, no matter what I set the default of the parameter to be or on the outside of the shader. Is there something special I need to do to get it to listen to the metallic parameter? Or is it broken?

Hey all,

I was wondering if it's possible to control other environment variables (not houdini specific) in the unity_houdini.env. If your hda relies on a python library and you want to distribute it, it would be nice to be able to add they python paths to the unity_houdini.env. I tried PYTHONPATH which I use from my normal houdini.env, but houdini engine in unity didn't seem to read it. It got the hda search paths just fine.

The docs say “The environment file unity_houdini.env is in fact same as the traditional houdini.env file” but it doesn't seem to catch my PYTHONPATH adjustment. The same thing works fine in unity if I add it to the traditional houdini.env.

My unity_houdini.env looks like this:
PYTHONPATH = “W:/Work/PipeTest;&”
HEU_ENVPATH_ADD_HOUDINI_PATH = “W:/Work/Houdini;W:/Work/PipeTest;”

I tried adding the “HEU_ENVPATH_” on the beginning but that didn't change anything. Is there some syntax I have to use or is it just not possible? Any thoughts?

-bk

Congratulations!! Houdini is great about finding ways to achieve things and then building on each achievement for the next cool thing! I understand how you feel. A lot of my “microscopic achievement”s end up getting turned into tools that then get added to others.