Houdini Main Changelogs
8.0.253 | In the RenderMan ROP, we now output AttributeBegin/AttributeEnd pairs in the RIB stream around shading groups which have a matching RIB hack. The format is: AttributeBegin # { <attrib_name> <attrib_value> AttributeEnd # } <attrib_name> <attrib_value> Note that if <attrib_value> contains spaces, then it will be appropriately double quoted and escaped as necessary. This has two advantages: 1. If the RIB hack outputs attribute values such as motionfactor, they will only affect the shading group around which the RIB hack was executed. 2. This allows easy RIB filtering to discard specific shading groups. |
Thu. May 26, 2005 | |
8.0.253 | In the RenderMan ROP, we now output AttributeBegin/AttributeEnd pairs in the RIB stream around shading groups which have a matching RIB hack. The format is: AttributeBegin # { <attrib_name> <attrib_value> AttributeEnd # } <attrib_name> <attrib_value> Note that if <attrib_value> contains spaces, then it will be appropriately double quoted and escaped as necessary. This has two advantages: 1. If the RIB hack outputs attribute values such as motionfactor, they will only affect the shading group around which the RIB hack was executed. 2. This allows easy RIB filtering to discard specific shading groups. |
Thu. May 26, 2005 | |
8.0.253 | In the RenderMan ROP, we now output AttributeBegin/AttributeEnd pairs in the RIB stream around shading groups which have a matching RIB hack. The format is: AttributeBegin # { <attrib_name> <attrib_value> AttributeEnd # } <attrib_name> <attrib_value> Note that if <attrib_value> contains spaces, then it will be appropriately double quoted and escaped as necessary. This has two advantages: 1. If the RIB hack outputs attribute values such as motionfactor, they will only affect the shading group around which the RIB hack was executed. 2. This allows easy RIB filtering to discard specific shading groups. |
Thu. May 26, 2005 | |
8.0.252 | The Visibility SOP now has the option to set visibility in all viewports at once. The selector toolbox also has three new options to quickly hide or expose selections in all viewports. |
Wed. May 25, 2005 | |
8.0.252 | The Visibility SOP now has the option to set visibility in all viewports at once. The selector toolbox also has three new options to quickly hide or expose selections in all viewports. |
Wed. May 25, 2005 | |
8.0.252 | The Visibility SOP now has the option to set visibility in all viewports at once. The selector toolbox also has three new options to quickly hide or expose selections in all viewports. |
Wed. May 25, 2005 | |
8.0.252 | The Visibility SOP now has the option to set visibility in all viewports at once. The selector toolbox also has three new options to quickly hide or expose selections in all viewports. |
Wed. May 25, 2005 | |
8.0.252 | The Visibility SOP now has the option to set visibility in all viewports at once. The selector toolbox also has three new options to quickly hide or expose selections in all viewports. |
Wed. May 25, 2005 | |
8.0.252 | The Link Editor can now export the current node in the source tree as the view camera to any linked viewers. |
Wed. May 25, 2005 | |
8.0.252 | The Link Editor can now export the current node in the source tree as the view camera to any linked viewers. |
Wed. May 25, 2005 | |
8.0.252 | The Link Editor can now export the current node in the source tree as the view camera to any linked viewers. |
Wed. May 25, 2005 | |
8.0.252 | The Link Editor can now export the current node in the source tree as the view camera to any linked viewers. |
Wed. May 25, 2005 | |
8.0.252 | The Link Editor can now export the current node in the source tree as the view camera to any linked viewers. |
Wed. May 25, 2005 | |
8.0.252 | The previously removed optimization for renaming nodes has been reinstated without breaking the Joint handle. |
Wed. May 25, 2005 | |
8.0.252 | The previously removed optimization for renaming nodes has been reinstated without breaking the Joint handle. |
Wed. May 25, 2005 | |
8.0.252 | The previously removed optimization for renaming nodes has been reinstated without breaking the Joint handle. |
Wed. May 25, 2005 | |
8.0.252 | The previously removed optimization for renaming nodes has been reinstated without breaking the Joint handle. |
Wed. May 25, 2005 | |
8.0.252 | The previously removed optimization for renaming nodes has been reinstated without breaking the Joint handle. |
Wed. May 25, 2005 | |
8.0.252 | Rather than doing collision dectection internally, RBD Solver now expects an external Collider. |
Wed. May 25, 2005 | |
8.0.252 | Rather than doing collision dectection internally, RBD Solver now expects an external Collider. |
Wed. May 25, 2005 | |
8.0.252 | Rather than doing collision dectection internally, RBD Solver now expects an external Collider. |
Wed. May 25, 2005 | |
8.0.252 | Rather than doing collision dectection internally, RBD Solver now expects an external Collider. |
Wed. May 25, 2005 | |
8.0.252 | Rather than doing collision dectection internally, RBD Solver now expects an external Collider. |
Wed. May 25, 2005 | |
8.0.251 | Previous optimization to renaming nodes accidentally broke the updating of bones in the joint handle. The optimization has now been removed. |
Tue. May 24, 2005 | |
8.0.251 | Previous optimization to renaming nodes accidentally broke the updating of bones in the joint handle. The optimization has now been removed. |
Tue. May 24, 2005 |