Houdini Main Changelogs
 |
6.1.140 | Fixed bug where the display colour in objects could not be animated. |
Fri. September 19, 2003 |
|
6.1.140 | Fixed bug where the display colour in objects could not be animated. |
Fri. September 19, 2003 |
|
6.1.140 | Fixed bug where the display colour in objects could not be animated. |
Fri. September 19, 2003 |
 |
6.1.139 | Fixed recently introduced bug that could cause core dumps when deleting operator definitions from the Embedded OTL. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed recently introduced bug that could cause core dumps when deleting operator definitions from the Embedded OTL. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed recently introduced bug that could cause core dumps when deleting operator definitions from the Embedded OTL. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed recently introduced bug that could cause core dumps when deleting operator definitions from the Embedded OTL. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed recently introduced bug that could cause core dumps when deleting operator definitions from the Embedded OTL. |
Thu. September 18, 2003 |
 |
6.1.139 | Fixed a long-standing VOPs bug that could result in VEX code being generated from VOPs in the wrong order. This bug would appear only given the right cirumstances of input connections and ordering in the operator list view. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed a long-standing VOPs bug that could result in VEX code being generated from VOPs in the wrong order. This bug would appear only given the right cirumstances of input connections and ordering in the operator list view. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed a long-standing VOPs bug that could result in VEX code being generated from VOPs in the wrong order. This bug would appear only given the right cirumstances of input connections and ordering in the operator list view. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed a long-standing VOPs bug that could result in VEX code being generated from VOPs in the wrong order. This bug would appear only given the right cirumstances of input connections and ordering in the operator list view. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed a long-standing VOPs bug that could result in VEX code being generated from VOPs in the wrong order. This bug would appear only given the right cirumstances of input connections and ordering in the operator list view. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed recently introduced problem where the Bricks VOP would be created incorrectly. One of the subnets inside it would be wired incorrectly. This bug may have also affected other VOP scripted subnets, but has now been fixed. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed recently introduced problem where the Bricks VOP would be created incorrectly. One of the subnets inside it would be wired incorrectly. This bug may have also affected other VOP scripted subnets, but has now been fixed. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed recently introduced problem where the Bricks VOP would be created incorrectly. One of the subnets inside it would be wired incorrectly. This bug may have also affected other VOP scripted subnets, but has now been fixed. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed recently introduced problem where the Bricks VOP would be created incorrectly. One of the subnets inside it would be wired incorrectly. This bug may have also affected other VOP scripted subnets, but has now been fixed. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed recently introduced problem where the Bricks VOP would be created incorrectly. One of the subnets inside it would be wired incorrectly. This bug may have also affected other VOP scripted subnets, but has now been fixed. |
Thu. September 18, 2003 |
 |
6.1.139 | The pomset command now accepts the word "on" in upper or lower case, or any non-zero numeric value to turn on a flag. Any other value turns the flag off. This matches the behavior of the opset command. Previously only the string "on" would turn the flag on. |
Thu. September 18, 2003 |
|
6.1.139 | The pomset command now accepts the word "on" in upper or lower case, or any non-zero numeric value to turn on a flag. Any other value turns the flag off. This matches the behavior of the opset command. Previously only the string "on" would turn the flag on. |
Thu. September 18, 2003 |
|
6.1.139 | The pomset command now accepts the word "on" in upper or lower case, or any non-zero numeric value to turn on a flag. Any other value turns the flag off. This matches the behavior of the opset command. Previously only the string "on" would turn the flag on. |
Thu. September 18, 2003 |
|
6.1.139 | The pomset command now accepts the word "on" in upper or lower case, or any non-zero numeric value to turn on a flag. Any other value turns the flag off. This matches the behavior of the opset command. Previously only the string "on" would turn the flag on. |
Thu. September 18, 2003 |
|
6.1.139 | The pomset command now accepts the word "on" in upper or lower case, or any non-zero numeric value to turn on a flag. Any other value turns the flag off. This matches the behavior of the opset command. Previously only the string "on" would turn the flag on. |
Thu. September 18, 2003 |
 |
6.1.139 | Fixed a bug that caused crashes when transforming object at SOP level. |
Thu. September 18, 2003 |
|
6.1.139 | Fixed a bug that caused crashes when transforming object at SOP level. |
Thu. September 18, 2003 |