Houdini Main Changelogs
 |
6.1.51 | Several grid boundary artifacts in filtered evaluation of 3d textures have been eliminated. Evaluation time of the textures is slightly more expensive, but more correct. |
Sat. June 21, 2003 |
|
6.1.51 | Several grid boundary artifacts in filtered evaluation of 3d textures have been eliminated. Evaluation time of the textures is slightly more expensive, but more correct. |
Sat. June 21, 2003 |
|
6.1.51 | Several grid boundary artifacts in filtered evaluation of 3d textures have been eliminated. Evaluation time of the textures is slightly more expensive, but more correct. |
Sat. June 21, 2003 |
|
6.1.51 | Several grid boundary artifacts in filtered evaluation of 3d textures have been eliminated. Evaluation time of the textures is slightly more expensive, but more correct. |
Sat. June 21, 2003 |
 |
6.1.50 | There is now a Main Preferences option under Handles to colour transform handles differently for each axis. |
Fri. June 20, 2003 |
|
6.1.50 | There is now a Main Preferences option under Handles to colour transform handles differently for each axis. |
Fri. June 20, 2003 |
|
6.1.50 | There is now a Main Preferences option under Handles to colour transform handles differently for each axis. |
Fri. June 20, 2003 |
|
6.1.50 | There is now a Main Preferences option under Handles to colour transform handles differently for each axis. |
Fri. June 20, 2003 |
|
6.1.50 | There is now a Main Preferences option under Handles to colour transform handles differently for each axis. |
Fri. June 20, 2003 |
|
6.1.50 | The texture3d functions are now thread safe. This means that they will work properly in COP or other threaded OP contexts. |
Fri. June 20, 2003 |
|
6.1.50 | The texture3d functions are now thread safe. This means that they will work properly in COP or other threaded OP contexts. |
Fri. June 20, 2003 |
|
6.1.50 | The texture3d functions are now thread safe. This means that they will work properly in COP or other threaded OP contexts. |
Fri. June 20, 2003 |
|
6.1.50 | The texture3d functions are now thread safe. This means that they will work properly in COP or other threaded OP contexts. |
Fri. June 20, 2003 |
|
6.1.50 | The texture3d functions are now thread safe. This means that they will work properly in COP or other threaded OP contexts. |
Fri. June 20, 2003 |
 |
6.1.50 | New SOP expression functions detail() and details() which mimic the prim(), point(), and vertex() family of functions, but providing access to detail attributes. |
Fri. June 20, 2003 |
|
6.1.50 | New SOP expression functions detail() and details() which mimic the prim(), point(), and vertex() family of functions, but providing access to detail attributes. |
Fri. June 20, 2003 |
|
6.1.50 | New SOP expression functions detail() and details() which mimic the prim(), point(), and vertex() family of functions, but providing access to detail attributes. |
Fri. June 20, 2003 |
|
6.1.50 | New SOP expression functions detail() and details() which mimic the prim(), point(), and vertex() family of functions, but providing access to detail attributes. |
Fri. June 20, 2003 |
|
6.1.50 | New SOP expression functions detail() and details() which mimic the prim(), point(), and vertex() family of functions, but providing access to detail attributes. |
Fri. June 20, 2003 |
 |
6.1.50 | Fixed bug in the COP rasterizer which would sometimes have random white pixels on the edges. This was caused by zero area polygons. |
Fri. June 20, 2003 |
|
6.1.50 | Fixed bug in the COP rasterizer which would sometimes have random white pixels on the edges. This was caused by zero area polygons. |
Fri. June 20, 2003 |
|
6.1.50 | Fixed bug in the COP rasterizer which would sometimes have random white pixels on the edges. This was caused by zero area polygons. |
Fri. June 20, 2003 |
|
6.1.50 | Fixed bug in the COP rasterizer which would sometimes have random white pixels on the edges. This was caused by zero area polygons. |
Fri. June 20, 2003 |
|
6.1.50 | Fixed bug in the COP rasterizer which would sometimes have random white pixels on the edges. This was caused by zero area polygons. |
Fri. June 20, 2003 |
|
6.1.50 | The Facet SOP's Remove Inline option now properly differentiates between open and closed polygons. This means its behaviour may change from 6.0 for open polygons where, if the polygon had been closed, the start or end points would have been removed. |
Fri. June 20, 2003 |