Houdini Main Changelogs
 |
6.1.55 | It is now possible to create custom operator types with arbitrary nesting of parameters into folders, including having folders within other folders. This can be done using the Type Properties dialog, using the group pragma in VEX code (use "Foder 1/Folder 2" to indicate Folder 2 nested inside Folder 1), and in the VOP Network parameter order editor. |
Wed. June 25, 2003 |
 |
6.1.55 | When using the group pragma to create folder tabs for your VEX operators, the behavior has changed slightly. Previously, this: #pragma group Page1 parm1 #pragma group Page2 parm2 #pragma group Page1 parm3 would result in parm1 and parm3 both appearing on the first page (Page1), and parm2 appearing on Page2. Now this would result in parm1 appearing on Page1, parm2 on Page2, and parm3 on a third page, also labeled Page1. |
Wed. June 25, 2003 |
|
6.1.55 | It is now possible to create custom operator types with arbitrary nesting of parameters into folders, including having folders within other folders. This can be done using the Type Properties dialog, using the group pragma in VEX code (use "Foder 1/Folder 2" to indicate Folder 2 nested inside Folder 1), and in the VOP Network parameter order editor. |
Wed. June 25, 2003 |
|
6.1.55 | When using the group pragma to create folder tabs for your VEX operators, the behavior has changed slightly. Previously, this: #pragma group Page1 parm1 #pragma group Page2 parm2 #pragma group Page1 parm3 would result in parm1 and parm3 both appearing on the first page (Page1), and parm2 appearing on Page2. Now this would result in parm1 appearing on Page1, parm2 on Page2, and parm3 on a third page, also labeled Page1. |
Wed. June 25, 2003 |
 |
6.1.55 | It is now possible to change the frame step in MPlay via the Options->Settings dialog. Previously, the frame step field was ignored. |
Wed. June 25, 2003 |
|
6.1.55 | It is now possible to change the frame step in MPlay via the Options->Settings dialog. Previously, the frame step field was ignored. |
Wed. June 25, 2003 |
|
6.1.55 | It is now possible to change the frame step in MPlay via the Options->Settings dialog. Previously, the frame step field was ignored. |
Wed. June 25, 2003 |
|
6.1.55 | It is now possible to change the frame step in MPlay via the Options->Settings dialog. Previously, the frame step field was ignored. |
Wed. June 25, 2003 |
|
6.1.55 | It is now possible to change the frame step in MPlay via the Options->Settings dialog. Previously, the frame step field was ignored. |
Wed. June 25, 2003 |
 |
6.1.55 | The render command will now look in the current object path for the output driver instead of scanning solely "/out" for the output driver. In theory, render scripts should be un-affected by this change. However, it's possible that under some circumstances, scripts may behave slightly differently. |
Wed. June 25, 2003 |
|
6.1.55 | The render command will now look in the current object path for the output driver instead of scanning solely "/out" for the output driver. In theory, render scripts should be un-affected by this change. However, it's possible that under some circumstances, scripts may behave slightly differently. |
Wed. June 25, 2003 |
|
6.1.55 | The render command will now look in the current object path for the output driver instead of scanning solely "/out" for the output driver. In theory, render scripts should be un-affected by this change. However, it's possible that under some circumstances, scripts may behave slightly differently. |
Wed. June 25, 2003 |
|
6.1.55 | The render command will now look in the current object path for the output driver instead of scanning solely "/out" for the output driver. In theory, render scripts should be un-affected by this change. However, it's possible that under some circumstances, scripts may behave slightly differently. |
Wed. June 25, 2003 |
|
6.1.55 | The render command will now look in the current object path for the output driver instead of scanning solely "/out" for the output driver. In theory, render scripts should be un-affected by this change. However, it's possible that under some circumstances, scripts may behave slightly differently. |
Wed. June 25, 2003 |
|
6.1.55 | The render command will now look in the current object path for the output driver instead of scanning solely "/out" for the output driver. |
Wed. June 25, 2003 |
|
6.1.55 | The render command will now look in the current object path for the output driver instead of scanning solely "/out" for the output driver. |
Wed. June 25, 2003 |
|
6.1.55 | The render command will now look in the current object path for the output driver instead of scanning solely "/out" for the output driver. |
Wed. June 25, 2003 |
|
6.1.55 | The render command will now look in the current object path for the output driver instead of scanning solely "/out" for the output driver. |
Wed. June 25, 2003 |
|
6.1.55 | The render command will now look in the current object path for the output driver instead of scanning solely "/out" for the output driver. |
Wed. June 25, 2003 |
|
6.1.55 | The orientation of auto-generated reflection maps was fixed for mantra. Reflection maps will now be oriented correctly for the object's transform. Default shaders like metal and glass will now work correctly with auto-generated reflection maps. |
Wed. June 25, 2003 |
|
6.1.55 | The orientation of auto-generated reflection maps was fixed for mantra. Reflection maps will now be oriented correctly for the object's transform. Default shaders like metal and glass will now work correctly with auto-generated reflection maps. |
Wed. June 25, 2003 |
|
6.1.55 | The orientation of auto-generated reflection maps was fixed for mantra. Reflection maps will now be oriented correctly for the object's transform. Default shaders like metal and glass will now work correctly with auto-generated reflection maps. |
Wed. June 25, 2003 |
|
6.1.55 | The orientation of auto-generated reflection maps was fixed for mantra. Reflection maps will now be oriented correctly for the object's transform. Default shaders like metal and glass will now work correctly with auto-generated reflection maps. |
Wed. June 25, 2003 |
|
6.1.55 | The orientation of auto-generated reflection maps was fixed for mantra. Reflection maps will now be oriented correctly for the object's transform. Default shaders like metal and glass will now work correctly with auto-generated reflection maps. |
Wed. June 25, 2003 |
 |
6.1.55 | The channel editor can now automatically put in a default cycle() expression using the frame range from the beginning of the animation. |
Wed. June 25, 2003 |