Dialog scripts for OP macros, Renderers etc (i.e. the dialog scripts found in $HH/config/Scripts) are no longer cumulative. That is, only the first script found in the path is loaded. Include statements must be added to maintain the previous behaviour.

The VEX compiler vcc now allows variable declarations to occur anywhere within the function body. Not just at the beginning of scope. Thus: surface foo() { Cf = 1; float bar = max(Cf); Of = bar; } will now compile even though the "bar" variable is declared in the middle of the function.

The VEX compiler vcc now allows variable declarations to occur anywhere within the function body. Not just at the beginning of scope. Thus: surface foo() { Cf = 1; float bar = max(Cf); Of = bar; } will now compile even though the "bar" variable is declared in the middle of the function.

The VEX compiler vcc now allows variable declarations to occur anywhere within the function body. Not just at the beginning of scope. Thus: surface foo() { Cf = 1; float bar = max(Cf); Of = bar; } will now compile even though the "bar" variable is declared in the middle of the function.

The VEX compiler vcc now allows variable declarations to occur anywhere within the function body. Not just at the beginning of scope. Thus: surface foo() { Cf = 1; float bar = max(Cf); Of = bar; } will now compile even though the "bar" variable is declared in the middle of the function.

The VEX compiler vcc now allows variable declarations to occur anywhere within the function body. Not just at the beginning of scope. Thus: surface foo() { Cf = 1; float bar = max(Cf); Of = bar; } will now compile even though the "bar" variable is declared in the middle of the function.

PLEASE NOTE THE FOLLOWING CHANGE!

We are attempting to clear up how Houdini treats paths and provide a consistent and intuitive mechanism. Unfortunately, this likely means one will have to change how environment variables are set up.

The following paths are NO LONGER searched by default by the HOUDINI_PATH, nor by the @ short form:

• $HIP/houdini
• $HIP/$USER
• $JOB (which was only searched if $HIP didn't exist)
• /usr/local/houdini

The new search order is:

• $HIP
• $HOME/houdini4.9
• $HSITE/houdini4.9
• $HFS/houdini
• $HFS/bin (NT only)

The following environment variables are no longer installed nor supported:

• $HIH (use $HOME/houdini4.9)
• $HIL (use $HSITE/houdini4.9)
• $HIS (use $HFS/houdini)
• $HIPDIR (use $HIP)

Other changes:

• $HIP now acts like $HIPDIR used to act. It also acts as ifHOUDINI_HIP_FROM_PATH was always set. This means $HIP alwaysprovides a .hip relative path so changing mount points, movingjobs, etc, will not break .hip files.
• $JOB, which was kept from Prisms for backwards compatibility, isretained. It will give you the old $HIP style behaviour. The"job" command now only changes $JOB and not $HIP.
• hconfig now sets $HIP internally to the directory hconfig wasrun from. As a result, you can see when $HIP is being searchedby a .hip file.
• The "=" variable expands to $HIP in pathnames. Thus, if onewants to check $HIP/houdini in HOUDINI_PATH again, the command:

setenv HOUDINI_PATH "=/houdini;&"

can be used.

• A new variable, $HSITE, has been added. This is to allow you tohave somewhere to put site-wide changes without altering the$HFS install.
• The non-HFS relative "houdini" directories are now all appendedwith the DSO Version number (currently 4.9). The good news ofthis is that different major/minor versions of houdini won'tconflict with each others preferences. This applies to $HOMEand $HSITE.

Hopefully the inconvenience caused by this will be outweighed by having a simple, straightforward, and consistent directory paradigm.

PLEASE NOTE THE FOLLOWING CHANGE!

We are attempting to clear up how Houdini treats paths and provide a consistent and intuitive mechanism. Unfortunately, this likely means one will have to change how environment variables are set up.

The following paths are NO LONGER searched by default by the HOUDINI_PATH, nor by the @ short form:

• $HIP/houdini
• $HIP/$USER
• $JOB (which was only searched if $HIP didn't exist)
• /usr/local/houdini

The new search order is:

• $HIP
• $HOME/houdini4.9
• $HSITE/houdini4.9
• $HFS/houdini
• $HFS/bin (NT only)

The following environment variables are no longer installed nor supported:

• $HIH (use $HOME/houdini4.9)
• $HIL (use $HSITE/houdini4.9)
• $HIS (use $HFS/houdini)
• $HIPDIR (use $HIP)

Other changes:

• $HIP now acts like $HIPDIR used to act. It also acts as ifHOUDINI_HIP_FROM_PATH was always set. This means $HIP alwaysprovides a .hip relative path so changing mount points, movingjobs, etc, will not break .hip files.
• $JOB, which was kept from Prisms for backwards compatibility, isretained. It will give you the old $HIP style behaviour. The"job" command now only changes $JOB and not $HIP.
• hconfig now sets $HIP internally to the directory hconfig wasrun from. As a result, you can see when $HIP is being searchedby a .hip file.
• The "=" variable expands to $HIP in pathnames. Thus, if onewants to check $HIP/houdini in HOUDINI_PATH again, the command:

setenv HOUDINI_PATH "=/houdini;&"

can be used.

• A new variable, $HSITE, has been added. This is to allow you tohave somewhere to put site-wide changes without altering the$HFS install.
• The non-HFS relative "houdini" directories are now all appendedwith the DSO Version number (currently 4.9). The good news ofthis is that different major/minor versions of houdini won'tconflict with each others preferences. This applies to $HOMEand $HSITE.

Hopefully the inconvenience caused by this will be outweighed by having a simple, straightforward, and consistent directory paradigm.

PLEASE NOTE THE FOLLOWING CHANGE!

We are attempting to clear up how Houdini treats paths and provide a consistent and intuitive mechanism. Unfortunately, this likely means one will have to change how environment variables are set up.

The following paths are NO LONGER searched by default by the HOUDINI_PATH, nor by the @ short form:

• $HIP/houdini
• $HIP/$USER
• $JOB (which was only searched if $HIP didn't exist)
• /usr/local/houdini

The new search order is:

• $HIP
• $HOME/houdini4.9
• $HSITE/houdini4.9
• $HFS/houdini
• $HFS/bin (NT only)

The following environment variables are no longer installed nor supported:

• $HIH (use $HOME/houdini4.9)
• $HIL (use $HSITE/houdini4.9)
• $HIS (use $HFS/houdini)
• $HIPDIR (use $HIP)

Other changes:

• $HIP now acts like $HIPDIR used to act. It also acts as ifHOUDINI_HIP_FROM_PATH was always set. This means $HIP alwaysprovides a .hip relative path so changing mount points, movingjobs, etc, will not break .hip files.
• $JOB, which was kept from Prisms for backwards compatibility, isretained. It will give you the old $HIP style behaviour. The"job" command now only changes $JOB and not $HIP.
• hconfig now sets $HIP internally to the directory hconfig wasrun from. As a result, you can see when $HIP is being searchedby a .hip file.
• The "=" variable expands to $HIP in pathnames. Thus, if onewants to check $HIP/houdini in HOUDINI_PATH again, the command:

setenv HOUDINI_PATH "=/houdini;&"

can be used.

• A new variable, $HSITE, has been added. This is to allow you tohave somewhere to put site-wide changes without altering the$HFS install.
• The non-HFS relative "houdini" directories are now all appendedwith the DSO Version number (currently 4.9). The good news ofthis is that different major/minor versions of houdini won'tconflict with each others preferences. This applies to $HOMEand $HSITE.

Hopefully the inconvenience caused by this will be outweighed by having a simple, straightforward, and consistent directory paradigm.

PLEASE NOTE THE FOLLOWING CHANGE!

We are attempting to clear up how Houdini treats paths and provide a consistent and intuitive mechanism. Unfortunately, this likely means one will have to change how environment variables are set up.

The following paths are NO LONGER searched by default by the HOUDINI_PATH, nor by the @ short form:

• $HIP/houdini
• $HIP/$USER
• $JOB (which was only searched if $HIP didn't exist)
• /usr/local/houdini

The new search order is:

• $HIP
• $HOME/houdini4.9
• $HSITE/houdini4.9
• $HFS/houdini
• $HFS/bin (NT only)

The following environment variables are no longer installed nor supported:

• $HIH (use $HOME/houdini4.9)
• $HIL (use $HSITE/houdini4.9)
• $HIS (use $HFS/houdini)
• $HIPDIR (use $HIP)

Other changes:

• $HIP now acts like $HIPDIR used to act. It also acts as ifHOUDINI_HIP_FROM_PATH was always set. This means $HIP alwaysprovides a .hip relative path so changing mount points, movingjobs, etc, will not break .hip files.
• $JOB, which was kept from Prisms for backwards compatibility, isretained. It will give you the old $HIP style behaviour. The"job" command now only changes $JOB and not $HIP.
• hconfig now sets $HIP internally to the directory hconfig wasrun from. As a result, you can see when $HIP is being searchedby a .hip file.
• The "=" variable expands to $HIP in pathnames. Thus, if onewants to check $HIP/houdini in HOUDINI_PATH again, the command:

setenv HOUDINI_PATH "=/houdini;&"

can be used.

• A new variable, $HSITE, has been added. This is to allow you tohave somewhere to put site-wide changes without altering the$HFS install.
• The non-HFS relative "houdini" directories are now all appendedwith the DSO Version number (currently 4.9). The good news ofthis is that different major/minor versions of houdini won'tconflict with each others preferences. This applies to $HOMEand $HSITE.

Hopefully the inconvenience caused by this will be outweighed by having a simple, straightforward, and consistent directory paradigm.

PLEASE NOTE THE FOLLOWING CHANGE!

We are attempting to clear up how Houdini treats paths and provide a consistent and intuitive mechanism. Unfortunately, this likely means one will have to change how environment variables are set up.

The following paths are NO LONGER searched by default by the HOUDINI_PATH, nor by the @ short form:

• $HIP/houdini
• $HIP/$USER
• $JOB (which was only searched if $HIP didn't exist)
• /usr/local/houdini

The new search order is:

• $HIP
• $HOME/houdini4.9
• $HSITE/houdini4.9
• $HFS/houdini
• $HFS/bin (NT only)

The following environment variables are no longer installed nor supported:

• $HIH (use $HOME/houdini4.9)
• $HIL (use $HSITE/houdini4.9)
• $HIS (use $HFS/houdini)
• $HIPDIR (use $HIP)

Other changes:

• $HIP now acts like $HIPDIR used to act. It also acts as ifHOUDINI_HIP_FROM_PATH was always set. This means $HIP alwaysprovides a .hip relative path so changing mount points, movingjobs, etc, will not break .hip files.
• $JOB, which was kept from Prisms for backwards compatibility, isretained. It will give you the old $HIP style behaviour. The"job" command now only changes $JOB and not $HIP.
• hconfig now sets $HIP internally to the directory hconfig wasrun from. As a result, you can see when $HIP is being searchedby a .hip file.
• The "=" variable expands to $HIP in pathnames. Thus, if onewants to check $HIP/houdini in HOUDINI_PATH again, the command:

setenv HOUDINI_PATH "=/houdini;&"

can be used.

• A new variable, $HSITE, has been added. This is to allow you tohave somewhere to put site-wide changes without altering the$HFS install.
• The non-HFS relative "houdini" directories are now all appendedwith the DSO Version number (currently 4.9). The good news ofthis is that different major/minor versions of houdini won'tconflict with each others preferences. This applies to $HOMEand $HSITE.

Hopefully the inconvenience caused by this will be outweighed by having a simple, straightforward, and consistent directory paradigm.

We now reset the animation playback settings when starting a new file from File | New.

We now reset the animation playback settings when starting a new file from File | New.

We now reset the animation playback settings when starting a new file from File | New.

We now reset the animation playback settings when starting a new file from File | New.

We now reset the animation playback settings when starting a new file from File | New.

There is now a list of the most recently used files in the File menu that can be used to load files. The history is stored in $HOME/houdini/file.history.

There is now a list of the most recently used files in the File menu that can be used to load files. The history is stored in $HOME/houdini/file.history.

There is now a list of the most recently used files in the File menu that can be used to load files. The history is stored in $HOME/houdini/file.history.

There is now a list of the most recently used files in the File menu that can be used to load files. The history is stored in $HOME/houdini/file.history.

There is now a list of the most recently used files in the File menu that can be used to load files. The history is stored in $HOME/houdini/file.history.

Adding preferences for whether or not secure selection should be on by default at the sop and object levels.

Adding preferences for whether or not secure selection should be on by default at the sop and object levels.

Adding preferences for whether or not secure selection should be on by default at the sop and object levels.

Adding preferences for whether or not secure selection should be on by default at the sop and object levels.