Houdini Main Changelogs
 |
5.1.60 | All of the SOPs which handle local variables (such as Point, Transform, etc) now cache their previous local variable table. This removes a significant constant-time overhead from these operators if the incoming geometry has the same types of attributes from cook to cook. |
Fri. March 22, 2002 |
|
5.1.60 | All of the SOPs which handle local variables (such as Point, Transform, etc) now cache their previous local variable table. This removes a significant constant-time overhead from these operators if the incoming geometry has the same types of attributes from cook to cook. |
Fri. March 22, 2002 |
 |
5.1.60 | Houdini Difference from 4.1: The PolyReduce operator is less willing to create degenerate polygons in versions 5.0 and later. As a result, the point/polygon orders out of a polyreduce operator may change between the versions. There is no work around. |
Fri. March 22, 2002 |
|
5.1.60 | Houdini Difference from 4.1: The PolyReduce operator is less willing to create degenerate polygons in versions 5.0 and later. As a result, the point/polygon orders out of a polyreduce operator may change between the versions. There is no work around. |
Fri. March 22, 2002 |
|
5.1.60 | Houdini Difference from 4.1: The PolyReduce operator is less willing to create degenerate polygons in versions 5.0 and later. As a result, the point/polygon orders out of a polyreduce operator may change between the versions. There is no work around. |
Fri. March 22, 2002 |
|
5.1.60 | Houdini Difference from 4.1: The PolyReduce operator is less willing to create degenerate polygons in versions 5.0 and later. As a result, the point/polygon orders out of a polyreduce operator may change between the versions. There is no work around. |
Fri. March 22, 2002 |
|
5.1.60 | Houdini Difference from 4.1: The PolyReduce operator is less willing to create degenerate polygons in versions 5.0 and later. As a result, the point/polygon orders out of a polyreduce operator may change between the versions. There is no work around. |
Fri. March 22, 2002 |
|
5.1.60 | SHOPs no longer recook everytime an object is displayed, instead only cooking when their own parameters have changed. |
Fri. March 22, 2002 |
|
5.1.60 | SHOPs no longer recook everytime an object is displayed, instead only cooking when their own parameters have changed. |
Fri. March 22, 2002 |
|
5.1.60 | SHOPs no longer recook everytime an object is displayed, instead only cooking when their own parameters have changed. |
Fri. March 22, 2002 |
|
5.1.60 | SHOPs no longer recook everytime an object is displayed, instead only cooking when their own parameters have changed. |
Fri. March 22, 2002 |
|
5.1.60 | SHOPs no longer recook everytime an object is displayed, instead only cooking when their own parameters have changed. |
Fri. March 22, 2002 |
|
5.1.60 | The Cache SOP now has a default increment of one so it can be used intuitively to speed up the playback of animating SOPs. |
Fri. March 22, 2002 |
|
5.1.60 | The Cache SOP now has a default increment of one so it can be used intuitively to speed up the playback of animating SOPs. |
Fri. March 22, 2002 |
|
5.1.60 | The Cache SOP now has a default increment of one so it can be used intuitively to speed up the playback of animating SOPs. |
Fri. March 22, 2002 |
|
5.1.60 | The Cache SOP now has a default increment of one so it can be used intuitively to speed up the playback of animating SOPs. |
Fri. March 22, 2002 |
|
5.1.60 | The Cache SOP now has a default increment of one so it can be used intuitively to speed up the playback of animating SOPs. |
Fri. March 22, 2002 |
|
5.1.60 | The default cache increment is now 1 rather than 10. This may affect old scripts that relied on the previous default. |
Fri. March 22, 2002 |
|
5.1.60 | The default cache increment is now 1 rather than 10. This may affect old scripts that relied on the previous default. |
Fri. March 22, 2002 |
|
5.1.60 | The default cache increment is now 1 rather than 10. This may affect old scripts that relied on the previous default. |
Fri. March 22, 2002 |
|
5.1.60 | The default cache increment is now 1 rather than 10. This may affect old scripts that relied on the previous default. |
Fri. March 22, 2002 |
|
5.1.60 | The default cache increment is now 1 rather than 10. This may affect old scripts that relied on the previous default. |
Fri. March 22, 2002 |
|
5.1.60 | Ray-traced motion blur works for displaced open polygons now. The previous version commit has been changed to reflect this. |
Fri. March 22, 2002 |
|
5.1.60 | Ray-traced motion blur works for displaced open polygons now. The previous version commit has been changed to reflect this. |
Fri. March 22, 2002 |
|
5.1.60 | Ray-traced motion blur works for displaced open polygons now. The previous version commit has been changed to reflect this. |
Fri. March 22, 2002 |