Houdini Main Changelogs
 |
5.1.52 | Deleting keys of locked channel segments are no longer allowed. Note that deletion of an entire locked channel is still allowed. |
Thu. March 14, 2002 |
|
5.1.52 | Deleting keys of locked channel segments are no longer allowed. Note that deletion of an entire locked channel is still allowed. |
Thu. March 14, 2002 |
|
5.1.52 | Deleting keys of locked channel segments are no longer allowed. Note that deletion of an entire locked channel is still allowed. |
Thu. March 14, 2002 |
|
5.1.52 | Deleting keys of locked channel segments are no longer allowed. Note that deletion of an entire locked channel is still allowed. |
Thu. March 14, 2002 |
 |
5.1.52 | Values for custom panels are now properly saved and loaded from the hip file. Unfortunately, the interests to execute scripts and watch operator parameter changes are not "wired-up" until a panel's UI is actually built. In addition, slider and input field initial values are currently ignored. Hitting cancel in the interactive UI builder is no longer as prohibitive as it was previously with large custom panels. |
Thu. March 14, 2002 |
|
5.1.52 | Values for custom panels are now properly saved and loaded from the hip file. Unfortunately, the interests to execute scripts and watch operator parameter changes are not "wired-up" until a panel's UI is actually built. In addition, slider and input field initial values are currently ignored. Hitting cancel in the interactive UI builder is no longer as prohibitive as it was previously with large custom panels. |
Thu. March 14, 2002 |
|
5.1.52 | Values for custom panels are now properly saved and loaded from the hip file. Unfortunately, the interests to execute scripts and watch operator parameter changes are not "wired-up" until a panel's UI is actually built. In addition, slider and input field initial values are currently ignored. Hitting cancel in the interactive UI builder is no longer as prohibitive as it was previously with large custom panels. |
Thu. March 14, 2002 |
|
5.1.52 | Values for custom panels are now properly saved and loaded from the hip file. Unfortunately, the interests to execute scripts and watch operator parameter changes are not "wired-up" until a panel's UI is actually built. In addition, slider and input field initial values are currently ignored. Hitting cancel in the interactive UI builder is no longer as prohibitive as it was previously with large custom panels. |
Thu. March 14, 2002 |
|
5.1.52 | Values for custom panels are now properly saved and loaded from the hip file. Unfortunately, the interests to execute scripts and watch operator parameter changes are not "wired-up" until a panel's UI is actually built. In addition, slider and input field initial values are currently ignored. Hitting cancel in the interactive UI builder is no longer as prohibitive as it was previously with large custom panels. |
Thu. March 14, 2002 |
 |
5.1.51 | The chls command now lists channels in ascending instead of descending order. Similarly, the Fetch CHOP now fetches channels in ascending instead of descending order. In this way, it is now consistent with the Export CHOP and if it fetched from parameters which did not have channels. |
Wed. March 13, 2002 |
|
5.1.51 | The chls command now lists channels in ascending instead of descending order. Similarly, the Fetch CHOP now fetches channels in ascending instead of descending order. In this way, it is now consistent with the Export CHOP and if it fetched from parameters which did not have channels. |
Wed. March 13, 2002 |
|
5.1.51 | The chls command now lists channels in ascending instead of descending order. Similarly, the Fetch CHOP now fetches channels in ascending instead of descending order. In this way, it is now consistent with the Export CHOP and if it fetched from parameters which did not have channels. |
Wed. March 13, 2002 |
|
5.1.51 | The chls command now lists channels in ascending instead of descending order. Similarly, the Fetch CHOP now fetches channels in ascending instead of descending order. In this way, it is now consistent with the Export CHOP and if it fetched from parameters which did not have channels. |
Wed. March 13, 2002 |
|
5.1.51 | The chls command now lists channels in ascending instead of descending order. Similarly, the Fetch CHOP now fetches channels in ascending instead of descending order. In this way, it is now consistent with the Export CHOP and if it fetched from parameters which did not have channels. |
Wed. March 13, 2002 |
 |
5.1.50 | Fixed bug where the bonefixchops command would not properly adjust affected InverseKin CHOPs if the bone chain was in an object subnet. Note that the bonefixchops command is in the delete script of bone objects by default and thus affects regular deletion of bones in IK bone chains. |
Wed. March 13, 2002 |
|
5.1.50 | Fixed bug where the bonefixchops command would not properly adjust affected InverseKin CHOPs if the bone chain was in an object subnet. Note that the bonefixchops command is in the delete script of bone objects by default and thus affects regular deletion of bones in IK bone chains. |
Wed. March 13, 2002 |
|
5.1.50 | Fixed bug where the bonefixchops command would not properly adjust affected InverseKin CHOPs if the bone chain was in an object subnet. Note that the bonefixchops command is in the delete script of bone objects by default and thus affects regular deletion of bones in IK bone chains. |
Wed. March 13, 2002 |
|
5.1.50 | Fixed bug where the bonefixchops command would not properly adjust affected InverseKin CHOPs if the bone chain was in an object subnet. Note that the bonefixchops command is in the delete script of bone objects by default and thus affects regular deletion of bones in IK bone chains. |
Wed. March 13, 2002 |
|
5.1.50 | Fixed bug where the bonefixchops command would not properly adjust affected InverseKin CHOPs if the bone chain was in an object subnet. Note that the bonefixchops command is in the delete script of bone objects by default and thus affects regular deletion of bones in IK bone chains. |
Wed. March 13, 2002 |
 |
5.1.50 | The Particle SOP no longer has the Alpha Speed parameter ("alpha"). This will cause warning about unknown channels to be generated in loading old .hip files which can be ignored as the parameter does nothing. The only caveat is if it was used as a spare channel, in which case some work must be done to recover its value. |
Tue. March 12, 2002 |
|
5.1.50 | The Particle SOP no longer has the Alpha Speed parameter ("alpha"). This will cause warning about unknown channels to be generated in loading old .hip files which can be ignored as the parameter does nothing. The only caveat is if it was used as a spare channel, in which case some work must be done to recover its value. |
Tue. March 12, 2002 |
|
5.1.50 | The Particle SOP no longer has the Alpha Speed parameter ("alpha"). This will cause warning about unknown channels to be generated in loading old .hip files which can be ignored as the parameter does nothing. The only caveat is if it was used as a spare channel, in which case some work must be done to recover its value. |
Tue. March 12, 2002 |
|
5.1.50 | The Particle SOP no longer has the Alpha Speed parameter ("alpha"). This will cause warning about unknown channels to be generated in loading old .hip files which can be ignored as the parameter does nothing. The only caveat is if it was used as a spare channel, in which case some work must be done to recover its value. |
Tue. March 12, 2002 |
|
5.1.50 | The Particle SOP no longer has the Alpha Speed parameter ("alpha"). This will cause warning about unknown channels to be generated in loading old .hip files which can be ignored as the parameter does nothing. The only caveat is if it was used as a spare channel, in which case some work must be done to recover its value. |
Tue. March 12, 2002 |
|
5.1.50 | The Alpha Speed parameter of the Particle Sop is now gone. As it did nothing before, this is to clean up the interface. |
Tue. March 12, 2002 |