Houdini Main Changelogs
6.0.216 | When Houdini writes OPlibraries files (after Installing and Operator Type Library), the library paths are no longer written using full paths. If the library is in a subdirectory of where the OPlibraries file is, we write out a relative path. Otherwise, if the library is in a subdirectory of HIP, HOME, HSITE, or HFS, we write out the library path using the appropriate environment variable. Otherwise we still write the full path name. |
Wed. February 19, 2003 | |
6.0.216 | When Houdini writes OPlibraries files (after Installing and Operator Type Library), the library paths are no longer written using full paths. If the library is in a subdirectory of where the OPlibraries file is, we write out a relative path. Otherwise, if the library is in a subdirectory of HIP, HOME, HSITE, or HFS, we write out the library path using the appropriate environment variable. Otherwise we still write the full path name. |
Wed. February 19, 2003 | |
6.0.216 | When Houdini writes OPlibraries files (after Installing and Operator Type Library), the library paths are no longer written using full paths. If the library is in a subdirectory of where the OPlibraries file is, we write out a relative path. Otherwise, if the library is in a subdirectory of HIP, HOME, HSITE, or HFS, we write out the library path using the appropriate environment variable. Otherwise we still write the full path name. |
Wed. February 19, 2003 | |
6.0.216 | When Houdini writes OPlibraries files (after Installing and Operator Type Library), the library paths are no longer written using full paths. If the library is in a subdirectory of where the OPlibraries file is, we write out a relative path. Otherwise, if the library is in a subdirectory of HIP, HOME, HSITE, or HFS, we write out the library path using the appropriate environment variable. Otherwise we still write the full path name. |
Wed. February 19, 2003 | |
6.0.216 | When Houdini writes OPlibraries files (after Installing and Operator Type Library), the library paths are no longer written using full paths. If the library is in a subdirectory of where the OPlibraries file is, we write out a relative path. Otherwise, if the library is in a subdirectory of HIP, HOME, HSITE, or HFS, we write out the library path using the appropriate environment variable. Otherwise we still write the full path name. |
Wed. February 19, 2003 | |
6.0.216 | Fixed bug where CHOPs wouldn't save channel data to any format other than .clip and .bclip under Linux. |
Wed. February 19, 2003 | |
6.0.216 | Fixed bug where CHOPs wouldn't save channel data to any format other than .clip and .bclip under Linux. |
Wed. February 19, 2003 | |
6.0.216 | Fixed bug where CHOPs wouldn't save channel data to any format other than .clip and .bclip under Linux. |
Wed. February 19, 2003 | |
6.0.216 | Fixed bug where CHOPs wouldn't save channel data to any format other than .clip and .bclip under Linux. |
Wed. February 19, 2003 | |
6.0.216 | Fixed bug where CHOPs wouldn't save channel data to any format other than .clip and .bclip under Linux. |
Wed. February 19, 2003 | |
6.0.215 | Fixed bug where Houdini would crash if a subnet type operator was deleted while a network editor was viewing the contents of that subnet. The network editor would contain invalid subnet input connectors, and interacting with those connectors in any way would cause the crash. |
Tue. February 18, 2003 | |
6.0.215 | Fixed bug where Houdini would crash if a subnet type operator was deleted while a network editor was viewing the contents of that subnet. The network editor would contain invalid subnet input connectors, and interacting with those connectors in any way would cause the crash. |
Tue. February 18, 2003 | |
6.0.215 | Fixed bug where Houdini would crash if a subnet type operator was deleted while a network editor was viewing the contents of that subnet. The network editor would contain invalid subnet input connectors, and interacting with those connectors in any way would cause the crash. |
Tue. February 18, 2003 | |
6.0.215 | Fixed bug where Houdini would crash if a subnet type operator was deleted while a network editor was viewing the contents of that subnet. The network editor would contain invalid subnet input connectors, and interacting with those connectors in any way would cause the crash. |
Tue. February 18, 2003 | |
6.0.215 | Fixed bug where Houdini would crash if a subnet type operator was deleted while a network editor was viewing the contents of that subnet. The network editor would contain invalid subnet input connectors, and interacting with those connectors in any way would cause the crash. |
Tue. February 18, 2003 | |
6.0.215 | Fixed bug where deleting a node that was connected to the input of a node with read-only permissions would cause Houdini to hang in an infinite loop. |
Tue. February 18, 2003 | |
6.0.215 | Fixed bug where deleting a node that was connected to the input of a node with read-only permissions would cause Houdini to hang in an infinite loop. |
Tue. February 18, 2003 | |
6.0.215 | Fixed bug where deleting a node that was connected to the input of a node with read-only permissions would cause Houdini to hang in an infinite loop. |
Tue. February 18, 2003 | |
6.0.215 | Fixed bug where deleting a node that was connected to the input of a node with read-only permissions would cause Houdini to hang in an infinite loop. |
Tue. February 18, 2003 | |
6.0.215 | Fixed bug where deleting a node that was connected to the input of a node with read-only permissions would cause Houdini to hang in an infinite loop. |
Tue. February 18, 2003 | |
6.0.215 | Fixde bug where Edit SOPs would not function properly inside subnet type operator definitions with locked contents. These operators would always appear with error conditions related to permissions. Now these types of operators work properly inside operators with locked contents. |
Tue. February 18, 2003 | |
6.0.215 | Fixde bug where Edit SOPs would not function properly inside subnet type operator definitions with locked contents. These operators would always appear with error conditions related to permissions. Now these types of operators work properly inside operators with locked contents. |
Tue. February 18, 2003 | |
6.0.215 | Fixde bug where Edit SOPs would not function properly inside subnet type operator definitions with locked contents. These operators would always appear with error conditions related to permissions. Now these types of operators work properly inside operators with locked contents. |
Tue. February 18, 2003 | |
6.0.215 | Fixde bug where Edit SOPs would not function properly inside subnet type operator definitions with locked contents. These operators would always appear with error conditions related to permissions. Now these types of operators work properly inside operators with locked contents. |
Tue. February 18, 2003 | |
6.0.215 | Fixde bug where Edit SOPs would not function properly inside subnet type operator definitions with locked contents. These operators would always appear with error conditions related to permissions. Now these types of operators work properly inside operators with locked contents. |
Tue. February 18, 2003 |