Does anyone has set up Houdini HSITE through Ayon? The env variable is picked up by Houdini however the tools and scripts aren’t. Is there an order to add the environmental?
Before Ayon we just set the HSITE variable to a folder on the server. That way our custom HDA’s and scripts like 123.py and 456.py were picked up.
Just cross-referencing: Originally came up on Ynput discord here
In AYON we use the HOUDINI_PATH enviroment variable to configure the houdini setup here.
Other than that, we basically do nothing custom. However, HSITE and HOUDINI_PATH are somewhat related so likely the issue is somewhere there, see e.g. the Houdini docs: Environment variables
Aside of that we use pythonrc.py files for startup scripts because they work in both Houdini Core, Houdini FX (and even the other license types). Otherwise you’d need 123.py, 456.py for Houdini FX, and houdinicore.py for Houdini core (I believe?). And I’m not sure whether multiple 123.py files ever worked - according to thispythonrc.py would also be the way to go.
The question is: what fails with your custom HDAs and everything?
It may also be worth sharing some more details about where you are configuring HSITE currently in AYON and with what values. It may be that it helps to identify where that may affect things too (and potentially can give us an easier reproducable example)
It could be that HOUDINI_PATH overrides how HSITE behaves.
Thanks for the reply. I think I have to dive into it further. So from Ayon 123.py and 456.py aren’t set? Because you can only use one. It will pick up the first it will find. If it does set it we probably have to set it up in a different way. We don’t set the environmental on a per user basis.
It also might be my knowledge of Ayon so far. I’ll dive into it a bit further and will let you know if I have more succes…