Houdini Main Changelogs
6.0.211 | The Null SOP now can have no inputs, in which case it, as one would expect, generates no geometry. |
Fri. February 14, 2003 | |
6.0.211 | The Null SOP now can have no inputs, in which case it, as one would expect, generates no geometry. |
Fri. February 14, 2003 | |
6.0.211 | The Null SOP now can have no inputs, in which case it, as one would expect, generates no geometry. |
Fri. February 14, 2003 | |
6.0.211 | The Null SOP now can have no inputs, in which case it, as one would expect, generates no geometry. |
Fri. February 14, 2003 | |
6.0.211 | The Null SOP now can have no inputs, in which case it, as one would expect, generates no geometry. |
Fri. February 14, 2003 | |
6.0.211 | You can now have merge OPs wire into the indirect inputs of subnet OPs even if those inputs are not connected to anything at the parent level. |
Fri. February 14, 2003 | |
6.0.211 | You can now have merge OPs wire into the indirect inputs of subnet OPs even if those inputs are not connected to anything at the parent level. |
Fri. February 14, 2003 | |
6.0.211 | You can now have merge OPs wire into the indirect inputs of subnet OPs even if those inputs are not connected to anything at the parent level. |
Fri. February 14, 2003 | |
6.0.211 | You can now have merge OPs wire into the indirect inputs of subnet OPs even if those inputs are not connected to anything at the parent level. |
Fri. February 14, 2003 | |
6.0.211 | You can now have merge OPs wire into the indirect inputs of subnet OPs even if those inputs are not connected to anything at the parent level. |
Fri. February 14, 2003 | |
6.0.211 | The caching of the Trail SOP has been tweaked. It now removes geometry from its cache based upon when they were last needed, not on their frame number. This way, the second time playing through an animation where the cache size is less than the frame range, will cache as well as the first time. |
Fri. February 14, 2003 | |
6.0.211 | The caching of the Trail SOP has been tweaked. It now removes geometry from its cache based upon when they were last needed, not on their frame number. This way, the second time playing through an animation where the cache size is less than the frame range, will cache as well as the first time. |
Fri. February 14, 2003 | |
6.0.211 | The caching of the Trail SOP has been tweaked. It now removes geometry from its cache based upon when they were last needed, not on their frame number. This way, the second time playing through an animation where the cache size is less than the frame range, will cache as well as the first time. |
Fri. February 14, 2003 | |
6.0.211 | The caching of the Trail SOP has been tweaked. It now removes geometry from its cache based upon when they were last needed, not on their frame number. This way, the second time playing through an animation where the cache size is less than the frame range, will cache as well as the first time. |
Fri. February 14, 2003 | |
6.0.211 | The caching of the Trail SOP has been tweaked. It now removes geometry from its cache based upon when they were last needed, not on their frame number. This way, the second time playing through an animation where the cache size is less than the frame range, will cache as well as the first time. |
Fri. February 14, 2003 | |
6.0.211 | Fixed bug in the code to convert absolute node references to relative node references when saving an operator definition from the Type Properties dialog. |
Fri. February 14, 2003 | |
6.0.211 | Fixed bug in the code to convert absolute node references to relative node references when saving an operator definition from the Type Properties dialog. |
Fri. February 14, 2003 | |
6.0.211 | Fixed bug in the code to convert absolute node references to relative node references when saving an operator definition from the Type Properties dialog. |
Fri. February 14, 2003 | |
6.0.211 | Fixed bug in the code to convert absolute node references to relative node references when saving an operator definition from the Type Properties dialog. |
Fri. February 14, 2003 | |
6.0.211 | Fixed bug in the code to convert absolute node references to relative node references when saving an operator definition from the Type Properties dialog. |
Fri. February 14, 2003 | |
6.0.211 | If the embedded operator type library and another external operator type library both have definitions for the same operator, and both have the same time stamp, preference would be given to the definition in the embedded library (even if the "Give Preference to Definitions Save in Hip File" option is turned off). Now in that situation, preference is given to the definition in the external library file. |
Fri. February 14, 2003 | |
6.0.211 | If the embedded operator type library and another external operator type library both have definitions for the same operator, and both have the same time stamp, preference would be given to the definition in the embedded library (even if the "Give Preference to Definitions Save in Hip File" option is turned off). Now in that situation, preference is given to the definition in the external library file. |
Fri. February 14, 2003 | |
6.0.211 | If the embedded operator type library and another external operator type library both have definitions for the same operator, and both have the same time stamp, preference would be given to the definition in the embedded library (even if the "Give Preference to Definitions Save in Hip File" option is turned off). Now in that situation, preference is given to the definition in the external library file. |
Fri. February 14, 2003 | |
6.0.211 | If the embedded operator type library and another external operator type library both have definitions for the same operator, and both have the same time stamp, preference would be given to the definition in the embedded library (even if the "Give Preference to Definitions Save in Hip File" option is turned off). Now in that situation, preference is given to the definition in the external library file. |
Fri. February 14, 2003 | |
6.0.211 | If the embedded operator type library and another external operator type library both have definitions for the same operator, and both have the same time stamp, preference would be given to the definition in the embedded library (even if the "Give Preference to Definitions Save in Hip File" option is turned off). Now in that situation, preference is given to the definition in the external library file. |
Fri. February 14, 2003 |