Houdini Main Changelogs

6.0.229

The Parent tool and the Dynamic Parent tool behave a little better in the context of subnetworks. Fetch objects are created for child-parent pairs that aren't in the same subnet, unless a chain can be found from the parent to the child through indirect inputs.

Tue. March 4, 2003
6.0.229

The Parent tool and the Dynamic Parent tool behave a little better in the context of subnetworks. Fetch objects are created for child-parent pairs that aren't in the same subnet, unless a chain can be found from the parent to the child through indirect inputs.

Tue. March 4, 2003
6.0.229

The Parent tool and the Dynamic Parent tool behave a little better in the context of subnetworks. Fetch objects are created for child-parent pairs that aren't in the same subnet, unless a chain can be found from the parent to the child through indirect inputs.

Tue. March 4, 2003
6.0.229

The icon for the current pane type is no longer a pulldown menu. You now must use the pane menu.

Tue. March 4, 2003
6.0.229

The icon for the current pane type is no longer a pulldown menu. You now must use the pane menu.

Tue. March 4, 2003
6.0.229

The icon for the current pane type is no longer a pulldown menu. You now must use the pane menu.

Tue. March 4, 2003
6.0.229

The icon for the current pane type is no longer a pulldown menu. You now must use the pane menu.

Tue. March 4, 2003
6.0.229

The icon for the current pane type is no longer a pulldown menu. You now must use the pane menu.

Tue. March 4, 2003
6.0.229

When expressions referred to a valid CHOP, but an invalid track, they were not getting extra inputs. This meant they would not notice when the track became valid.

Tue. March 4, 2003
6.0.229

When expressions referred to a valid CHOP, but an invalid track, they were not getting extra inputs. This meant they would not notice when the track became valid.

Tue. March 4, 2003
6.0.229

When expressions referred to a valid CHOP, but an invalid track, they were not getting extra inputs. This meant they would not notice when the track became valid.

Tue. March 4, 2003
6.0.229

When expressions referred to a valid CHOP, but an invalid track, they were not getting extra inputs. This meant they would not notice when the track became valid.

Tue. March 4, 2003
6.0.229

When expressions referred to a valid CHOP, but an invalid track, they were not getting extra inputs. This meant they would not notice when the track became valid.

Tue. March 4, 2003
6.0.229

Removing the Network menu from pane types that don't use network paths (like the text editor, the help browser, etc.).

Tue. March 4, 2003
6.0.229

Removing the Network menu from pane types that don't use network paths (like the text editor, the help browser, etc.).

Tue. March 4, 2003
6.0.229

Removing the Network menu from pane types that don't use network paths (like the text editor, the help browser, etc.).

Tue. March 4, 2003
6.0.229

Removing the Network menu from pane types that don't use network paths (like the text editor, the help browser, etc.).

Tue. March 4, 2003
6.0.229

Removing the Network menu from pane types that don't use network paths (like the text editor, the help browser, etc.).

Tue. March 4, 2003
6.0.229

CHOP expressions such as chopf() no longer generate error flags with invalid parameters. This now matches the behaviour of other OP expressions such as the SOP point() function. This was required as the error messages were ending up on the wrong nodes, preventing them cooking.

Tue. March 4, 2003
6.0.229

CHOP expressions such as chopf() no longer generate error flags with invalid parameters. This now matches the behaviour of other OP expressions such as the SOP point() function. This was required as the error messages were ending up on the wrong nodes, preventing them cooking.

Tue. March 4, 2003
6.0.229

CHOP expressions such as chopf() no longer generate error flags with invalid parameters. This now matches the behaviour of other OP expressions such as the SOP point() function. This was required as the error messages were ending up on the wrong nodes, preventing them cooking.

Tue. March 4, 2003
6.0.229

CHOP expressions such as chopf() no longer generate error flags with invalid parameters. This now matches the behaviour of other OP expressions such as the SOP point() function. This was required as the error messages were ending up on the wrong nodes, preventing them cooking.

Tue. March 4, 2003
6.0.229

CHOP expressions such as chopf() no longer generate error flags with invalid parameters. This now matches the behaviour of other OP expressions such as the SOP point() function. This was required as the error messages were ending up on the wrong nodes, preventing them cooking.

Tue. March 4, 2003
6.0.229

The Null CHOP has been changed to properly lock and unlock its inputs, which should resolves some intermittent cooking problems.

Tue. March 4, 2003
6.0.229

The Null CHOP has been changed to properly lock and unlock its inputs, which should resolves some intermittent cooking problems.

Tue. March 4, 2003