hda inside vrayMaterialBuilder

[fred_hopp]

Has anyone had any luck making hdas that are intended to be used inside a vrayMaterialBuilder?

if I make a subnet, and an hda from it while inside vrayMaterialBuilder, it works and renders fine, but as soon as I create a new node of that new hda type, houdini throws this error



Traceback (most recent call last):
File "vop_test_vray_otl", line 3, in <module>
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.759/houdini/python3.7libs\voptoolutils.py", line 54, in genericTool
exact_node_type=exact_node_type)
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.759/houdini/python3.7libs\toolutils.py", line 1393, in new_func
return function(*args, **kwargs)
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.759/houdini/python3.7libs\toolutils.py", line 1514, in genericTool
exact_node_type)
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.759/houdini/python3.7libs\toolutils.py", line 1373, in createNodeInContainer
exact_type_name = exact_node_type)
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.759/houdini/python3.7libs\houpythonportion\ui.py", line 1081, in decorator
return func(*args, **kwargs)
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.759/houdini/python3.7libs\hou.py", line 13132, in createNode
return _hou.Node_createNode(self, node_type_name, node_name, run_init_scripts, load_contents, exact_type_name, force_valid_node_name)
hou.OperationFailed: The attempted operation failed.
Invalid node type name

[bdancer]

I have some code to allow HDAs inside the material builder, I guess HDA detection doesn't work in your case for some reason.
Is it possible to send me get .hip and .hda file?

[david.anastacio]

Hi fred_hopp,

We run custom HDAs inside material networks all the time, we never ran into issues with those, even the debug works with custom HDAs
Have you tried recreating it again, houdini can some times be a bit stubborn.

Best,
David.

[fred_hopp]

Thanks guys.

Knowing that it is possible, I narrowed it down to the fact that my "TAB Submenu Path" was NOT the default "Digital Assets" (trying to keep thing neat and tidy). Not using the default seems to break it.

I'm glad that it works, but I think it would be cool to be able to make use of the TAB Submenu Path, just to be consistent with hdas in houdini in general.

Cheers and thanks.

[fred_hopp]

Last thing, if anyone is having similar issues or doesn't have their hdas showing up, one needs to get rid of "$HDA_TABLE_AND_NAME" in the Context Options

[david.anastacio]

Thanks guys.

Knowing that it is possible, I narrowed it down to the fact that my "TAB Submenu Path" was NOT the default "Digital Assets" (trying to keep thing neat and tidy). Not using the default seems to break it.

I'm glad that it works, but I think it would be cool to be able to make use of the TAB Submenu Path, just to be consistent with hdas in houdini in general.

Cheers and thanks.

That's odd, never had that issue come up, and we always change the default tab menu path to a custom one.

Best,
David.

[fred_hopp]

I have some code to allow HDAs inside the material builder, I guess HDA detection doesn't work in your case for some reason.
Is it possible to send me get .hip and .hda file?

Here is a hip file with 2 hdas: one in "Digital Assets" that works just fine, and the same in a submenu path, with "$HDA_TABLE_AND_NAME" removed in the context options.
I would be curious as to what the issue is.

And thanks for the info, David!

[bdancer]

By default we detect user hda by "Digital Assets" top level menu name.

There are 2 env. vars to add additional hda:
1. VFH_HDA_MENU_PREFIX - ";" separated list of top level menu names
2. VFH_HDA_PREFIX - ";" separated list of namespaces of op definitiions (e.g. "oplib:/your_namespace::")

Hope it'll work for you.

[fred_hopp]

By default we detect user hda by "Digital Assets" top level menu name.

There are 2 env. vars to add additional hda:
1. VFH_HDA_MENU_PREFIX - ";" separated list of top level menu names
2. VFH_HDA_PREFIX - ";" separated list of namespaces of op definitiions (e.g. "oplib:/your_namespace::")

Hope it'll work for you.

Thank you so much. I will try that out.

Cheers.