When generating an OTL file from MentalRay shaders using mids, the shaders are now properly classified by type (light, surface, etc). Unsupported shader types (i.e. shader types that Houdini does not know how to use) are not added to the OTL and generate an error message.

When generating an OTL file from MentalRay shaders using mids, the shaders are now properly classified by type (light, surface, etc). Unsupported shader types (i.e. shader types that Houdini does not know how to use) are not added to the OTL and generate an error message.

When generating an OTL file from MentalRay shaders using mids, the shaders are now properly classified by type (light, surface, etc). Unsupported shader types (i.e. shader types that Houdini does not know how to use) are not added to the OTL and generate an error message.

When generating an OTL file from MentalRay shaders using mids, the shaders are now properly classified by type (light, surface, etc). Unsupported shader types (i.e. shader types that Houdini does not know how to use) are not added to the OTL and generate an error message.

When the auto-generate depth map option is turned on for a light source, Houdini will now verify that there's a valid filename before attempting to let the renderer generate the depth map.

When the auto-generate depth map option is turned on for a light source, Houdini will now verify that there's a valid filename before attempting to let the renderer generate the depth map.

When the auto-generate depth map option is turned on for a light source, Houdini will now verify that there's a valid filename before attempting to let the renderer generate the depth map.

When the auto-generate depth map option is turned on for a light source, Houdini will now verify that there's a valid filename before attempting to let the renderer generate the depth map.

When the auto-generate depth map option is turned on for a light source, Houdini will now verify that there's a valid filename before attempting to let the renderer generate the depth map.

The Bake VEX SOP now handles indirect SHOP references for shader definitions.

The Bake VEX SOP now handles indirect SHOP references for shader definitions.

The Bake VEX SOP now handles indirect SHOP references for shader definitions.

The Bake VEX SOP now handles indirect SHOP references for shader definitions.

The Bake VEX SOP now handles indirect SHOP references for shader definitions.

There was a memory leak with displacement shaders in VEX shaded mode. This has been fixed.

There was a memory leak with displacement shaders in VEX shaded mode. This has been fixed.

There was a memory leak with displacement shaders in VEX shaded mode. This has been fixed.

There was a memory leak with displacement shaders in VEX shaded mode. This has been fixed.

There was a memory leak with displacement shaders in VEX shaded mode. This has been fixed.

Fixed reading of AIFF files that were embedded inside an operator type definition inside an OTL.

Fixed reading of AIFF files that were embedded inside an operator type definition inside an OTL.

Fixed reading of AIFF files that were embedded inside an operator type definition inside an OTL.

Fixed reading of AIFF files that were embedded inside an operator type definition inside an OTL.

Fixed reading of AIFF files that were embedded inside an operator type definition inside an OTL.

Fixed bug which would result in a core dump if an OTL file containing a SHOP definition had its time stamp or contents changed while Houdini was running with an instance of that SHOP, and the "Refresh Operator Type Libraries" or otrefresh commands were not run. In this situation, changing a SHOP parameter value and then rendering would cause Houdini to crash.