Environment Variable Changes:

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. $JOB is nowthe proper way of using an externally-set environment variableto control your .hip behaviour. The path variables now supportenvironment references, so you add $JOB to your search pathwith:

setenv HOUDINI_PATH '$JOB;&'

• 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.
• $HIPNAME now refers to the .hip file only, with all pathsstripped. For the full .hip path, $HIP/$HIPNAME is to be used.
• DSOs are now searched both in @/dso, but also in @/dso_^, wherethe ^ is expanded into a system-specific extension.

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

To change old hip files into the new paradigm, use the opchange command. For example, to change a .hip which was created using $HIP in the old way into one using $JOB, you can:

opchange '$HIP' '$JOB'

This will update most references to JOB.

Environment Variable Changes:

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. $JOB is nowthe proper way of using an externally-set environment variableto control your .hip behaviour. The path variables now supportenvironment references, so you add $JOB to your search pathwith:

setenv HOUDINI_PATH '$JOB;&'

• 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.
• $HIPNAME now refers to the .hip file only, with all pathsstripped. For the full .hip path, $HIP/$HIPNAME is to be used.
• DSOs are now searched both in @/dso, but also in @/dso_^, wherethe ^ is expanded into a system-specific extension.

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

To change old hip files into the new paradigm, use the opchange command. For example, to change a .hip which was created using $HIP in the old way into one using $JOB, you can:

opchange '$HIP' '$JOB'

This will update most references to JOB.

Environment Variable Changes:

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. $JOB is nowthe proper way of using an externally-set environment variableto control your .hip behaviour. The path variables now supportenvironment references, so you add $JOB to your search pathwith:

setenv HOUDINI_PATH '$JOB;&'

• 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.
• $HIPNAME now refers to the .hip file only, with all pathsstripped. For the full .hip path, $HIP/$HIPNAME is to be used.
• DSOs are now searched both in @/dso, but also in @/dso_^, wherethe ^ is expanded into a system-specific extension.

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

To change old hip files into the new paradigm, use the opchange command. For example, to change a .hip which was created using $HIP in the old way into one using $JOB, you can:

opchange '$HIP' '$JOB'

This will update most references to JOB.

Environment Variable Changes:

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. $JOB is nowthe proper way of using an externally-set environment variableto control your .hip behaviour. The path variables now supportenvironment references, so you add $JOB to your search pathwith:

setenv HOUDINI_PATH '$JOB;&'

• 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.
• $HIPNAME now refers to the .hip file only, with all pathsstripped. For the full .hip path, $HIP/$HIPNAME is to be used.
• DSOs are now searched both in @/dso, but also in @/dso_^, wherethe ^ is expanded into a system-specific extension.

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

To change old hip files into the new paradigm, use the opchange command. For example, to change a .hip which was created using $HIP in the old way into one using $JOB, you can:

opchange '$HIP' '$JOB'

This will update most references to JOB.

Environment Variable Changes:

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. $JOB is nowthe proper way of using an externally-set environment variableto control your .hip behaviour. The path variables now supportenvironment references, so you add $JOB to your search pathwith:

setenv HOUDINI_PATH '$JOB;&'

• 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.
• $HIPNAME now refers to the .hip file only, with all pathsstripped. For the full .hip path, $HIP/$HIPNAME is to be used.
• DSOs are now searched both in @/dso, but also in @/dso_^, wherethe ^ is expanded into a system-specific extension.

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

To change old hip files into the new paradigm, use the opchange command. For example, to change a .hip which was created using $HIP in the old way into one using $JOB, you can:

opchange '$HIP' '$JOB'

This will update most references to JOB.

The Clip SOP now uses the opposite sense for its distance parameter. The distance parameter should be negated (multiplied by -1) in old .hip files. The old behaviour is restored if HOUDINI4_COMPATIBILITY is set.

The Clip SOP now uses the opposite sense for its distance parameter. The distance parameter should be negated (multiplied by -1) in old .hip files. The old behaviour is restored if HOUDINI4_COMPATIBILITY is set.

The Clip SOP now uses the opposite sense for its distance parameter. The distance parameter should be negated (multiplied by -1) in old .hip files. The old behaviour is restored if HOUDINI4_COMPATIBILITY is set.

The Clip SOP now uses the opposite sense for its distance parameter. The distance parameter should be negated (multiplied by -1) in old .hip files. The old behaviour is restored if HOUDINI4_COMPATIBILITY is set.

The Clip SOP now uses the opposite sense for its distance parameter. The distance parameter should be negated (multiplied by -1) in old .hip files. The old behaviour is restored if HOUDINI4_COMPATIBILITY is set.

Facet::Remove Inline Points now deletes the points as well as removes them from the geometry. No workaround exists.

Facet::Remove Inline Points now deletes the points as well as removes them from the geometry. No workaround exists.

Facet::Remove Inline Points now deletes the points as well as removes them from the geometry. No workaround exists.

Facet::Remove Inline Points now deletes the points as well as removes them from the geometry. No workaround exists.

Facet::Remove Inline Points now deletes the points as well as removes them from the geometry. No workaround exists.

The Capture SOP now has a "Normalize Capture Weights" toggle which defaults to on. For old style behaviour, turn this off.

The Capture SOP now has a "Normalize Capture Weights" toggle which defaults to on. For old style behaviour, turn this off.

The Capture SOP now has a "Normalize Capture Weights" toggle which defaults to on. For old style behaviour, turn this off.

The Capture SOP now has a "Normalize Capture Weights" toggle which defaults to on. For old style behaviour, turn this off.

The Capture SOP now has a "Normalize Capture Weights" toggle which defaults to on. For old style behaviour, turn this off.

The Box SOP defaults to generating consolidated points. For the old behaviour, turn off the point consolidation.

The Box SOP defaults to generating consolidated points. For the old behaviour, turn off the point consolidation.

The Box SOP defaults to generating consolidated points. For the old behaviour, turn off the point consolidation.