I'm having a problem with setting up houdini 8 to work with our environment variables.

It seems houdini 8 breaks when it encounters the HOUDINI_PATH variable.

If the variable is even created and empty it crashes out houdini 8.

With Houdini 7 it works fine.

I'm just installing 8 now to test it out in our environment. Any ideas?

thanks,

-mikey

If you create an empty HOUDINI_PATH variable, then things will go horribly wrong because all the required setup files are read off of HOUDINI_PATH. When you set it to empty, it won't be able to find any of the required start up files. I just tried that here in H7 and things do go horribly as well.

So, my suggestion is to don't do that. If you're setting up your own custom HOUDINI_PATH environment variable, you must make sure that $HFS/bin and $HFS/houdini are included in it.

edward
$HFS/bin and $HFS/houdini are included in it.

$HSF/bin is missing in my HOUDINI_PATH

I've never had a problem in Houdini 6-7 with my path.

I'll add $HSF/bin and see how it goes, thanks.

I'll also see if it was being set anywhere else.

Thanks again,

-mikey

adding HFS/bin solved my problem.
wonder why my path was fine in houdini6 and 7?

-mikey

I guess it looks for more stuff now.

It turns out it wasn't adding HFS/bin that fixed it

It looks like Houdini8.0's paths no longer accept spaces
Houdini7.0 and before did.

so when I added semicolons it fixed it

getting houdini8.0 up and having help did it for me because I could search on path and see that hconfig -ap was the command I needed to figure things out.

Very cool, thanks all.

-mikey

How does adding semicolons help with the space in HOUDINI_PATH issue?

edward
How does adding semicolons help with the space in HOUDINI_PATH issue?

using hconfig -ap I noticed that the example paths were seperated by ;'s
My tcsh seperates paths with spaces
Houdini7 worked with the spaces seperating path entries
Houdini8 doesn't like the spaces

Replacing the spaces with ;'s fixed it.


new path:
setenv HOUDINI_PATH “.;${HIP};${HOME}/houdini${HOUDINI_MAJOR_RELEASE}.${HOUDINI_MINOR_RELEASE};${HSITE}/houdini${HOUDINI_MAJOR_RELEASE}.${HOUDINI_MINOR_RELEASE};${HFS}/houdini;${HFS}/bin”

old path had spaces

or more easily readable new:

setenv HOUDINI_PATH “.;$HIP;$HOME/houdini8.0;$HSITE/houdini8.0;$HFS/houdini;$HFS/bin”

old

setenv HOUDINI_PATH “. $HIP $HOME/houdini8.0 $HSITE/houdini8.0 $HFS/houdini $HFS/bin”

Does that make sense?
-mikey

Ah, that makes sense now. I don't think it was ever intended to allow spaces as the separator between paths. In H8, it was fixed so that one could have spaces in their paths (eg. CProgram Files). So this broke your incorrect (but previously tolerated) HOUDINI_PATH.

edward
Ah, that makes sense now. I don't think it was ever intended to allow spaces as the separator between paths. In H8, it was fixed so that one could have spaces in their paths (eg. CProgram Files). So this broke your incorrect (but previously tolerated) HOUDINI_PATH.

My tsch requires spaces for it's path so I used that convention.
-mikey

If you use “set path” in tcsh, then you can use spaces. But if you echo $PATH, isn't it concantenated using semi-colons?

edward
If you use “set path” in tcsh, then you can use spaces. But if you echo $PATH, isn't it concantenated using semi-colons?

hmmm, mine doesn't concatentate. Also our current tcsh used either spaces or simi colons.

-mikey