Houdini Main Changelogs
5.1.73 | Added preference for what viewers can save their view commands to the hip files. This should help combat file bloat in the .application section. |
Thu. April 4, 2002 | |
5.1.72 | The opget command now properly reports on the status of the object origin axis flag. Similarly, when opscript is used on an object, the resulting opset command will contain the proper object origin axis flag state. |
Wed. April 3, 2002 | |
5.1.72 | The opget command now properly reports on the status of the object origin axis flag. Similarly, when opscript is used on an object, the resulting opset command will contain the proper object origin axis flag state. |
Wed. April 3, 2002 | |
5.1.72 | The opget command now properly reports on the status of the object origin axis flag. Similarly, when opscript is used on an object, the resulting opset command will contain the proper object origin axis flag state. |
Wed. April 3, 2002 | |
5.1.72 | The opget command now properly reports on the status of the object origin axis flag. Similarly, when opscript is used on an object, the resulting opset command will contain the proper object origin axis flag state. |
Wed. April 3, 2002 | |
5.1.72 | The opget command now properly reports on the status of the object origin axis flag. Similarly, when opscript is used on an object, the resulting opset command will contain the proper object origin axis flag state. |
Wed. April 3, 2002 | |
5.1.72 | The Magnet SOPs group will no longer seem to stick with an old group even after the group has changed. |
Wed. April 3, 2002 | |
5.1.72 | The Magnet SOPs group will no longer seem to stick with an old group even after the group has changed. |
Wed. April 3, 2002 | |
5.1.72 | The Magnet SOPs group will no longer seem to stick with an old group even after the group has changed. |
Wed. April 3, 2002 | |
5.1.72 | The Magnet SOPs group will no longer seem to stick with an old group even after the group has changed. |
Wed. April 3, 2002 | |
5.1.72 | The Magnet SOPs group will no longer seem to stick with an old group even after the group has changed. |
Wed. April 3, 2002 | |
5.1.71 | When modelling using the viewport inside a SOP subnet, the numbered inputs now also get correctly laid out. |
Tue. April 2, 2002 | |
5.1.71 | When modelling using the viewport inside a SOP subnet, the numbered inputs now also get correctly laid out. |
Tue. April 2, 2002 | |
5.1.71 | When modelling using the viewport inside a SOP subnet, the numbered inputs now also get correctly laid out. |
Tue. April 2, 2002 | |
5.1.71 | When modelling using the viewport inside a SOP subnet, the numbered inputs now also get correctly laid out. |
Tue. April 2, 2002 | |
5.1.71 | When modelling using the viewport inside a SOP subnet, the numbered inputs now also get correctly laid out. |
Tue. April 2, 2002 | |
5.1.71 | The Rename Selected Nodes dialog now properly disables the prefix and suffix end/start character fields when you first open it. |
Tue. April 2, 2002 | |
5.1.71 | The Rename Selected Nodes dialog now properly disables the prefix and suffix end/start character fields when you first open it. |
Tue. April 2, 2002 | |
5.1.71 | The Rename Selected Nodes dialog now properly disables the prefix and suffix end/start character fields when you first open it. |
Tue. April 2, 2002 | |
5.1.71 | The Rename Selected Nodes dialog now properly disables the prefix and suffix end/start character fields when you first open it. |
Tue. April 2, 2002 | |
5.1.71 | The Rename Selected Nodes dialog now properly disables the prefix and suffix end/start character fields when you first open it. |
Tue. April 2, 2002 | |
5.1.71 | The Properties::Parameters page now has a Disable When field where you can write the peculiar disable expressions that are supported by Vex. While not particularly user friendly, this has the virtue of preserving Vex disable values across property edits. |
Tue. April 2, 2002 | |
5.1.71 | The Properties::Parameters page now has a Disable When field where you can write the peculiar disable expressions that are supported by Vex. While not particularly user friendly, this has the virtue of preserving Vex disable values across property edits. |
Tue. April 2, 2002 | |
5.1.71 | The Properties::Parameters page now has a Disable When field where you can write the peculiar disable expressions that are supported by Vex. While not particularly user friendly, this has the virtue of preserving Vex disable values across property edits. |
Tue. April 2, 2002 | |
5.1.71 | The Properties::Parameters page now has a Disable When field where you can write the peculiar disable expressions that are supported by Vex. While not particularly user friendly, this has the virtue of preserving Vex disable values across property edits. |
Tue. April 2, 2002 |