Houdini Main Changelogs

6.2.42

Fixed the bug that prevented uvpoint manipulateor (Align SOP) and object-level path handle from reaching the exact endpoints of the curve (i.e., the parameter approaching 0 or 1)

Tue. November 11, 2003
6.2.42

Fixed the bug that prevented uvpoint manipulateor (Align SOP) and object-level path handle from reaching the exact endpoints of the curve (i.e., the parameter approaching 0 or 1)

Tue. November 11, 2003
6.2.42

Fixed the bug that prevented uvpoint manipulateor (Align SOP) and object-level path handle from reaching the exact endpoints of the curve (i.e., the parameter approaching 0 or 1)

Tue. November 11, 2003
6.2.42

Fixed the bug that prevented uvpoint manipulateor (Align SOP) and object-level path handle from reaching the exact endpoints of the curve (i.e., the parameter approaching 0 or 1)

Tue. November 11, 2003
6.2.42

Fixed the bug which would cause SOPs, CHOPs, and some other OPs to appear with disabled icons in their tiles if the node was write- protected or inside a locked subnet.

Tue. November 11, 2003
6.2.42

Fixed the bug which would cause SOPs, CHOPs, and some other OPs to appear with disabled icons in their tiles if the node was write- protected or inside a locked subnet.

Tue. November 11, 2003
6.2.42

Fixed the bug which would cause SOPs, CHOPs, and some other OPs to appear with disabled icons in their tiles if the node was write- protected or inside a locked subnet.

Tue. November 11, 2003
6.2.42

Fixed the bug which would cause SOPs, CHOPs, and some other OPs to appear with disabled icons in their tiles if the node was write- protected or inside a locked subnet.

Tue. November 11, 2003
6.2.42

Fixed the bug which would cause SOPs, CHOPs, and some other OPs to appear with disabled icons in their tiles if the node was write- protected or inside a locked subnet.

Tue. November 11, 2003
6.2.42

With custom VEX-Ops, the optimization levels have changed slightly. This impacts any users who have written VEX plug-ins. Please see on-line VEX documentation for details. This means that VEX plug-in source code may have to be modified and recompiled for correct behaviour.

Tue. November 11, 2003
6.2.42

With custom VEX-Ops, the optimization levels have changed slightly. This impacts any users who have written VEX plug-ins. Please see on-line VEX documentation for details. This means that VEX plug-in source code may have to be modified and recompiled for correct behaviour.

Tue. November 11, 2003
6.2.42

With custom VEX-Ops, the optimization levels have changed slightly. This impacts any users who have written VEX plug-ins. Please see on-line VEX documentation for details. This means that VEX plug-in source code may have to be modified and recompiled for correct behaviour.

Tue. November 11, 2003
6.2.42

With custom VEX-Ops, the optimization levels have changed slightly. This impacts any users who have written VEX plug-ins. Please see on-line VEX documentation for details. This means that VEX plug-in source code may have to be modified and recompiled for correct behaviour.

Tue. November 11, 2003
6.2.42

With custom VEX-Ops, the optimization levels have changed slightly. This impacts any users who have written VEX plug-ins. Please see on-line VEX documentation for details. This means that VEX plug-in source code may have to be modified and recompiled for correct behaviour.

Tue. November 11, 2003
6.2.42

With custom VEX-Ops, the optimization levels have changed slightly. This impacts any users who have written VEX plug-ins. Please see on-line VEX documentation for details.

Tue. November 11, 2003
6.2.42

With custom VEX-Ops, the optimization levels have changed slightly. This impacts any users who have written VEX plug-ins. Please see on-line VEX documentation for details.

Tue. November 11, 2003
6.2.42

With custom VEX-Ops, the optimization levels have changed slightly. This impacts any users who have written VEX plug-ins. Please see on-line VEX documentation for details.

Tue. November 11, 2003
6.2.42

With custom VEX-Ops, the optimization levels have changed slightly. This impacts any users who have written VEX plug-ins. Please see on-line VEX documentation for details.

Tue. November 11, 2003
6.2.42

With custom VEX-Ops, the optimization levels have changed slightly. This impacts any users who have written VEX plug-ins. Please see on-line VEX documentation for details.

Tue. November 11, 2003
6.2.42

When generating RIB, the global shading quality multiplier specified in the output driver was being considered twice. This caused incorrect shading rates to be generated in the RIB stream. This has been fixed.

Tue. November 11, 2003
6.2.42

When generating RIB, the global shading quality multiplier specified in the output driver was being considered twice. This caused incorrect shading rates to be generated in the RIB stream. This has been fixed.

Tue. November 11, 2003
6.2.42

When generating RIB, the global shading quality multiplier specified in the output driver was being considered twice. This caused incorrect shading rates to be generated in the RIB stream. This has been fixed.

Tue. November 11, 2003
6.2.42

When generating RIB, the global shading quality multiplier specified in the output driver was being considered twice. This caused incorrect shading rates to be generated in the RIB stream. This has been fixed.

Tue. November 11, 2003
6.2.42

When generating RIB, the global shading quality multiplier specified in the output driver was being considered twice. This caused incorrect shading rates to be generated in the RIB stream. This has been fixed.

Tue. November 11, 2003
6.2.42

When generating RIB, the global shading quality multiplier specified in the output driver was being considered twice. This caused incorrect shading rates to be generated in the RIB stream. This has been fixed.

Tue. November 11, 2003