Houdini Main Changelogs
6.2.121 | MPlay now accepts \$F in command line files, with an optional padding digit (ie, \$F4). \* is also accepted, though \$F or * is recommended. When a directory contains 2 sequences that differ only in the padding, the \$F syntax is the only way to differentiate them (like test0001.pic, test1.pic). \$F loads unpadded files, \$F{n} loads the n-padded files. |
Thu. January 29, 2004 | |
6.2.121 | Fixing a bug where Houdini would crash if there were more than 8K of error messages displayed to a message window. |
Thu. January 29, 2004 | |
6.2.121 | Fixing a bug where Houdini would crash if there were more than 8K of error messages displayed to a message window. |
Thu. January 29, 2004 | |
6.2.121 | Fixing a bug where Houdini would crash if there were more than 8K of error messages displayed to a message window. |
Thu. January 29, 2004 | |
6.2.121 | Fixing a bug where Houdini would crash if there were more than 8K of error messages displayed to a message window. |
Thu. January 29, 2004 | |
6.2.121 | Fixing a bug where Houdini would crash if there were more than 8K of error messages displayed to a message window. |
Thu. January 29, 2004 | |
6.2.121 | Fixing a bug where, if the help browser crashes for some reason and houdini crashes for a different reason, Houdini won't print out messages about the core dump handler being called recursively. |
Thu. January 29, 2004 | |
6.2.121 | Fixing a bug where, if the help browser crashes for some reason and houdini crashes for a different reason, Houdini won't print out messages about the core dump handler being called recursively. |
Thu. January 29, 2004 | |
6.2.121 | Fixing a bug where, if the help browser crashes for some reason and houdini crashes for a different reason, Houdini won't print out messages about the core dump handler being called recursively. |
Thu. January 29, 2004 | |
6.2.121 | Fixing a bug where, if the help browser crashes for some reason and houdini crashes for a different reason, Houdini won't print out messages about the core dump handler being called recursively. |
Thu. January 29, 2004 | |
6.2.121 | Fixing a bug where, if the help browser crashes for some reason and houdini crashes for a different reason, Houdini won't print out messages about the core dump handler being called recursively. |
Thu. January 29, 2004 | |
6.2.121 | A new global objects option has been added to allow Keep Position When Moving. When enabled, changing the transform of an object will automatically modify its output objects to maintain the same world transform. |
Thu. January 29, 2004 | |
6.2.121 | A new global objects option has been added to allow Keep Position When Moving. When enabled, changing the transform of an object will automatically modify its output objects to maintain the same world transform. |
Thu. January 29, 2004 | |
6.2.121 | A new global objects option has been added to allow Keep Position When Moving. When enabled, changing the transform of an object will automatically modify its output objects to maintain the same world transform. |
Thu. January 29, 2004 | |
6.2.121 | A new global objects option has been added to allow Keep Position When Moving. When enabled, changing the transform of an object will automatically modify its output objects to maintain the same world transform. |
Thu. January 29, 2004 | |
6.2.121 | A new global objects option has been added to allow Keep Position When Moving. When enabled, changing the transform of an object will automatically modify its output objects to maintain the same world transform. |
Thu. January 29, 2004 | |
6.2.120 | When user is in Pose state (or Transform or certain other states) and clicks on CTRL + MMB, the bottom blue help bar will now be populated with the name of the node the cursor is pointing at. |
Wed. January 28, 2004 | |
6.2.120 | When user is in Pose state (or Transform or certain other states) and clicks on CTRL + MMB, the bottom blue help bar will now be populated with the name of the node the cursor is pointing at. |
Wed. January 28, 2004 | |
6.2.120 | When user is in Pose state (or Transform or certain other states) and clicks on CTRL + MMB, the bottom blue help bar will now be populated with the name of the node the cursor is pointing at. |
Wed. January 28, 2004 | |
6.2.120 | When user is in Pose state (or Transform or certain other states) and clicks on CTRL + MMB, the bottom blue help bar will now be populated with the name of the node the cursor is pointing at. |
Wed. January 28, 2004 | |
6.2.120 | When user is in Pose state (or Transform or certain other states) and clicks on CTRL + MMB, the bottom blue help bar will now be populated with the name of the node the cursor is pointing at. |
Wed. January 28, 2004 | |
6.2.120 | When user attempts to load a custom color palette file which contains lines with formatting errors, Houdini will pop up a text dialog detailing the problem. To clarify a previous point: If there are problematic lines in a palette file, those lines will be skipped, but the remainder of the file will still be loaded properly. |
Wed. January 28, 2004 | |
6.2.120 | When user attempts to load a custom color palette file which contains lines with formatting errors, Houdini will pop up a text dialog detailing the problem. To clarify a previous point: If there are problematic lines in a palette file, those lines will be skipped, but the remainder of the file will still be loaded properly. |
Wed. January 28, 2004 | |
6.2.120 | When user attempts to load a custom color palette file which contains lines with formatting errors, Houdini will pop up a text dialog detailing the problem. To clarify a previous point: If there are problematic lines in a palette file, those lines will be skipped, but the remainder of the file will still be loaded properly. |
Wed. January 28, 2004 | |
6.2.120 | When user attempts to load a custom color palette file which contains lines with formatting errors, Houdini will pop up a text dialog detailing the problem. To clarify a previous point: If there are problematic lines in a palette file, those lines will be skipped, but the remainder of the file will still be loaded properly. |
Wed. January 28, 2004 |