Houdini Main Changelogs
6.2.20 | When a Transformer handle from a contained SOP is promoted to be bound to the parameters of a top-level subnet, the scale and rotate operations now behave properly. |
Mon. October 20, 2003 | |
6.2.20 | When a Transformer handle from a contained SOP is promoted to be bound to the parameters of a top-level subnet, the scale and rotate operations now behave properly. |
Mon. October 20, 2003 | |
6.2.20 | When a Transformer handle from a contained SOP is promoted to be bound to the parameters of a top-level subnet, the scale and rotate operations now behave properly. |
Mon. October 20, 2003 | |
6.2.20 | It is now possible to set custom help on a per-parameter basis for an operator type. This help appears in the popup help text when the cursor is floated over a label in the parameter dialog. This custom help text can also be set in a Parameter VOP or using a parmhelp pragma in a .vfl file. |
Mon. October 20, 2003 | |
6.2.20 | It is now possible to set custom help on a per-parameter basis for an operator type. This help appears in the popup help text when the cursor is floated over a label in the parameter dialog. This custom help text can also be set in a Parameter VOP or using a parmhelp pragma in a .vfl file. |
Mon. October 20, 2003 | |
6.2.20 | It is now possible to set custom help on a per-parameter basis for an operator type. This help appears in the popup help text when the cursor is floated over a label in the parameter dialog. This custom help text can also be set in a Parameter VOP or using a parmhelp pragma in a .vfl file. |
Mon. October 20, 2003 | |
6.2.20 | It is now possible to set custom help on a per-parameter basis for an operator type. This help appears in the popup help text when the cursor is floated over a label in the parameter dialog. This custom help text can also be set in a Parameter VOP or using a parmhelp pragma in a .vfl file. |
Mon. October 20, 2003 | |
6.2.20 | It is now possible to set custom help on a per-parameter basis for an operator type. This help appears in the popup help text when the cursor is floated over a label in the parameter dialog. This custom help text can also be set in a Parameter VOP or using a parmhelp pragma in a .vfl file. |
Mon. October 20, 2003 | |
6.2.20 | When choosing "Create Type From..." from the popup RMB menu for a subnet operator, when the Type Properties dialog appears, Houdini automatically saves the new operator type as if the Apply button was pressed. |
Mon. October 20, 2003 | |
6.2.20 | When choosing "Create Type From..." from the popup RMB menu for a subnet operator, when the Type Properties dialog appears, Houdini automatically saves the new operator type as if the Apply button was pressed. |
Mon. October 20, 2003 | |
6.2.20 | When choosing "Create Type From..." from the popup RMB menu for a subnet operator, when the Type Properties dialog appears, Houdini automatically saves the new operator type as if the Apply button was pressed. |
Mon. October 20, 2003 | |
6.2.20 | When choosing "Create Type From..." from the popup RMB menu for a subnet operator, when the Type Properties dialog appears, Houdini automatically saves the new operator type as if the Apply button was pressed. |
Mon. October 20, 2003 | |
6.2.20 | When choosing "Create Type From..." from the popup RMB menu for a subnet operator, when the Type Properties dialog appears, Houdini automatically saves the new operator type as if the Apply button was pressed. |
Mon. October 20, 2003 | |
6.2.20 | Undoing a rename operation on a locked subnet operator type could cause the expressions of the nodes inside the subnet to be erased. This problem is now fixed. |
Mon. October 20, 2003 | |
6.2.20 | Undoing a rename operation on a locked subnet operator type could cause the expressions of the nodes inside the subnet to be erased. This problem is now fixed. |
Mon. October 20, 2003 | |
6.2.20 | Undoing a rename operation on a locked subnet operator type could cause the expressions of the nodes inside the subnet to be erased. This problem is now fixed. |
Mon. October 20, 2003 | |
6.2.20 | Undoing a rename operation on a locked subnet operator type could cause the expressions of the nodes inside the subnet to be erased. This problem is now fixed. |
Mon. October 20, 2003 | |
6.2.20 | Undoing a rename operation on a locked subnet operator type could cause the expressions of the nodes inside the subnet to be erased. This problem is now fixed. |
Mon. October 20, 2003 | |
6.2.20 | Fixed a problem with channel referencing a parameter of a node that is not cooked (such as an object that isn't displayed). Suppose geo1, geo2, and geo3 are all objects. geo2 is not displayed. geo2/tx is 'ch("../geo1/tx")' and geo3/tx is 'ch("../geo2/tx")'. Changing geo1/tx would not move geo3 because geo2 would not cook and so would not propagate the parameter change. This problem is now fixed. |
Mon. October 20, 2003 | |
6.2.20 | Fixed a problem with channel referencing a parameter of a node that is not cooked (such as an object that isn't displayed). Suppose geo1, geo2, and geo3 are all objects. geo2 is not displayed. geo2/tx is 'ch("../geo1/tx")' and geo3/tx is 'ch("../geo2/tx")'. Changing geo1/tx would not move geo3 because geo2 would not cook and so would not propagate the parameter change. This problem is now fixed. |
Mon. October 20, 2003 | |
6.2.20 | Fixed a problem with channel referencing a parameter of a node that is not cooked (such as an object that isn't displayed). Suppose geo1, geo2, and geo3 are all objects. geo2 is not displayed. geo2/tx is 'ch("../geo1/tx")' and geo3/tx is 'ch("../geo2/tx")'. Changing geo1/tx would not move geo3 because geo2 would not cook and so would not propagate the parameter change. This problem is now fixed. |
Mon. October 20, 2003 | |
6.2.20 | Fixed a problem with channel referencing a parameter of a node that is not cooked (such as an object that isn't displayed). Suppose geo1, geo2, and geo3 are all objects. geo2 is not displayed. geo2/tx is 'ch("../geo1/tx")' and geo3/tx is 'ch("../geo2/tx")'. Changing geo1/tx would not move geo3 because geo2 would not cook and so would not propagate the parameter change. This problem is now fixed. |
Mon. October 20, 2003 | |
6.2.20 | Fixed a problem with channel referencing a parameter of a node that is not cooked (such as an object that isn't displayed). Suppose geo1, geo2, and geo3 are all objects. geo2 is not displayed. geo2/tx is 'ch("../geo1/tx")' and geo3/tx is 'ch("../geo2/tx")'. Changing geo1/tx would not move geo3 because geo2 would not cook and so would not propagate the parameter change. This problem is now fixed. |
Mon. October 20, 2003 | |
6.2.20 | When a parameter uses a channel reference with th "!!ch()!!" format, the parameter is marked with a green dot in the parameter dialog. This makes it easy to detect parameters using this sort of channel reference. |
Mon. October 20, 2003 | |
6.2.20 | When a parameter uses a channel reference with th "!!ch()!!" format, the parameter is marked with a green dot in the parameter dialog. This makes it easy to detect parameters using this sort of channel reference. |
Mon. October 20, 2003 |