Houdini Main Changelogs
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 | |
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 | |
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 | |
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 | |
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 | |
5.1.59 | The meaning of "variance 0" has changed in mantra so that this will cause every pixel to be sampled by the maximum super-sampling rate. |
Thu. March 21, 2002 | |
5.1.59 | The meaning of "variance 0" has changed in mantra so that this will cause every pixel to be sampled by the maximum super-sampling rate. |
Thu. March 21, 2002 | |
5.1.59 | The meaning of "variance 0" has changed in mantra so that this will cause every pixel to be sampled by the maximum super-sampling rate. |
Thu. March 21, 2002 | |
5.1.59 | The meaning of "variance 0" has changed in mantra so that this will cause every pixel to be sampled by the maximum super-sampling rate. |
Thu. March 21, 2002 | |
5.1.59 | The meaning of "variance 0" has changed in mantra so that this will cause every pixel to be sampled by the maximum super-sampling rate. |
Thu. March 21, 2002 | |
5.1.59 | Large portions of the ray-intersection code have been re-written. This allows for correct intersection against non-planar polygons. However, in some cases mantra will take a performance hit because of this improvement in quality. In other cases, memory or speed may be better than previous versions of mantra. However, in all cases, quality should be better. |
Thu. March 21, 2002 | |
5.1.59 | Large portions of the ray-intersection code have been re-written. This allows for correct intersection against non-planar polygons. However, in some cases mantra will take a performance hit because of this improvement in quality. In other cases, memory or speed may be better than previous versions of mantra. However, in all cases, quality should be better. |
Thu. March 21, 2002 | |
5.1.59 | Large portions of the ray-intersection code have been re-written. This allows for correct intersection against non-planar polygons. However, in some cases mantra will take a performance hit because of this improvement in quality. In other cases, memory or speed may be better than previous versions of mantra. However, in all cases, quality should be better. |
Thu. March 21, 2002 | |
5.1.59 | Large portions of the ray-intersection code have been re-written. This allows for correct intersection against non-planar polygons. However, in some cases mantra will take a performance hit because of this improvement in quality. In other cases, memory or speed may be better than previous versions of mantra. However, in all cases, quality should be better. |
Thu. March 21, 2002 | |
5.1.59 | Large portions of the ray-intersection code have been re-written. This allows for correct intersection against non-planar polygons. However, in some cases mantra will take a performance hit because of this improvement in quality. In other cases, memory or speed may be better than previous versions of mantra. However, in all cases, quality should be better. |
Thu. March 21, 2002 | |
5.1.59 | Motion blurred displacement mapping has been sped up in mantra. Results may be very subtly different, but no more incorrect than in previous versions. |
Thu. March 21, 2002 | |
5.1.59 | Motion blurred displacement mapping has been sped up in mantra. Results may be very subtly different, but no more incorrect than in previous versions. |
Thu. March 21, 2002 |