Houdini Main Changelogs
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 | |
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 | |
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 | |
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 | |
6.0.238 | When doing a File->New operation, or when loading a new hip file, persistent handle groups were not being destroyed. Now they are. |
Thu. March 13, 2003 | |
6.0.238 | When doing a File->New operation, or when loading a new hip file, persistent handle groups were not being destroyed. Now they are. |
Thu. March 13, 2003 | |
6.0.238 | When doing a File->New operation, or when loading a new hip file, persistent handle groups were not being destroyed. Now they are. |
Thu. March 13, 2003 | |
6.0.238 | When doing a File->New operation, or when loading a new hip file, persistent handle groups were not being destroyed. Now they are. |
Thu. March 13, 2003 | |
6.0.238 | When doing a File->New operation, or when loading a new hip file, persistent handle groups were not being destroyed. Now they are. |
Thu. March 13, 2003 | |
6.0.238 | The Edit Contents dialog would sometimes erroneously report that a section had been changed even when it had not been changed. This problem would occur under Windows because of carriage return characters not being handled properly. |
Thu. March 13, 2003 | |
6.0.238 | The Edit Contents dialog would sometimes erroneously report that a section had been changed even when it had not been changed. This problem would occur under Windows because of carriage return characters not being handled properly. |
Thu. March 13, 2003 | |
6.0.238 | The Edit Contents dialog would sometimes erroneously report that a section had been changed even when it had not been changed. This problem would occur under Windows because of carriage return characters not being handled properly. |
Thu. March 13, 2003 | |
6.0.238 | The Edit Contents dialog would sometimes erroneously report that a section had been changed even when it had not been changed. This problem would occur under Windows because of carriage return characters not being handled properly. |
Thu. March 13, 2003 | |
6.0.238 | The Edit Contents dialog would sometimes erroneously report that a section had been changed even when it had not been changed. This problem would occur under Windows because of carriage return characters not being handled properly. |
Thu. March 13, 2003 | |
6.0.238 | It is now possible to set the input labels for VEX operators and custom subnet operators. This is done on the Input/Output page of the Type Properties dialog. |
Thu. March 13, 2003 | |
6.0.238 | It is now possible to set the input labels for VEX operators and custom subnet operators. This is done on the Input/Output page of the Type Properties dialog. |
Thu. March 13, 2003 | |
6.0.238 | It is now possible to set the input labels for VEX operators and custom subnet operators. This is done on the Input/Output page of the Type Properties dialog. |
Thu. March 13, 2003 | |
6.0.238 | It is now possible to set the input labels for VEX operators and custom subnet operators. This is done on the Input/Output page of the Type Properties dialog. |
Thu. March 13, 2003 | |
6.0.238 | It is now possible to set the input labels for VEX operators and custom subnet operators. This is done on the Input/Output page of the Type Properties dialog. |
Thu. March 13, 2003 | |
6.0.237 | The interface to the function HoudiniFindFile() was changed. Please see the header file for the new signature. |
Wed. March 12, 2003 | |
6.0.237 | The interface to the function HoudiniFindFile() was changed. Please see the header file for the new signature. |
Wed. March 12, 2003 | |
6.0.237 | The interface to the function HoudiniFindFile() was changed. Please see the header file for the new signature. |
Wed. March 12, 2003 | |
6.0.237 | The interface to the function HoudiniFindFile() was changed. Please see the header file for the new signature. |
Wed. March 12, 2003 | |
6.0.237 | The interface to the function HoudiniFindFile() was changed. Please see the header file for the new signature. |
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 |