Houdini Main Changelogs
8.0.355 | Can no longer select nodes in the light linker target tree when the source selection is empty. |
Tue. September 6, 2005 | |
8.0.355 | Can no longer select nodes in the light linker target tree when the source selection is empty. |
Tue. September 6, 2005 | |
8.0.355 | Can no longer select nodes in the light linker target tree when the source selection is empty. |
Tue. September 6, 2005 | |
8.0.355 | Can no longer select nodes in the light linker target tree when the source selection is empty. |
Tue. September 6, 2005 | |
8.0.354 | Improved the behaviour of the Compositing option 'Reduce Cache Size when Inactive'. Now it waits a short period of time after a COP cooks before beginning to gradually reduce the COP cook cache to its Inactive size. Previously, it would clear the cache as soon as the cook was done. This tended to cause a lot of recooking, which made COPs feel pretty slow. This change will make COPs in Houdini feel much faster since cache hits will improve significantly. |
Mon. September 5, 2005 | |
8.0.354 | Improved the behaviour of the Compositing option 'Reduce Cache Size when Inactive'. Now it waits a short period of time after a COP cooks before beginning to gradually reduce the COP cook cache to its Inactive size. Previously, it would clear the cache as soon as the cook was done. This tended to cause a lot of recooking, which made COPs feel pretty slow. This change will make COPs in Houdini feel much faster since cache hits will improve significantly. |
Mon. September 5, 2005 | |
8.0.354 | Improved the behaviour of the Compositing option 'Reduce Cache Size when Inactive'. Now it waits a short period of time after a COP cooks before beginning to gradually reduce the COP cook cache to its Inactive size. Previously, it would clear the cache as soon as the cook was done. This tended to cause a lot of recooking, which made COPs feel pretty slow. This change will make COPs in Houdini feel much faster since cache hits will improve significantly. |
Mon. September 5, 2005 | |
8.0.354 | Improved the behaviour of the Compositing option 'Reduce Cache Size when Inactive'. Now it waits a short period of time after a COP cooks before beginning to gradually reduce the COP cook cache to its Inactive size. Previously, it would clear the cache as soon as the cook was done. This tended to cause a lot of recooking, which made COPs feel pretty slow. This change will make COPs in Houdini feel much faster since cache hits will improve significantly. |
Mon. September 5, 2005 | |
8.0.354 | Improved the behaviour of the Compositing option 'Reduce Cache Size when Inactive'. Now it waits a short period of time after a COP cooks before beginning to gradually reduce the COP cook cache to its Inactive size. Previously, it would clear the cache as soon as the cook was done. This tended to cause a lot of recooking, which made COPs feel pretty slow. This change will make COPs in Houdini feel much faster since cache hits will improve significantly. |
Mon. September 5, 2005 | |
8.0.354 | Fixed a couple of small bugs with outputing images outside the valid frame range. First, if the user selects 'black' as the extend condition, then render black frames when outside the range - don't bail out of the render. Second, if the user renders a range of frames for a single still image, render the same image for all the frames - don't just render frame 1. |
Mon. September 5, 2005 | |
8.0.354 | Fixed a couple of small bugs with outputing images outside the valid frame range. First, if the user selects 'black' as the extend condition, then render black frames when outside the range - don't bail out of the render. Second, if the user renders a range of frames for a single still image, render the same image for all the frames - don't just render frame 1. |
Mon. September 5, 2005 | |
8.0.354 | Fixed a couple of small bugs with outputing images outside the valid frame range. First, if the user selects 'black' as the extend condition, then render black frames when outside the range - don't bail out of the render. Second, if the user renders a range of frames for a single still image, render the same image for all the frames - don't just render frame 1. |
Mon. September 5, 2005 | |
8.0.354 | Fixed a couple of small bugs with outputing images outside the valid frame range. First, if the user selects 'black' as the extend condition, then render black frames when outside the range - don't bail out of the render. Second, if the user renders a range of frames for a single still image, render the same image for all the frames - don't just render frame 1. |
Mon. September 5, 2005 | |
8.0.354 | Fixed a couple of small bugs with outputing images outside the valid frame range. First, if the user selects 'black' as the extend condition, then render black frames when outside the range - don't bail out of the render. Second, if the user renders a range of frames for a single still image, render the same image for all the frames - don't just render frame 1. |
Mon. September 5, 2005 | |
8.0.354 | Made the VEX noise() function threadsafe, so it can be used correctly in multithreaded VEX COPs. This was also used by such VOPs as aanoise. |
Mon. September 5, 2005 | |
8.0.354 | Made the VEX noise() function threadsafe, so it can be used correctly in multithreaded VEX COPs. This was also used by such VOPs as aanoise. |
Mon. September 5, 2005 | |
8.0.354 | Made the VEX noise() function threadsafe, so it can be used correctly in multithreaded VEX COPs. This was also used by such VOPs as aanoise. |
Mon. September 5, 2005 | |
8.0.354 | Made the VEX noise() function threadsafe, so it can be used correctly in multithreaded VEX COPs. This was also used by such VOPs as aanoise. |
Mon. September 5, 2005 | |
8.0.354 | Made the VEX noise() function threadsafe, so it can be used correctly in multithreaded VEX COPs. This was also used by such VOPs as aanoise. |
Mon. September 5, 2005 | |
8.0.352 | Mantra is a little more graceful in handling input stream errors. For example, if an ASCII geometry stream contains a NAN, the stream will typically throw an error. Mantra will attempt to recover from this error (displaying an appropriate warning message). |
Sat. September 3, 2005 | |
8.0.352 | Mantra is a little more graceful in handling input stream errors. For example, if an ASCII geometry stream contains a NAN, the stream will typically throw an error. Mantra will attempt to recover from this error (displaying an appropriate warning message). |
Sat. September 3, 2005 | |
8.0.352 | Mantra is a little more graceful in handling input stream errors. For example, if an ASCII geometry stream contains a NAN, the stream will typically throw an error. Mantra will attempt to recover from this error (displaying an appropriate warning message). |
Sat. September 3, 2005 | |
8.0.352 | Mantra is a little more graceful in handling input stream errors. For example, if an ASCII geometry stream contains a NAN, the stream will typically throw an error. Mantra will attempt to recover from this error (displaying an appropriate warning message). |
Sat. September 3, 2005 | |
8.0.352 | Mantra is a little more graceful in handling input stream errors. For example, if an ASCII geometry stream contains a NAN, the stream will typically throw an error. Mantra will attempt to recover from this error (displaying an appropriate warning message). |
Sat. September 3, 2005 | |
8.0.351 | There is a new run-time optimizer for VEX available. This optimizer is turned on by setting the environment variable HOUDINI_VEX_OPTIMIZER to 1 (it must be 1 exactly, not 2 and 5 is right out). The new optimizer handles uber shaders much more efficiently than the existing optimizer. Scenes which make heavy use of uber shaders will render much more efficiently now (with less time spent in loading VEX code). The new optimizer also fixes several bugs, including, but not limited to: 5054 - error optimizing functions with multiple return points 9261 - Optimization of do/while loops 11151 - Extra read variables 11871 - Uniform/Varying issue 18876 - shimport() over-optimization 18855 - error optimizing functions with multiple return points 18749 - poor optimization w.r.t. getcomp() along with several uncovered bugs. After sufficient testing, this new optimizer will most likely be made the default. |
Fri. September 2, 2005 |