Houdini Main Changelogs
 |
6.0.204 | The see one/see all button has now been enabled at the OBJ level, allowing you to filter the display of objects at the object subnet level. Either click on the button directly or bring up the CTRL+RMB menu in the view state (or press 'e'). |
Fri. February 7, 2003 |
|
6.0.204 | The see one/see all button has now been enabled at the OBJ level, allowing you to filter the display of objects at the object subnet level. Either click on the button directly or bring up the CTRL+RMB menu in the view state (or press 'e'). |
Fri. February 7, 2003 |
|
6.0.204 | The see one/see all button has now been enabled at the OBJ level, allowing you to filter the display of objects at the object subnet level. Either click on the button directly or bring up the CTRL+RMB menu in the view state (or press 'e'). |
Fri. February 7, 2003 |
 |
6.0.204 | Added two new parameters to the Collision POP to control the terminate behaviour of bouncing particles. When the impulse of the collision falls below the minimum value, particles can either stop, slide, or stick. |
Fri. February 7, 2003 |
|
6.0.204 | Added two new parameters to the Collision POP to control the terminate behaviour of bouncing particles. When the impulse of the collision falls below the minimum value, particles can either stop, slide, or stick. |
Fri. February 7, 2003 |
|
6.0.204 | Added two new parameters to the Collision POP to control the terminate behaviour of bouncing particles. When the impulse of the collision falls below the minimum value, particles can either stop, slide, or stick. |
Fri. February 7, 2003 |
|
6.0.204 | Added two new parameters to the Collision POP to control the terminate behaviour of bouncing particles. When the impulse of the collision falls below the minimum value, particles can either stop, slide, or stick. |
Fri. February 7, 2003 |
|
6.0.204 | Added two new parameters to the Collision POP to control the terminate behaviour of bouncing particles. When the impulse of the collision falls below the minimum value, particles can either stop, slide, or stick. |
Fri. February 7, 2003 |
 |
6.0.204 | There is a new VEX function to intersect a ray against a 3d texture map. Please see the VEX documentation for more details. |
Fri. February 7, 2003 |
|
6.0.204 | There is a new VEX function to intersect a ray against a 3d texture map. Please see the VEX documentation for more details. |
Fri. February 7, 2003 |
|
6.0.204 | There is a new VEX function to intersect a ray against a 3d texture map. Please see the VEX documentation for more details. |
Fri. February 7, 2003 |
|
6.0.204 | There is a new VEX function to intersect a ray against a 3d texture map. Please see the VEX documentation for more details. |
Fri. February 7, 2003 |
|
6.0.204 | There is a new VEX function to intersect a ray against a 3d texture map. Please see the VEX documentation for more details. |
Fri. February 7, 2003 |
 |
6.0.204 | The CHOP PreTransform, when set to the "Object and Channel" channel name mode, will name the channels the absolute path, ie /obj/model/tx, rather than model/tx. This can be undone with a rename CHOP, or ignored, as /obj/model/tx will do the expected overrides. |
Fri. February 7, 2003 |
|
6.0.204 | The CHOP PreTransform, when set to the "Object and Channel" channel name mode, will name the channels the absolute path, ie /obj/model/tx, rather than model/tx. This can be undone with a rename CHOP, or ignored, as /obj/model/tx will do the expected overrides. |
Fri. February 7, 2003 |
|
6.0.204 | The CHOP PreTransform, when set to the "Object and Channel" channel name mode, will name the channels the absolute path, ie /obj/model/tx, rather than model/tx. This can be undone with a rename CHOP, or ignored, as /obj/model/tx will do the expected overrides. |
Fri. February 7, 2003 |
|
6.0.204 | The CHOP PreTransform, when set to the "Object and Channel" channel name mode, will name the channels the absolute path, ie /obj/model/tx, rather than model/tx. This can be undone with a rename CHOP, or ignored, as /obj/model/tx will do the expected overrides. |
Fri. February 7, 2003 |
|
6.0.204 | The CHOP PreTransform, when set to the "Object and Channel" channel name mode, will name the channels the absolute path, ie /obj/model/tx, rather than model/tx. This can be undone with a rename CHOP, or ignored, as /obj/model/tx will do the expected overrides. |
Fri. February 7, 2003 |
 |
6.0.204 | Fixed a bug where Parameter VOPs inside subnets would not have their proper pragmas output to the VFL code. This resulted in badly defined parameters when a VOPNET was used to "Create Context Operator Type". Also, we now generate our VFL code such that the parameters in the operator type resulting from this operation match the order of the parameters specified in the VOPNET. |
Fri. February 7, 2003 |
|
6.0.204 | Fixed a bug where Parameter VOPs inside subnets would not have their proper pragmas output to the VFL code. This resulted in badly defined parameters when a VOPNET was used to "Create Context Operator Type". Also, we now generate our VFL code such that the parameters in the operator type resulting from this operation match the order of the parameters specified in the VOPNET. |
Fri. February 7, 2003 |
|
6.0.204 | Fixed a bug where Parameter VOPs inside subnets would not have their proper pragmas output to the VFL code. This resulted in badly defined parameters when a VOPNET was used to "Create Context Operator Type". Also, we now generate our VFL code such that the parameters in the operator type resulting from this operation match the order of the parameters specified in the VOPNET. |
Fri. February 7, 2003 |
|
6.0.204 | Fixed a bug where Parameter VOPs inside subnets would not have their proper pragmas output to the VFL code. This resulted in badly defined parameters when a VOPNET was used to "Create Context Operator Type". Also, we now generate our VFL code such that the parameters in the operator type resulting from this operation match the order of the parameters specified in the VOPNET. |
Fri. February 7, 2003 |
|
6.0.204 | Fixed a bug where Parameter VOPs inside subnets would not have their proper pragmas output to the VFL code. This resulted in badly defined parameters when a VOPNET was used to "Create Context Operator Type". Also, we now generate our VFL code such that the parameters in the operator type resulting from this operation match the order of the parameters specified in the VOPNET. |
Fri. February 7, 2003 |
|
6.0.204 | Fixed a bug where connections to the inputs of Parameter VOPs could be lost when a hip file was reloaded. |
Fri. February 7, 2003 |
|
6.0.204 | Fixed a bug where connections to the inputs of Parameter VOPs could be lost when a hip file was reloaded. |
Fri. February 7, 2003 |