The variable to control threading in the IMG library was changed from SESI_THREAD_NOIMG to HOUDINI_THREAD_IMAGE. The sense of the variable was also changed so that threading is turned off by default. This doesn't affect COP2, but will affect the old composite operators and most noticably, ipaint.

The variable to control threading in the IMG library was changed from SESI_THREAD_NOIMG to HOUDINI_THREAD_IMAGE. The sense of the variable was also changed so that threading is turned off by default. This doesn't affect COP2, but will affect the old composite operators and most noticably, ipaint.

The variable to control threading in the IMG library was changed from SESI_THREAD_NOIMG to HOUDINI_THREAD_IMAGE. The sense of the variable was also changed so that threading is turned off by default. This doesn't affect COP2, but will affect the old composite operators and most noticably, ipaint.

The variable to control threading in the IMG library was changed from SESI_THREAD_NOIMG to HOUDINI_THREAD_IMAGE. The sense of the variable was also changed so that threading is turned off by default. This doesn't affect COP2, but will affect the old composite operators and most noticably, ipaint.

When objects of the same name were in different sub-networks, the renderer got confused as to which object was being referred to. For objects in sub-networks, the name passed to the renderer now includes the full path without the leading "/obj/". When dealing with objects in subnetworks, this is the name which should be used when specifying visible objects. For example: *,^s_windmill1/* will match all objects except for the objects contained in s_windmill1. Note that the pattern: s_windmill1 will not cause the objects in the subnet to be rendered, the asterix must be specified in the pattern.

When objects of the same name were in different sub-networks, the renderer got confused as to which object was being referred to. For objects in sub-networks, the name passed to the renderer now includes the full path without the leading "/obj/". When dealing with objects in subnetworks, this is the name which should be used when specifying visible objects. For example: *,^s_windmill1/* will match all objects except for the objects contained in s_windmill1. Note that the pattern: s_windmill1 will not cause the objects in the subnet to be rendered, the asterix must be specified in the pattern.

When objects of the same name were in different sub-networks, the renderer got confused as to which object was being referred to. For objects in sub-networks, the name passed to the renderer now includes the full path without the leading "/obj/". When dealing with objects in subnetworks, this is the name which should be used when specifying visible objects. For example: *,^s_windmill1/* will match all objects except for the objects contained in s_windmill1. Note that the pattern: s_windmill1 will not cause the objects in the subnet to be rendered, the asterix must be specified in the pattern.

When objects of the same name were in different sub-networks, the renderer got confused as to which object was being referred to. For objects in sub-networks, the name passed to the renderer now includes the full path without the leading "/obj/". When dealing with objects in subnetworks, this is the name which should be used when specifying visible objects. For example: *,^s_windmill1/* will match all objects except for the objects contained in s_windmill1. Note that the pattern: s_windmill1 will not cause the objects in the subnet to be rendered, the asterix must be specified in the pattern.

When objects of the same name were in different sub-networks, the renderer got confused as to which object was being referred to. For objects in sub-networks, the name passed to the renderer now includes the full path without the leading "/obj/". When dealing with objects in subnetworks, this is the name which should be used when specifying visible objects. For example: *,^s_windmill1/* will match all objects except for the objects contained in s_windmill1. Note that the pattern: s_windmill1 will not cause the objects in the subnet to be rendered, the asterix must be specified in the pattern.

Fixed a problem with wren that produced small breaks in lines.

Fixed a problem with wren that produced small breaks in lines.

Fixed a problem with wren that produced small breaks in lines.

Fixed a problem with wren that produced small breaks in lines.

Fixed a problem with wren that produced small breaks in lines.

The Capture page under the Bone object's parameters dialog now only shows the parameters that are relevant to the bone's capture type. They change when you change the capture type.

The Capture page under the Bone object's parameters dialog now only shows the parameters that are relevant to the bone's capture type. They change when you change the capture type.

The Capture page under the Bone object's parameters dialog now only shows the parameters that are relevant to the bone's capture type. They change when you change the capture type.

The Capture page under the Bone object's parameters dialog now only shows the parameters that are relevant to the bone's capture type. They change when you change the capture type.

The Capture page under the Bone object's parameters dialog now only shows the parameters that are relevant to the bone's capture type. They change when you change the capture type.

The Capture region handle now has an option for showing it as opaque. This provides a quick way to determine if points are within a capture region without using a Capture SOP.

The Capture region handle now has an option for showing it as opaque. This provides a quick way to determine if points are within a capture region without using a Capture SOP.

The Capture region handle now has an option for showing it as opaque. This provides a quick way to determine if points are within a capture region without using a Capture SOP.

The Capture region handle now has an option for showing it as opaque. This provides a quick way to determine if points are within a capture region without using a Capture SOP.

The Capture region handle now has an option for showing it as opaque. This provides a quick way to determine if points are within a capture region without using a Capture SOP.

Changing an operator name now causes any manipulators which are attached to that operator to potentially change their name as well. The manipulator searches for the old op name, and replaces it with the new one.