Houdini Main Changelogs
6.1.110 | The -geometry option now lets you span multiple monitors under Windows. |
Wed. August 20, 2003 | |
6.1.110 | The -geometry option now lets you span multiple monitors under Windows. |
Wed. August 20, 2003 | |
6.1.110 | The -geometry option now lets you span multiple monitors under Windows. |
Wed. August 20, 2003 | |
6.1.110 | Fixed a case where having an output on an object subnet other than the default would falsely report infinite recursion. |
Wed. August 20, 2003 | |
6.1.110 | Fixed a case where having an output on an object subnet other than the default would falsely report infinite recursion. |
Wed. August 20, 2003 | |
6.1.110 | Fixed a case where having an output on an object subnet other than the default would falsely report infinite recursion. |
Wed. August 20, 2003 | |
6.1.110 | Fixed a case where having an output on an object subnet other than the default would falsely report infinite recursion. |
Wed. August 20, 2003 | |
6.1.110 | Fixed a case where having an output on an object subnet other than the default would falsely report infinite recursion. |
Wed. August 20, 2003 | |
6.1.110 | When using the "Install Operator Type Library..." dialog, when the user hits enter, check if the current path is a directory, and if so, open the filechooser rather than giving an error message. |
Wed. August 20, 2003 | |
6.1.110 | When using the "Install Operator Type Library..." dialog, when the user hits enter, check if the current path is a directory, and if so, open the filechooser rather than giving an error message. |
Wed. August 20, 2003 | |
6.1.110 | When using the "Install Operator Type Library..." dialog, when the user hits enter, check if the current path is a directory, and if so, open the filechooser rather than giving an error message. |
Wed. August 20, 2003 | |
6.1.110 | When using the "Install Operator Type Library..." dialog, when the user hits enter, check if the current path is a directory, and if so, open the filechooser rather than giving an error message. |
Wed. August 20, 2003 | |
6.1.110 | When using the "Install Operator Type Library..." dialog, when the user hits enter, check if the current path is a directory, and if so, open the filechooser rather than giving an error message. |
Wed. August 20, 2003 | |
6.1.110 | Fixed bug where displaying individual components of a image with the int32 format would cause Halo to crash. |
Wed. August 20, 2003 | |
6.1.110 | Fixed bug where displaying individual components of a image with the int32 format would cause Halo to crash. |
Wed. August 20, 2003 | |
6.1.110 | Fixed bug where displaying individual components of a image with the int32 format would cause Halo to crash. |
Wed. August 20, 2003 | |
6.1.110 | Fixed bug where displaying individual components of a image with the int32 format would cause Halo to crash. |
Wed. August 20, 2003 | |
6.1.110 | Fixed bug where displaying individual components of a image with the int32 format would cause Halo to crash. |
Wed. August 20, 2003 | |
6.1.110 | Fixed a bug in COPs where saving out to a non .pic image format would cause the output image to be corrupt if the alpha channel and the RGB channels were computed with different bounds. |
Wed. August 20, 2003 | |
6.1.110 | Fixed a bug in COPs where saving out to a non .pic image format would cause the output image to be corrupt if the alpha channel and the RGB channels were computed with different bounds. |
Wed. August 20, 2003 | |
6.1.110 | Fixed a bug in COPs where saving out to a non .pic image format would cause the output image to be corrupt if the alpha channel and the RGB channels were computed with different bounds. |
Wed. August 20, 2003 | |
6.1.110 | Fixed a bug in COPs where saving out to a non .pic image format would cause the output image to be corrupt if the alpha channel and the RGB channels were computed with different bounds. |
Wed. August 20, 2003 | |
6.1.110 | Fixed a bug in COPs where saving out to a non .pic image format would cause the output image to be corrupt if the alpha channel and the RGB channels were computed with different bounds. |
Wed. August 20, 2003 | |
6.1.110 | If an OTL file was modified outside a Houdini session (either by a second Houdini session, or through regular file manipulation), Houdini previously would not detect this change. This could lead to corrupted OTL files or core dumps. Now we detect externally-induced changes to OTL files and automatically refresh any libraries that are changed. The refresh happens the next time Houdini tries to access information from the OTL. |
Wed. August 20, 2003 | |
6.1.110 | If an OTL file was modified outside a Houdini session (either by a second Houdini session, or through regular file manipulation), Houdini previously would not detect this change. This could lead to corrupted OTL files or core dumps. Now we detect externally-induced changes to OTL files and automatically refresh any libraries that are changed. The refresh happens the next time Houdini tries to access information from the OTL. |
Wed. August 20, 2003 |