Houdini Main Changelogs
 |
6.2.145 | The matrix*vector operator has been removed. Formerly, this operator did the exact same thing as the vector*matrix operator, a row vector multiply. However, this is mathematically incorrect and unintuitive. Existing HDK code should probably be changed to perform a vector*matrix multiply, unless a matrix*vector multiply was actually desired, in which case the colVecMult(matrix,vector) method should be used. |
Wed. February 25, 2004 |
|
6.2.145 | The matrix*vector operator has been removed. Formerly, this operator did the exact same thing as the vector*matrix operator, a row vector multiply. However, this is mathematically incorrect and unintuitive. Existing HDK code should probably be changed to perform a vector*matrix multiply, unless a matrix*vector multiply was actually desired, in which case the colVecMult(matrix,vector) method should be used. |
Wed. February 25, 2004 |
|
6.2.145 | The matrix*vector operator has been removed. Formerly, this operator did the exact same thing as the vector*matrix operator, a row vector multiply. However, this is mathematically incorrect and unintuitive. Existing HDK code should probably be changed to perform a vector*matrix multiply, unless a matrix*vector multiply was actually desired, in which case the colVecMult(matrix,vector) method should be used. |
Wed. February 25, 2004 |
 |
6.2.146 | The Object Merge SOP will now instance its input provided it is merging from one specific SOP and has no transform object. |
Wed. February 25, 2004 |
|
6.2.146 | The Object Merge SOP will now instance its input provided it is merging from one specific SOP and has no transform object. |
Wed. February 25, 2004 |
|
6.2.146 | The Object Merge SOP will now instance its input provided it is merging from one specific SOP and has no transform object. |
Wed. February 25, 2004 |
|
6.2.146 | The Object Merge SOP will now instance its input provided it is merging from one specific SOP and has no transform object. |
Wed. February 25, 2004 |
|
6.2.146 | The Object Merge SOP will now instance its input provided it is merging from one specific SOP and has no transform object. |
Wed. February 25, 2004 |
|
6.2.146 | Fixing a bug in the UVProject SOP where it would trigger an assert about accessing an array out of bounds, though it was only out of bounds based on the entry count, not the array size. |
Wed. February 25, 2004 |
|
6.2.146 | Fixing a bug in the UVProject SOP where it would trigger an assert about accessing an array out of bounds, though it was only out of bounds based on the entry count, not the array size. |
Wed. February 25, 2004 |
|
6.2.146 | Fixing a bug in the UVProject SOP where it would trigger an assert about accessing an array out of bounds, though it was only out of bounds based on the entry count, not the array size. |
Wed. February 25, 2004 |
|
6.2.146 | Fixing a bug in the UVProject SOP where it would trigger an assert about accessing an array out of bounds, though it was only out of bounds based on the entry count, not the array size. |
Wed. February 25, 2004 |
|
6.2.146 | Fixing a bug in the UVProject SOP where it would trigger an assert about accessing an array out of bounds, though it was only out of bounds based on the entry count, not the array size. |
Wed. February 25, 2004 |
 |
6.2.145 | Added the -S option to opget. |
Tue. February 24, 2004 |
|
6.2.145 | Added the -S option to opget. |
Tue. February 24, 2004 |
|
6.2.145 | Added the -S option to opget. |
Tue. February 24, 2004 |
|
6.2.145 | Added the -S option to opget. |
Tue. February 24, 2004 |
|
6.2.145 | Added the -S option to opget. |
Tue. February 24, 2004 |
|
6.2.145 | The PRMincRange range defined in PRM/PRM_Shared now has the range 1 to [20] instead of 2 to [20]. HDK OPs that used this range should either switch to an internal range of 2 to [20] or change their code to allow the 1 case. |
Tue. February 24, 2004 |
|
6.2.145 | The PRMincRange range defined in PRM/PRM_Shared now has the range 1 to [20] instead of 2 to [20]. HDK OPs that used this range should either switch to an internal range of 2 to [20] or change their code to allow the 1 case. |
Tue. February 24, 2004 |
|
6.2.145 | The PRMincRange range defined in PRM/PRM_Shared now has the range 1 to [20] instead of 2 to [20]. HDK OPs that used this range should either switch to an internal range of 2 to [20] or change their code to allow the 1 case. |
Tue. February 24, 2004 |
|
6.2.145 | The PRMincRange range defined in PRM/PRM_Shared now has the range 1 to [20] instead of 2 to [20]. HDK OPs that used this range should either switch to an internal range of 2 to [20] or change their code to allow the 1 case. |
Tue. February 24, 2004 |
|
6.2.145 | The PRMincRange range defined in PRM/PRM_Shared now has the range 1 to [20] instead of 2 to [20]. HDK OPs that used this range should either switch to an internal range of 2 to [20] or change their code to allow the 1 case. |
Tue. February 24, 2004 |
|
6.2.145 | The Add, Align, Bridge, Skin, Fillet, Join, and Stitch SOPs all now allow a value of 1 for the N parameter. Previously they clamped the value of N at 2, now they do so at 1. Expressions that relied on this clamping will no longer work, however, it is more likely that the expressions did not expect the clamping. |
Tue. February 24, 2004 |
|
6.2.145 | The Add, Align, Bridge, Skin, Fillet, Join, and Stitch SOPs all now allow a value of 1 for the N parameter. Previously they clamped the value of N at 2, now they do so at 1. Expressions that relied on this clamping will no longer work, however, it is more likely that the expressions did not expect the clamping. |
Tue. February 24, 2004 |