Houdini Main Changelogs
6.0.238 | Fixed crash in Halo that could occur if trying to composite from a File COP which read in a corrupt image file. |
Thu. March 13, 2003 | |
6.0.238 | Fixed crash in Halo that could occur if trying to composite from a File COP which read in a corrupt image file. |
Thu. March 13, 2003 | |
6.0.238 | Fixed crash in Halo that could occur if trying to composite from a File COP which read in a corrupt image file. |
Thu. March 13, 2003 | |
6.0.238 | Fixed crash in Halo that could occur if trying to composite from a File COP which read in a corrupt image file. |
Thu. March 13, 2003 | |
6.0.238 | In the network editor pane for a subnet type operator, the look of the parent input gadgets has been improved. They now display the input label associated with the corresponding input of the subnet, as well as the name of the node currently connected to that input. |
Thu. March 13, 2003 | |
6.0.238 | In the network editor pane for a subnet type operator, the look of the parent input gadgets has been improved. They now display the input label associated with the corresponding input of the subnet, as well as the name of the node currently connected to that input. |
Thu. March 13, 2003 | |
6.0.238 | In the network editor pane for a subnet type operator, the look of the parent input gadgets has been improved. They now display the input label associated with the corresponding input of the subnet, as well as the name of the node currently connected to that input. |
Thu. March 13, 2003 | |
6.0.238 | In the network editor pane for a subnet type operator, the look of the parent input gadgets has been improved. They now display the input label associated with the corresponding input of the subnet, as well as the name of the node currently connected to that input. |
Thu. March 13, 2003 | |
6.0.238 | In the network editor pane for a subnet type operator, the look of the parent input gadgets has been improved. They now display the input label associated with the corresponding input of the subnet, as well as the name of the node currently connected to that input. |
Thu. March 13, 2003 | |
6.0.238 | This COP2 cache now works properly with cache sizes over 4 gigabytes on systems that support this. |
Thu. March 13, 2003 | |
6.0.238 | This COP2 cache now works properly with cache sizes over 4 gigabytes on systems that support this. |
Thu. March 13, 2003 | |
6.0.238 | This COP2 cache now works properly with cache sizes over 4 gigabytes on systems that support this. |
Thu. March 13, 2003 | |
6.0.238 | This COP2 cache now works properly with cache sizes over 4 gigabytes on systems that support this. |
Thu. March 13, 2003 | |
6.0.238 | This COP2 cache now works properly with cache sizes over 4 gigabytes on systems that support this. |
Thu. March 13, 2003 | |
6.0.238 | Optimized the premultiply COP for the 8 and 16 bit cases. Performance has improved from 2-4x. |
Thu. March 13, 2003 | |
6.0.238 | Optimized the premultiply COP for the 8 and 16 bit cases. Performance has improved from 2-4x. |
Thu. March 13, 2003 | |
6.0.238 | Optimized the premultiply COP for the 8 and 16 bit cases. Performance has improved from 2-4x. |
Thu. March 13, 2003 | |
6.0.238 | Optimized the premultiply COP for the 8 and 16 bit cases. Performance has improved from 2-4x. |
Thu. March 13, 2003 | |
6.0.238 | Optimized the premultiply COP for the 8 and 16 bit cases. Performance has improved from 2-4x. |
Thu. March 13, 2003 | |
6.0.238 | The Edit VEX Function button available on VEX operators (such as the Gradient COP or Mountain SOP) now brings up a Type Properties dialog if the operator is defined in an OTL. Otherwise it still tries to locate the VEX source code on disk and open a text editor on that file. |
Thu. March 13, 2003 | |
6.0.238 | The Edit VEX Function button available on VEX operators (such as the Gradient COP or Mountain SOP) now brings up a Type Properties dialog if the operator is defined in an OTL. Otherwise it still tries to locate the VEX source code on disk and open a text editor on that file. |
Thu. March 13, 2003 | |
6.0.238 | The Edit VEX Function button available on VEX operators (such as the Gradient COP or Mountain SOP) now brings up a Type Properties dialog if the operator is defined in an OTL. Otherwise it still tries to locate the VEX source code on disk and open a text editor on that file. |
Thu. March 13, 2003 | |
6.0.238 | The Edit VEX Function button available on VEX operators (such as the Gradient COP or Mountain SOP) now brings up a Type Properties dialog if the operator is defined in an OTL. Otherwise it still tries to locate the VEX source code on disk and open a text editor on that file. |
Thu. March 13, 2003 | |
6.0.238 | The Edit VEX Function button available on VEX operators (such as the Gradient COP or Mountain SOP) now brings up a Type Properties dialog if the operator is defined in an OTL. Otherwise it still tries to locate the VEX source code on disk and open a text editor on that file. |
Thu. March 13, 2003 | |
6.0.238 | Fixed a bug with some RenderMan SHOPs incorrectly reporting their shader names in the Type Properties dialog. The shader name would appear as "opdef:/Shop/ri_constant" for example, where the correct value would be "constant". |
Thu. March 13, 2003 |