When i3dgen generates metaballs on point/particle geometry, the standard Houdini instancing code is now used. This means that the metaballs used in i3dgen can now be oriented, scaled, etc.

When i3dgen generates metaballs on point/particle geometry, the standard Houdini instancing code is now used. This means that the metaballs used in i3dgen can now be oriented, scaled, etc.

When i3dgen generates metaballs on point/particle geometry, the standard Houdini instancing code is now used. This means that the metaballs used in i3dgen can now be oriented, scaled, etc.

Fixed bug in Houdini's command line applications (like mplay) that could sometimes crash on Windows if the supplied command line was too long. For example, typing 'mplay *.jpg' in a directory that contains many files should now only be limited by the command line limit of the user's shell.

Fixed bug in Houdini's command line applications (like mplay) that could sometimes crash on Windows if the supplied command line was too long. For example, typing 'mplay *.jpg' in a directory that contains many files should now only be limited by the command line limit of the user's shell.

Fixed bug in Houdini's command line applications (like mplay) that could sometimes crash on Windows if the supplied command line was too long. For example, typing 'mplay *.jpg' in a directory that contains many files should now only be limited by the command line limit of the user's shell.

Fixed bug in Houdini's command line applications (like mplay) that could sometimes crash on Windows if the supplied command line was too long. For example, typing 'mplay *.jpg' in a directory that contains many files should now only be limited by the command line limit of the user's shell.

Fixed bug in Houdini's command line applications (like mplay) that could sometimes crash on Windows if the supplied command line was too long. For example, typing 'mplay *.jpg' in a directory that contains many files should now only be limited by the command line limit of the user's shell.

Fixed bug in mplay where specifying a frame range on the command line along with the -C option for caching, would ignore the frame range and cache all the available files. Now, only the files in the specified frame range are cached. If the user later decides to change the frame range, the additional files must be loaded explicitly.

Fixed bug in mplay where specifying a frame range on the command line along with the -C option for caching, would ignore the frame range and cache all the available files. Now, only the files in the specified frame range are cached. If the user later decides to change the frame range, the additional files must be loaded explicitly.

Fixed bug in mplay where specifying a frame range on the command line along with the -C option for caching, would ignore the frame range and cache all the available files. Now, only the files in the specified frame range are cached. If the user later decides to change the frame range, the additional files must be loaded explicitly.

Fixed bug in mplay where specifying a frame range on the command line along with the -C option for caching, would ignore the frame range and cache all the available files. Now, only the files in the specified frame range are cached. If the user later decides to change the frame range, the additional files must be loaded explicitly.

Fixed bug in mplay where specifying a frame range on the command line along with the -C option for caching, would ignore the frame range and cache all the available files. Now, only the files in the specified frame range are cached. If the user later decides to change the frame range, the additional files must be loaded explicitly.

When editing the Type Properties of compositing operators, some reserved parameters would erroneously appear in the Parameters list, which in turn could lead to the generation of invalid operator type definitions. These reserved parameters no longer do this.

When editing the Type Properties of compositing operators, some reserved parameters would erroneously appear in the Parameters list, which in turn could lead to the generation of invalid operator type definitions. These reserved parameters no longer do this.

When editing the Type Properties of compositing operators, some reserved parameters would erroneously appear in the Parameters list, which in turn could lead to the generation of invalid operator type definitions. These reserved parameters no longer do this.

When editing the Type Properties of compositing operators, some reserved parameters would erroneously appear in the Parameters list, which in turn could lead to the generation of invalid operator type definitions. These reserved parameters no longer do this.

When editing the Type Properties of compositing operators, some reserved parameters would erroneously appear in the Parameters list, which in turn could lead to the generation of invalid operator type definitions. These reserved parameters no longer do this.

Matrices are now output with double precision to RIB streams. This improves accuracy for large scale scenes.

Matrices are now output with double precision to RIB streams. This improves accuracy for large scale scenes.

Matrices are now output with double precision to RIB streams. This improves accuracy for large scale scenes.

Matrices are now output with double precision to RIB streams. This improves accuracy for large scale scenes.

Matrices are now output with double precision to RIB streams. This improves accuracy for large scale scenes.

The geometry CHOP now creates a 0 sample channel when given a zero point geometry, rather than a 1 sample channel of random data.

The geometry CHOP now creates a 0 sample channel when given a zero point geometry, rather than a 1 sample channel of random data.