Houdini Main Changelogs

6.1.13

Fixed bug where collapsible transform in COPs would sometimes result in an incorrect concatenation of operations.

Wed. May 14, 2003
6.1.13

Fixed bug where collapsible transform in COPs would sometimes result in an incorrect concatenation of operations.

Wed. May 14, 2003
6.1.13

Fixed bug where collapsible transform in COPs would sometimes result in an incorrect concatenation of operations.

Wed. May 14, 2003
6.1.13

Fixed bug where collapsible transform in COPs would sometimes result in an incorrect concatenation of operations.

Wed. May 14, 2003
6.1.12

Use ALT+LMB to select multiple spline point handles, rather than CTRL+LMB. Unfortunately, CTRL+LMB conflicts with way too many other operations in the viewer.

Tue. May 13, 2003
6.1.12

Use ALT+LMB to select multiple spline point handles, rather than CTRL+LMB. Unfortunately, CTRL+LMB conflicts with way too many other operations in the viewer.

Tue. May 13, 2003
6.1.12

Use ALT+LMB to select multiple spline point handles, rather than CTRL+LMB. Unfortunately, CTRL+LMB conflicts with way too many other operations in the viewer.

Tue. May 13, 2003
6.1.12

Use ALT+LMB to select multiple spline point handles, rather than CTRL+LMB. Unfortunately, CTRL+LMB conflicts with way too many other operations in the viewer.

Tue. May 13, 2003
6.1.12

Use ALT+LMB to select multiple spline point handles, rather than CTRL+LMB. Unfortunately, CTRL+LMB conflicts with way too many other operations in the viewer.

Tue. May 13, 2003
6.1.12

The swap COP has been updated to store the plane mapping information in string parameters. This means that deleting a plane from the input will not reorder all the parameters. Backwards compatibility is almost maintained, but the node only updates itself when the sequence info cooks. Thus, you may need to cook the node. Please be aware of this.

Tue. May 13, 2003
6.1.12

The swap COP has been updated to store the plane mapping information in string parameters. This means that deleting a plane from the input will not reorder all the parameters. Backwards compatibility is almost maintained, but the node only updates itself when the sequence info cooks. Thus, you may need to cook the node. Please be aware of this.

Tue. May 13, 2003
6.1.12

The swap COP has been updated to store the plane mapping information in string parameters. This means that deleting a plane from the input will not reorder all the parameters. Backwards compatibility is almost maintained, but the node only updates itself when the sequence info cooks. Thus, you may need to cook the node. Please be aware of this.

Tue. May 13, 2003
6.1.12

The swap COP has been updated to store the plane mapping information in string parameters. This means that deleting a plane from the input will not reorder all the parameters. Backwards compatibility is almost maintained, but the node only updates itself when the sequence info cooks. Thus, you may need to cook the node. Please be aware of this.

Tue. May 13, 2003
6.1.12

The swap COP has been updated to store the plane mapping information in string parameters. This means that deleting a plane from the input will not reorder all the parameters. Backwards compatibility is almost maintained, but the node only updates itself when the sequence info cooks. Thus, you may need to cook the node. Please be aware of this.

Tue. May 13, 2003
6.1.12

The swap COP now correctly uses string parameters to represent the plane mappings. This is transparent to the user, though unfortunately, not backwards compatible. The best that can be done is that the node will update itself when it cooks its sequence info.

Tue. May 13, 2003
6.1.12

The swap COP now correctly uses string parameters to represent the plane mappings. This is transparent to the user, though unfortunately, not backwards compatible. The best that can be done is that the node will update itself when it cooks its sequence info.

Tue. May 13, 2003
6.1.12

The swap COP now correctly uses string parameters to represent the plane mappings. This is transparent to the user, though unfortunately, not backwards compatible. The best that can be done is that the node will update itself when it cooks its sequence info.

Tue. May 13, 2003
6.1.12

The swap COP now correctly uses string parameters to represent the plane mappings. This is transparent to the user, though unfortunately, not backwards compatible. The best that can be done is that the node will update itself when it cooks its sequence info.

Tue. May 13, 2003
6.1.12

The swap COP now correctly uses string parameters to represent the plane mappings. This is transparent to the user, though unfortunately, not backwards compatible. The best that can be done is that the node will update itself when it cooks its sequence info.

Tue. May 13, 2003
6.1.12

Fixed bug where a constant tile would not be correctly composited over a non-constant tile in certain cases where large canvas support and motion blur was turned on, and the real constant tile boundaries were all inside the frame (as in the output of a Color COP).

Tue. May 13, 2003
6.1.12

Fixed bug where a constant tile would not be correctly composited over a non-constant tile in certain cases where large canvas support and motion blur was turned on, and the real constant tile boundaries were all inside the frame (as in the output of a Color COP).

Tue. May 13, 2003
6.1.12

Fixed bug where a constant tile would not be correctly composited over a non-constant tile in certain cases where large canvas support and motion blur was turned on, and the real constant tile boundaries were all inside the frame (as in the output of a Color COP).

Tue. May 13, 2003
6.1.12

Fixed bug where a constant tile would not be correctly composited over a non-constant tile in certain cases where large canvas support and motion blur was turned on, and the real constant tile boundaries were all inside the frame (as in the output of a Color COP).

Tue. May 13, 2003
6.1.12

Fixed bug where a constant tile would not be correctly composited over a non-constant tile in certain cases where large canvas support and motion blur was turned on, and the real constant tile boundaries were all inside the frame (as in the output of a Color COP).

Tue. May 13, 2003
6.1.12

Fixed bug where we were incorrectly clipping the boundaries of a transformed region, which sometimes resulted in incomplete images.

Tue. May 13, 2003