Houdini Select (hselect) is born.

If you have triangles with point normals, you can now convert them to Triangular Beziers.

If you have triangles with point normals, you can now convert them to Triangular Beziers.

If you have triangles with point normals, you can now convert them to Triangular Beziers.

If you have triangles with point normals, you can now convert them to Triangular Beziers.

If you have triangles with point normals, you can now convert them to Triangular Beziers.

Instead of being hard-coded within Houdini, the default op-handle and op-selector bindings are now stored in a text file called OPbindings. This file by default is in $HH, but is searched for using the HOUDINI_PATH, so placing an OPbindings file in $HOME will override the default file. This file can use the #include directive. There is also a new textport command, omwrite. This command writes all current binding information to a specified file (or $HOME/houdini/OPbindings if no file is specified). The output file is in the format required for the OPbindings file.

Instead of being hard-coded within Houdini, the default op-handle and op-selector bindings are now stored in a text file called OPbindings. This file by default is in $HH, but is searched for using the HOUDINI_PATH, so placing an OPbindings file in $HOME will override the default file. This file can use the #include directive. There is also a new textport command, omwrite. This command writes all current binding information to a specified file (or $HOME/houdini/OPbindings if no file is specified). The output file is in the format required for the OPbindings file.

Instead of being hard-coded within Houdini, the default op-handle and op-selector bindings are now stored in a text file called OPbindings. This file by default is in $HH, but is searched for using the HOUDINI_PATH, so placing an OPbindings file in $HOME will override the default file. This file can use the #include directive. There is also a new textport command, omwrite. This command writes all current binding information to a specified file (or $HOME/houdini/OPbindings if no file is specified). The output file is in the format required for the OPbindings file.

Instead of being hard-coded within Houdini, the default op-handle and op-selector bindings are now stored in a text file called OPbindings. This file by default is in $HH, but is searched for using the HOUDINI_PATH, so placing an OPbindings file in $HOME will override the default file. This file can use the #include directive. There is also a new textport command, omwrite. This command writes all current binding information to a specified file (or $HOME/houdini/OPbindings if no file is specified). The output file is in the format required for the OPbindings file.

Instead of being hard-coded within Houdini, the default op-handle and op-selector bindings are now stored in a text file called OPbindings. This file by default is in $HH, but is searched for using the HOUDINI_PATH, so placing an OPbindings file in $HOME will override the default file. This file can use the #include directive. There is also a new textport command, omwrite. This command writes all current binding information to a specified file (or $HOME/houdini/OPbindings if no file is specified). The output file is in the format required for the OPbindings file.

Added several new commands for dynamically modifying OP-selector bindings from the textport. These commands mirror the omXXX commands, and are: omsbind, omsbindinfo, omsls, omsunbind, and omswhere. The parameters are generally very similar to the parameters for the corresponding omXXX commands (except omsbind, which requires very different information).

Added several new commands for dynamically modifying OP-selector bindings from the textport. These commands mirror the omXXX commands, and are: omsbind, omsbindinfo, omsls, omsunbind, and omswhere. The parameters are generally very similar to the parameters for the corresponding omXXX commands (except omsbind, which requires very different information).

Added several new commands for dynamically modifying OP-selector bindings from the textport. These commands mirror the omXXX commands, and are: omsbind, omsbindinfo, omsls, omsunbind, and omswhere. The parameters are generally very similar to the parameters for the corresponding omXXX commands (except omsbind, which requires very different information).

Added several new commands for dynamically modifying OP-selector bindings from the textport. These commands mirror the omXXX commands, and are: omsbind, omsbindinfo, omsls, omsunbind, and omswhere. The parameters are generally very similar to the parameters for the corresponding omXXX commands (except omsbind, which requires very different information).

Added several new commands for dynamically modifying OP-selector bindings from the textport. These commands mirror the omXXX commands, and are: omsbind, omsbindinfo, omsls, omsunbind, and omswhere. The parameters are generally very similar to the parameters for the corresponding omXXX commands (except omsbind, which requires very different information).

The Clip SOP now has the opposite sense for "distance" than before. This is now the logical value - the distance along the given vector to start clipping at - rather than the negation of that.

The Clip SOP now has the opposite sense for "distance" than before. This is now the logical value - the distance along the given vector to start clipping at - rather than the negation of that.

The Clip SOP now has the opposite sense for "distance" than before. This is now the logical value - the distance along the given vector to start clipping at - rather than the negation of that.

The Clip SOP now has the opposite sense for "distance" than before. This is now the logical value - the distance along the given vector to start clipping at - rather than the negation of that.

The Clip SOP now has the opposite sense for "distance" than before. This is now the logical value - the distance along the given vector to start clipping at - rather than the negation of that.

When specifying geometry files for mantra to load (in the Render Tab of the geometry object), it is now possible to have an application which generates geometry. By prefixing the command with a pipe (|) symbol, mantra will open the command and read the geometry from stdout. For example, opparm logo detail_file ( '|gconvert somefile stdout.bgeo' ) will cause mantra to open gconvert as a pipe and read the geometry from the output of the application. It is suggested that bounding box information is also supplied so that mantra can defer opening the pipe until the object is actually required.

When specifying geometry files for mantra to load (in the Render Tab of the geometry object), it is now possible to have an application which generates geometry. By prefixing the command with a pipe (|) symbol, mantra will open the command and read the geometry from stdout. For example, opparm logo detail_file ( '|gconvert somefile stdout.bgeo' ) will cause mantra to open gconvert as a pipe and read the geometry from the output of the application. It is suggested that bounding box information is also supplied so that mantra can defer opening the pipe until the object is actually required.

When specifying geometry files for mantra to load (in the Render Tab of the geometry object), it is now possible to have an application which generates geometry. By prefixing the command with a pipe (|) symbol, mantra will open the command and read the geometry from stdout. For example, opparm logo detail_file ( '|gconvert somefile stdout.bgeo' ) will cause mantra to open gconvert as a pipe and read the geometry from the output of the application. It is suggested that bounding box information is also supplied so that mantra can defer opening the pipe until the object is actually required.

When specifying geometry files for mantra to load (in the Render Tab of the geometry object), it is now possible to have an application which generates geometry. By prefixing the command with a pipe (|) symbol, mantra will open the command and read the geometry from stdout. For example, opparm logo detail_file ( '|gconvert somefile stdout.bgeo' ) will cause mantra to open gconvert as a pipe and read the geometry from the output of the application. It is suggested that bounding box information is also supplied so that mantra can defer opening the pipe until the object is actually required.