Chris P


About Me

Not Specified
Not Specified


Recent Forum Posts

HSITE in OSX Nov. 5, 2014, 4:16 p.m.

As you mentioned it works at work on linux are you doing this from OSX in the same environment or at home?

This maybe obvious, but I just picked this up from the docs:

The $HSITE directory must contain a houdinix.y directory (such as houdini9.0). If no such directory exists, Houdini will not search in $HSITE.

Yup, I had totally forgot about that note on documentation. This way will work, now I have to find how to make it independent of Houdini's version same as in work.

Thanks Andy

HSITE in OSX Nov. 5, 2014, 9:20 a.m.

Are you starting Houdini from that terminal session, or via the Finder?
Vars exported by bash are not system wide, you need to open a terminal and run the Houdini setup from there, then enter houdini or houdinifx to launch houdini from within that environment. That should do it. Depending on your OSX version, there are various methods for setting vars system wide.

I hope this helps.

from terminal, the houdini setup will run automatically with a script I have in .bash_profile and all I do is type houdinifx. Also, I am on OS X Yosemite.

The variables are recognized by houdini, from textport when I am running
setenv $HSITE
I will get the right path

But it seems to ignores everything inside there.

HSITE in OSX Nov. 5, 2014, 7:49 a.m.

You can get your all otl directories by:


Thanks for the reply, but I don't want to use HOUDINI_OTLSCAN_PATH, I want the HSITE, is not just the otls that missing, there python scripts, toolbars, dso, presets, icons, etc.

Also, I don't think it has to do with which env variable I am using, something else I am doing wrong using Houdini's env variables in OSX.