Houdini Main Changelogs
6.0.237 | Fixed bug where entering 0...3 or 2..3..4 in a numeric parameter results it in being accepted. However, it was unclear as to what the actual interpretation was. We now properly flag this as an expression which evaluates with errors. |
Wed. March 12, 2003 | |
6.0.237 | Fixed bug where entering 0...3 or 2..3..4 in a numeric parameter results it in being accepted. However, it was unclear as to what the actual interpretation was. We now properly flag this as an expression which evaluates with errors. |
Wed. March 12, 2003 | |
6.0.237 | Fixed bug where entering 0...3 or 2..3..4 in a numeric parameter results it in being accepted. However, it was unclear as to what the actual interpretation was. We now properly flag this as an expression which evaluates with errors. |
Wed. March 12, 2003 | |
6.0.237 | Fixed bug where entering 0...3 or 2..3..4 in a numeric parameter results it in being accepted. However, it was unclear as to what the actual interpretation was. We now properly flag this as an expression which evaluates with errors. |
Wed. March 12, 2003 | |
6.0.237 | Fixed Halo crashes that would happen if the raster failed to allocate for some reason. It now produces and error with an informative message. |
Wed. March 12, 2003 | |
6.0.237 | Fixed Halo crashes that would happen if the raster failed to allocate for some reason. It now produces and error with an informative message. |
Wed. March 12, 2003 | |
6.0.237 | Fixed Halo crashes that would happen if the raster failed to allocate for some reason. It now produces and error with an informative message. |
Wed. March 12, 2003 | |
6.0.237 | Fixed Halo crashes that would happen if the raster failed to allocate for some reason. It now produces and error with an informative message. |
Wed. March 12, 2003 | |
6.0.237 | Fixed Halo crashes that would happen if the raster failed to allocate for some reason. It now produces and error with an informative message. |
Wed. March 12, 2003 | |
6.0.237 | Composable transforms do not work correctly if the input has a different resolution from the current node. This case was quite common with a transform or a scale on the foreground input to a composite or layer. In this case, we disable the composing of transforms. |
Wed. March 12, 2003 | |
6.0.237 | Composable transforms do not work correctly if the input has a different resolution from the current node. This case was quite common with a transform or a scale on the foreground input to a composite or layer. In this case, we disable the composing of transforms. |
Wed. March 12, 2003 | |
6.0.237 | Composable transforms do not work correctly if the input has a different resolution from the current node. This case was quite common with a transform or a scale on the foreground input to a composite or layer. In this case, we disable the composing of transforms. |
Wed. March 12, 2003 | |
6.0.237 | Composable transforms do not work correctly if the input has a different resolution from the current node. This case was quite common with a transform or a scale on the foreground input to a composite or layer. In this case, we disable the composing of transforms. |
Wed. March 12, 2003 | |
6.0.237 | Composable transforms do not work correctly if the input has a different resolution from the current node. This case was quite common with a transform or a scale on the foreground input to a composite or layer. In this case, we disable the composing of transforms. |
Wed. March 12, 2003 | |
6.0.237 | In the Visible Object and Active Lights parameters of render operators, specifying the name of an object subnet automatically includes all children of that subnet. |
Wed. March 12, 2003 | |
6.0.237 | In the Visible Object and Active Lights parameters of render operators, specifying the name of an object subnet automatically includes all children of that subnet. |
Wed. March 12, 2003 | |
6.0.237 | In the Visible Object and Active Lights parameters of render operators, specifying the name of an object subnet automatically includes all children of that subnet. |
Wed. March 12, 2003 | |
6.0.237 | In the Visible Object and Active Lights parameters of render operators, specifying the name of an object subnet automatically includes all children of that subnet. |
Wed. March 12, 2003 | |
6.0.237 | In the Visible Object and Active Lights parameters of render operators, specifying the name of an object subnet automatically includes all children of that subnet. |
Wed. March 12, 2003 | |
6.0.237 | Fixing a bug where Houdini can't read directory listings on very large Linux file systems. |
Wed. March 12, 2003 | |
6.0.237 | Fixing a bug where Houdini can't read directory listings on very large Linux file systems. |
Wed. March 12, 2003 | |
6.0.237 | Fixing a bug where Houdini can't read directory listings on very large Linux file systems. |
Wed. March 12, 2003 | |
6.0.237 | Fixing a bug where Houdini can't read directory listings on very large Linux file systems. |
Wed. March 12, 2003 | |
6.0.237 | Fixing a bug where Houdini can't read directory listings on very large Linux file systems. |
Wed. March 12, 2003 | |
6.0.237 | Fixed bug where the proxy resolution was accounted for twice in the transform/composite/layer cops when the pivot had an expression such as 0.5*$W, 0.5*$H. |
Wed. March 12, 2003 |