Houdini Main Changelogs
6.0.251 | Fixed potential core dumps when trying to add nodes to a locked subnet operator from within the viewport. |
Wed. March 26, 2003 | |
6.0.251 | Fixed potential core dumps when trying to add nodes to a locked subnet operator from within the viewport. |
Wed. March 26, 2003 | |
6.0.251 | Fixed potential core dumps when trying to add nodes to a locked subnet operator from within the viewport. |
Wed. March 26, 2003 | |
6.0.251 | Fixed potential core dumps when trying to add nodes to a locked subnet operator from within the viewport. |
Wed. March 26, 2003 | |
6.0.251 | If Houdini 6 detects a Houdini 5.5 hserver on unix, it will stop the old hserver and start a version 6 hserver. (hserver 6 will work with both Houdini 5.5 and Houdini 6.) |
Wed. March 26, 2003 | |
6.0.251 | If Houdini 6 detects a Houdini 5.5 hserver on unix, it will stop the old hserver and start a version 6 hserver. (hserver 6 will work with both Houdini 5.5 and Houdini 6.) |
Wed. March 26, 2003 | |
6.0.251 | If Houdini 6 detects a Houdini 5.5 hserver on unix, it will stop the old hserver and start a version 6 hserver. (hserver 6 will work with both Houdini 5.5 and Houdini 6.) |
Wed. March 26, 2003 | |
6.0.251 | If Houdini 6 detects a Houdini 5.5 hserver on unix, it will stop the old hserver and start a version 6 hserver. (hserver 6 will work with both Houdini 5.5 and Houdini 6.) |
Wed. March 26, 2003 | |
6.0.251 | If Houdini 6 detects a Houdini 5.5 hserver on unix, it will stop the old hserver and start a version 6 hserver. (hserver 6 will work with both Houdini 5.5 and Houdini 6.) |
Wed. March 26, 2003 | |
6.0.251 | Fixed some more crashing bugs with the new popnet SOP. |
Wed. March 26, 2003 | |
6.0.251 | Fixed some more crashing bugs with the new popnet SOP. |
Wed. March 26, 2003 | |
6.0.251 | Fixed some more crashing bugs with the new popnet SOP. |
Wed. March 26, 2003 | |
6.0.251 | Fixed some more crashing bugs with the new popnet SOP. |
Wed. March 26, 2003 | |
6.0.251 | Fixed some more crashing bugs with the new popnet SOP. |
Wed. March 26, 2003 | |
6.0.251 | Fixed a bug where deleting an operator definition from the Embedded OTL in the Operator Type Manager would not update the contents properly. Previously it would appear as if the definition had not been deleted. |
Wed. March 26, 2003 | |
6.0.251 | Fixed a bug where deleting an operator definition from the Embedded OTL in the Operator Type Manager would not update the contents properly. Previously it would appear as if the definition had not been deleted. |
Wed. March 26, 2003 | |
6.0.251 | Fixed a bug where deleting an operator definition from the Embedded OTL in the Operator Type Manager would not update the contents properly. Previously it would appear as if the definition had not been deleted. |
Wed. March 26, 2003 | |
6.0.251 | Fixed a bug where deleting an operator definition from the Embedded OTL in the Operator Type Manager would not update the contents properly. Previously it would appear as if the definition had not been deleted. |
Wed. March 26, 2003 | |
6.0.251 | Fixed a bug where deleting an operator definition from the Embedded OTL in the Operator Type Manager would not update the contents properly. Previously it would appear as if the definition had not been deleted. |
Wed. March 26, 2003 | |
6.0.251 | It is now possible to use the "op:" syntax with relative paths to reference a COP operator as a texture map (for background images, projected textures, and SHOPs). To use a relative COP path, use a format such as "op:cop2net1/file1" or "op:../../cop2net1/file1". |
Wed. March 26, 2003 | |
6.0.251 | It is now possible to use the "op:" syntax with relative paths to reference a COP operator as a texture map (for background images, projected textures, and SHOPs). To use a relative COP path, use a format such as "op:cop2net1/file1" or "op:../../cop2net1/file1". |
Wed. March 26, 2003 | |
6.0.251 | It is now possible to use the "op:" syntax with relative paths to reference a COP operator as a texture map (for background images, projected textures, and SHOPs). To use a relative COP path, use a format such as "op:cop2net1/file1" or "op:../../cop2net1/file1". |
Wed. March 26, 2003 | |
6.0.251 | It is now possible to use the "op:" syntax with relative paths to reference a COP operator as a texture map (for background images, projected textures, and SHOPs). To use a relative COP path, use a format such as "op:cop2net1/file1" or "op:../../cop2net1/file1". |
Wed. March 26, 2003 | |
6.0.251 | It is now possible to use the "op:" syntax with relative paths to reference a COP operator as a texture map (for background images, projected textures, and SHOPs). To use a relative COP path, use a format such as "op:cop2net1/file1" or "op:../../cop2net1/file1". |
Wed. March 26, 2003 | |
6.0.250 | Hitting tab in the multiline text editors will now insert enough spaces to align to the next 4 character column. Hitting tab with multiple lines selected will indent those lines by 4 characters. |
Tue. March 25, 2003 |