Houdini Main Changelogs
6.0.208 | In a viewport with many visible handles, pressing the "k" key would result in one undo for each handle. Now it creates a single undo entry for all the handles. |
Tue. February 11, 2003 | |
6.0.208 | In a viewport with many visible handles, pressing the "k" key would result in one undo for each handle. Now it creates a single undo entry for all the handles. |
Tue. February 11, 2003 | |
6.0.208 | The compiler vcc now handles a (void) return type more strictly. It is no longer possible to have code like: Cf = fresnel(P, N, 1.3, kr, kt); since the fresnel() function returns a void type, it is not possible to assign it's return value to another variable. |
Tue. February 11, 2003 | |
6.0.208 | The compiler vcc now handles a (void) return type more strictly. It is no longer possible to have code like: Cf = fresnel(P, N, 1.3, kr, kt); since the fresnel() function returns a void type, it is not possible to assign it's return value to another variable. |
Tue. February 11, 2003 | |
6.0.208 | The compiler vcc now handles a (void) return type more strictly. It is no longer possible to have code like: Cf = fresnel(P, N, 1.3, kr, kt); since the fresnel() function returns a void type, it is not possible to assign it's return value to another variable. |
Tue. February 11, 2003 | |
6.0.208 | The compiler vcc now handles a (void) return type more strictly. It is no longer possible to have code like: Cf = fresnel(P, N, 1.3, kr, kt); since the fresnel() function returns a void type, it is not possible to assign it's return value to another variable. |
Tue. February 11, 2003 | |
6.0.208 | The compiler vcc now handles a (void) return type more strictly. It is no longer possible to have code like: Cf = fresnel(P, N, 1.3, kr, kt); since the fresnel() function returns a void type, it is not possible to assign it's return value to another variable. |
Tue. February 11, 2003 | |
6.0.208 | Fixed bug where PolyKnit sop would sometimes cause a crash if the user modifies the input sops while in the middle of a knitting operation. |
Tue. February 11, 2003 | |
6.0.208 | Fixed bug where PolyKnit sop would sometimes cause a crash if the user modifies the input sops while in the middle of a knitting operation. |
Tue. February 11, 2003 | |
6.0.208 | Fixed bug where PolyKnit sop would sometimes cause a crash if the user modifies the input sops while in the middle of a knitting operation. |
Tue. February 11, 2003 | |
6.0.208 | Fixed bug where PolyKnit sop would sometimes cause a crash if the user modifies the input sops while in the middle of a knitting operation. |
Tue. February 11, 2003 | |
6.0.208 | Fixed bug where PolyKnit sop would sometimes cause a crash if the user modifies the input sops while in the middle of a knitting operation. |
Tue. February 11, 2003 | |
6.0.207 | The SHOP (and VOP) viewers now have a default ambient light with illumination (.1, .1, .1). Currently, there is no way to adjust the level of ambient light through the viewer. |
Mon. February 10, 2003 | |
6.0.207 | The SHOP (and VOP) viewers now have a default ambient light with illumination (.1, .1, .1). Currently, there is no way to adjust the level of ambient light through the viewer. |
Mon. February 10, 2003 | |
6.0.207 | The SHOP (and VOP) viewers now have a default ambient light with illumination (.1, .1, .1). Currently, there is no way to adjust the level of ambient light through the viewer. |
Mon. February 10, 2003 | |
6.0.207 | The SHOP (and VOP) viewers now have a default ambient light with illumination (.1, .1, .1). Currently, there is no way to adjust the level of ambient light through the viewer. |
Mon. February 10, 2003 | |
6.0.207 | The SHOP (and VOP) viewers now have a default ambient light with illumination (.1, .1, .1). Currently, there is no way to adjust the level of ambient light through the viewer. |
Mon. February 10, 2003 | |
6.0.207 | Fixed bug where if you use the capture region handles as deformers, then you would need to set a key first before changing its values. |
Mon. February 10, 2003 | |
6.0.207 | Fixed bug where if you use the capture region handles as deformers, then you would need to set a key first before changing its values. |
Mon. February 10, 2003 | |
6.0.207 | Fixed bug where if you use the capture region handles as deformers, then you would need to set a key first before changing its values. |
Mon. February 10, 2003 | |
6.0.207 | Fixed bug where if you use the capture region handles as deformers, then you would need to set a key first before changing its values. |
Mon. February 10, 2003 | |
6.0.207 | Fixed bug where if you use the capture region handles as deformers, then you would need to set a key first before changing its values. |
Mon. February 10, 2003 | |
6.0.207 | Performing a File|New or a File|Open now deletes all locally defined custom panels, i.e., those saved to the hip file. |
Mon. February 10, 2003 | |
6.0.207 | Performing a File|New or a File|Open now deletes all locally defined custom panels, i.e., those saved to the hip file. |
Mon. February 10, 2003 | |
6.0.207 | Performing a File|New or a File|Open now deletes all locally defined custom panels, i.e., those saved to the hip file. |
Mon. February 10, 2003 |