Houdini Main Changelogs
 |
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 |
|
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.59 | Ray-traced motion blur is now supported for most primitives in mantra. Currently, only metaballs and sub-division surfaces do not support deformation/velocity blur. This feature can be expensive, and can be turned off with the -QB command line option. This means that all reflections/shadows/refractions can be motion blurred. As a note: Motion blurred rays are not perfectly accurate. However, they should be artistically correct. |
Thu. March 21, 2002 |