Houdini Main Changelogs
7.0.108 | The clamp VOP now handles vector4 properly. |
Thu. June 24, 2004 | |
7.0.108 | The clamp VOP now handles vector4 properly. |
Thu. June 24, 2004 | |
7.0.108 | The clamp VOP now handles vector4 properly. |
Thu. June 24, 2004 | |
7.0.108 | Fixed bug where hold down space bar in network pane and clicking (without dragging) brings up toolbar and network pane becomes stuck in view state. |
Thu. June 24, 2004 | |
7.0.108 | Fixed bug where hold down space bar in network pane and clicking (without dragging) brings up toolbar and network pane becomes stuck in view state. |
Thu. June 24, 2004 | |
7.0.108 | Fixed bug where hold down space bar in network pane and clicking (without dragging) brings up toolbar and network pane becomes stuck in view state. |
Thu. June 24, 2004 | |
7.0.108 | Fixed bug where hold down space bar in network pane and clicking (without dragging) brings up toolbar and network pane becomes stuck in view state. |
Thu. June 24, 2004 | |
7.0.108 | Fixed bug where hold down space bar in network pane and clicking (without dragging) brings up toolbar and network pane becomes stuck in view state. |
Thu. June 24, 2004 | |
7.0.108 | Fixed bug where when loading custom panel files from a hip file that already existed on disk, the custom panel gadget values would be set into the wrong panel. |
Thu. June 24, 2004 | |
7.0.108 | Fixed bug where when loading custom panel files from a hip file that already existed on disk, the custom panel gadget values would be set into the wrong panel. |
Thu. June 24, 2004 | |
7.0.108 | Fixed bug where when loading custom panel files from a hip file that already existed on disk, the custom panel gadget values would be set into the wrong panel. |
Thu. June 24, 2004 | |
7.0.108 | Fixed bug where when loading custom panel files from a hip file that already existed on disk, the custom panel gadget values would be set into the wrong panel. |
Thu. June 24, 2004 | |
7.0.108 | Fixed bug where when loading custom panel files from a hip file that already existed on disk, the custom panel gadget values would be set into the wrong panel. |
Thu. June 24, 2004 | |
7.0.108 | The VEX pow() function now correctly works on vector4 types (as stated in the documentation). |
Thu. June 24, 2004 | |
7.0.108 | The VEX pow() function now correctly works on vector4 types (as stated in the documentation). |
Thu. June 24, 2004 | |
7.0.108 | The VEX pow() function now correctly works on vector4 types (as stated in the documentation). |
Thu. June 24, 2004 | |
7.0.108 | The VEX pow() function now correctly works on vector4 types (as stated in the documentation). |
Thu. June 24, 2004 | |
7.0.108 | The VEX pow() function now correctly works on vector4 types (as stated in the documentation). |
Thu. June 24, 2004 | |
7.0.107 | When writing VEX plug-ins, it's now possible to force the plug-in function to have a return code, even if it modifies multiple arguments. Due to this change, all VEX plug-ins will have to be re-created, regardless of whether they use the HDK libraries or not. |
Wed. June 23, 2004 | |
7.0.107 | When writing VEX plug-ins, it's now possible to force the plug-in function to have a return code, even if it modifies multiple arguments. Due to this change, all VEX plug-ins will have to be re-created, regardless of whether they use the HDK libraries or not. |
Wed. June 23, 2004 | |
7.0.107 | When writing VEX plug-ins, it's now possible to force the plug-in function to have a return code, even if it modifies multiple arguments. Due to this change, all VEX plug-ins will have to be re-created, regardless of whether they use the HDK libraries or not. |
Wed. June 23, 2004 | |
7.0.107 | When writing VEX plug-ins, it's now possible to force the plug-in function to have a return code, even if it modifies multiple arguments. Due to this change, all VEX plug-ins will have to be re-created, regardless of whether they use the HDK libraries or not. |
Wed. June 23, 2004 | |
7.0.107 | When writing VEX plug-ins, it's now possible to force the plug-in function to have a return code, even if it modifies multiple arguments. Due to this change, all VEX plug-ins will have to be re-created, regardless of whether they use the HDK libraries or not. |
Wed. June 23, 2004 | |
7.0.107 | RIB generation has been generalized in Houdini. There is now a file ($HH/ROPfeatures) which specifies the list of renderers supported by Houdini. Each renderer has a list of features which it supports. The file not only allows new renderers to be added to Houdini, but also allows for customization of RIB feature sets. For example, it has been noted that by just specifying the "trace" attributes for prman11, the geometry is persistent and impacts the memory footprint of the render. We include prman11.0-rt which turns off ray-tracing in prman11, but still supports all the other prman11 feature set. There is further documentation in the ROPfeatures file. |
Wed. June 23, 2004 | |
7.0.107 | RIB generation has been generalized in Houdini. There is now a file ($HH/ROPfeatures) which specifies the list of renderers supported by Houdini. Each renderer has a list of features which it supports. The file not only allows new renderers to be added to Houdini, but also allows for customization of RIB feature sets. For example, it has been noted that by just specifying the "trace" attributes for prman11, the geometry is persistent and impacts the memory footprint of the render. We include prman11.0-rt which turns off ray-tracing in prman11, but still supports all the other prman11 feature set. There is further documentation in the ROPfeatures file. |
Wed. June 23, 2004 |