Houdini Main Changelogs
 |
7.0.113 | Moved the hotkeys for the channel list gadgets into their own context. |
Tue. June 29, 2004 |
 |
7.0.112 | You can no longer create attributes with spaces or other invalid characters with the Measure SOP. |
Mon. June 28, 2004 |
|
7.0.112 | You can no longer create attributes with spaces or other invalid characters with the Measure SOP. |
Mon. June 28, 2004 |
|
7.0.112 | You can no longer create attributes with spaces or other invalid characters with the Measure SOP. |
Mon. June 28, 2004 |
|
7.0.112 | You can no longer create attributes with spaces or other invalid characters with the Measure SOP. |
Mon. June 28, 2004 |
|
7.0.112 | You can no longer create attributes with spaces or other invalid characters with the Measure SOP. |
Mon. June 28, 2004 |
|
7.0.112 | The Group SOP will no longer evaluate the creation name when creating the pop-ups in the combine tab. This means a creation name of "foo$F" will show up as "foo$F" rather than "foo1". This was done to prevent infinte recooks in cases where the creation name was a point expression to animated geometry. |
Mon. June 28, 2004 |
|
7.0.112 | The Group SOP will no longer evaluate the creation name when creating the pop-ups in the combine tab. This means a creation name of "foo$F" will show up as "foo$F" rather than "foo1". This was done to prevent infinte recooks in cases where the creation name was a point expression to animated geometry. |
Mon. June 28, 2004 |
|
7.0.112 | The Group SOP will no longer evaluate the creation name when creating the pop-ups in the combine tab. This means a creation name of "foo$F" will show up as "foo$F" rather than "foo1". This was done to prevent infinte recooks in cases where the creation name was a point expression to animated geometry. |
Mon. June 28, 2004 |
|
7.0.112 | The Group SOP will no longer evaluate the creation name when creating the pop-ups in the combine tab. This means a creation name of "foo$F" will show up as "foo$F" rather than "foo1". This was done to prevent infinte recooks in cases where the creation name was a point expression to animated geometry. |
Mon. June 28, 2004 |
|
7.0.112 | The Group SOP will no longer evaluate the creation name when creating the pop-ups in the combine tab. This means a creation name of "foo$F" will show up as "foo$F" rather than "foo1". This was done to prevent infinte recooks in cases where the creation name was a point expression to animated geometry. |
Mon. June 28, 2004 |
 |
7.0.112 | Initial commit of the parameter box functionality. It can be accessed from the channel list pane or channel editor. This is still very much a work in progress. |
Mon. June 28, 2004 |
|
7.0.112 | Initial commit of the parameter box functionality. It can be accessed from the channel list pane or channel editor. This is still very much a work in progress. |
Mon. June 28, 2004 |
|
7.0.112 | Initial commit of the parameter box functionality. It can be accessed from the channel list pane or channel editor. This is still very much a work in progress. |
Mon. June 28, 2004 |
|
7.0.112 | Initial commit of the parameter box functionality. It can be accessed from the channel list pane or channel editor. This is still very much a work in progress. |
Mon. June 28, 2004 |
|
7.0.112 | Initial commit of the parameter box functionality. It can be accessed from the channel list pane or channel editor. This is still very much a work in progress. |
Mon. June 28, 2004 |
 |
7.0.112 | At the Object level a new caching layer has been inserted. All objects now implement a virtual method cookMyObj() rather than cookMe(). The only class that implements cookMe() is OBJ_Node base class, where the caching of the transformations takes place. On cache hit, cookMyObj is skipped because the transformation has been found in the cache. On cache miss, a virtual method cookMyObj() is invoked by cookMe(). The method cookMyObj() does excactly the same thing that cookMe() used to do. Note that caching of the transforms is enabled and disabled by an object parameter. When this parameter is "off" the caching check does not occur, and cookMyObj() is always invoked. |
Mon. June 28, 2004 |
|
7.0.112 | At the Object level a new caching layer has been inserted. All objects now implement a virtual method cookMyObj() rather than cookMe(). The only class that implements cookMe() is OBJ_Node base class, where the caching of the transformations takes place. On cache hit, cookMyObj is skipped because the transformation has been found in the cache. On cache miss, a virtual method cookMyObj() is invoked by cookMe(). The method cookMyObj() does excactly the same thing that cookMe() used to do. Note that caching of the transforms is enabled and disabled by an object parameter. When this parameter is "off" the caching check does not occur, and cookMyObj() is always invoked. |
Mon. June 28, 2004 |
|
7.0.112 | At the Object level a new caching layer has been inserted. All objects now implement a virtual method cookMyObj() rather than cookMe(). The only class that implements cookMe() is OBJ_Node base class, where the caching of the transformations takes place. On cache hit, cookMyObj is skipped because the transformation has been found in the cache. On cache miss, a virtual method cookMyObj() is invoked by cookMe(). The method cookMyObj() does excactly the same thing that cookMe() used to do. Note that caching of the transforms is enabled and disabled by an object parameter. When this parameter is "off" the caching check does not occur, and cookMyObj() is always invoked. |
Mon. June 28, 2004 |
|
7.0.112 | At the Object level a new caching layer has been inserted. All objects now implement a virtual method cookMyObj() rather than cookMe(). The only class that implements cookMe() is OBJ_Node base class, where the caching of the transformations takes place. On cache hit, cookMyObj is skipped because the transformation has been found in the cache. On cache miss, a virtual method cookMyObj() is invoked by cookMe(). The method cookMyObj() does excactly the same thing that cookMe() used to do. Note that caching of the transforms is enabled and disabled by an object parameter. When this parameter is "off" the caching check does not occur, and cookMyObj() is always invoked. |
Mon. June 28, 2004 |
|
7.0.112 | At the Object level a new caching layer has been inserted. All objects now implement a virtual method cookMyObj() rather than cookMe(). The only class that implements cookMe() is OBJ_Node base class, where the caching of the transformations takes place. On cache hit, cookMyObj is skipped because the transformation has been found in the cache. On cache miss, a virtual method cookMyObj() is invoked by cookMe(). The method cookMyObj() does excactly the same thing that cookMe() used to do. Note that caching of the transforms is enabled and disabled by an object parameter. When this parameter is "off" the caching check does not occur, and cookMyObj() is always invoked. |
Mon. June 28, 2004 |
 |
7.0.112 | A new hscript command, "objcache", is now available for the object cache management. Please, see the help for details. |
Mon. June 28, 2004 |
|
7.0.112 | A new hscript command, "objcache", is now available for the object cache management. Please, see the help for details. |
Mon. June 28, 2004 |
|
7.0.112 | A new hscript command, "objcache", is now available for the object cache management. Please, see the help for details. |
Mon. June 28, 2004 |
|
7.0.112 | A new hscript command, "objcache", is now available for the object cache management. Please, see the help for details. |
Mon. June 28, 2004 |