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.

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.

New background image options. Can now set the offset and scaling of the background image. They can be set through the display options or by using the 'viewbackground' command. Their behaviour now is to adjust the offset and scaling relative to the one calculated by the viewer, this will likely change to an absolute position and size.

New background image options. Can now set the offset and scaling of the background image. They can be set through the display options or by using the 'viewbackground' command. Their behaviour now is to adjust the offset and scaling relative to the one calculated by the viewer, this will likely change to an absolute position and size.

New background image options. Can now set the offset and scaling of the background image. They can be set through the display options or by using the 'viewbackground' command. Their behaviour now is to adjust the offset and scaling relative to the one calculated by the viewer, this will likely change to an absolute position and size.

New background image options. Can now set the offset and scaling of the background image. They can be set through the display options or by using the 'viewbackground' command. Their behaviour now is to adjust the offset and scaling relative to the one calculated by the viewer, this will likely change to an absolute position and size.

New background image options. Can now set the offset and scaling of the background image. They can be set through the display options or by using the 'viewbackground' command. Their behaviour now is to adjust the offset and scaling relative to the one calculated by the viewer, this will likely change to an absolute position and size.

The bbox() expression function now takes D_XSIZE, D_YSIZE, and D_ZSIZE to find the respective sizes of the bounding box.

The bbox() expression function now takes D_XSIZE, D_YSIZE, and D_ZSIZE to find the respective sizes of the bounding box.

The bbox() expression function now takes D_XSIZE, D_YSIZE, and D_ZSIZE to find the respective sizes of the bounding box.

The bbox() expression function now takes D_XSIZE, D_YSIZE, and D_ZSIZE to find the respective sizes of the bounding box.

The bbox() expression function now takes D_XSIZE, D_YSIZE, and D_ZSIZE to find the respective sizes of the bounding box.

We now weight points for capture regions in the Capture SOP using the Elendt model. If you want the old method, you will need to set the environment variable HOUDINI_H4_CREGION_WEIGHTING.

We now weight points for capture regions in the Capture SOP using the Elendt model. If you want the old method, you will need to set the environment variable HOUDINI_H4_CREGION_WEIGHTING.