Houdini Main Changelogs
![]() |
6.1.146 | Fixed a bug introduced yesterday where non-Windows platforms would not list directories in the file chooser dialogs. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a bug introduced yesterday where non-Windows platforms would not list directories in the file chooser dialogs. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a bug introduced yesterday where non-Windows platforms would not list directories in the file chooser dialogs. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a bug introduced yesterday where non-Windows platforms would not list directories in the file chooser dialogs. |
木. 9月 25, 2003 |
![]() |
6.1.146 | When rendering geometry from disk files, there is now a further option to automatically save the Render SOP as an archive (Auto-Archive). This option is currently only implemented for IFD and RIB generation. The option should be used with caution since there are several caveats: 1) There are no efficiency gains when rendering IFDs, but the option is implemented for completeness. 2) When Auto-Archiving RIB objects, the archives will be incorrectly generated if the geometry is instanced more than one time. 3) Shaders are embedded in the auto-archive, therefore when rendering shadow maps, it's impossible to optimize using null shaders. |
木. 9月 25, 2003 |
![]() |
6.1.146 | When rendering geometry from disk files, there is now a further option to automatically save the Render SOP as an archive (Auto-Archive). This option is currently only implemented for IFD and RIB generation. The option should be used with caution since there are several caveats: 1) There are no efficiency gains when rendering IFDs, but the option is implemented for completeness. 2) When Auto-Archiving RIB objects, the archives will be incorrectly generated if the geometry is instanced more than one time. 3) Shaders are embedded in the auto-archive, therefore when rendering shadow maps, it's impossible to optimize using null shaders. |
木. 9月 25, 2003 |
![]() |
6.1.146 | When rendering geometry from disk files, there is now a further option to automatically save the Render SOP as an archive (Auto-Archive). This option is currently only implemented for IFD and RIB generation. The option should be used with caution since there are several caveats: 1) There are no efficiency gains when rendering IFDs, but the option is implemented for completeness. 2) When Auto-Archiving RIB objects, the archives will be incorrectly generated if the geometry is instanced more than one time. 3) Shaders are embedded in the auto-archive, therefore when rendering shadow maps, it's impossible to optimize using null shaders. |
木. 9月 25, 2003 |
![]() |
6.1.146 | When rendering geometry from disk files, there is now a further option to automatically save the Render SOP as an archive (Auto-Archive). This option is currently only implemented for IFD and RIB generation. The option should be used with caution since there are several caveats: 1) There are no efficiency gains when rendering IFDs, but the option is implemented for completeness. 2) When Auto-Archiving RIB objects, the archives will be incorrectly generated if the geometry is instanced more than one time. 3) Shaders are embedded in the auto-archive, therefore when rendering shadow maps, it's impossible to optimize using null shaders. |
木. 9月 25, 2003 |
![]() |
6.1.146 | When rendering geometry from disk files, there is now a further option to automatically save the Render SOP as an archive (Auto-Archive). This option is currently only implemented for IFD and RIB generation. The option should be used with caution since there are several caveats: 1) There are no efficiency gains when rendering IFDs, but the option is implemented for completeness. 2) When Auto-Archiving RIB objects, the archives will be incorrectly generated if the geometry is instanced more than one time. 3) Shaders are embedded in the auto-archive, therefore when rendering shadow maps, it's impossible to optimize using null shaders. |
木. 9月 25, 2003 |
![]() |
6.1.146 | When rendering geometry from disk files, there is now a further option to automatically save the Render SOP as an archive (Auto-Archive). This option is currently only implemented for IFD and RIB generation. The option should be used with caution since there are several caveats: 1) There are no efficiency gains when rendering IFDs, but the option is implemented for completeness. 2) When Auto-Archiving RIB objects, the archives will be incorrectly generated if the geometry is instanced more than one time. 3) Shaders are embedded in the auto-archive, therefore when rendering shadow maps, it's impossible to optimize using null shaders. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a threading bug with the VEX operators, which caused crashes periodically. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a threading bug with the VEX operators, which caused crashes periodically. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a threading bug with the VEX operators, which caused crashes periodically. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a threading bug with the VEX operators, which caused crashes periodically. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a threading bug with the VEX operators, which caused crashes periodically. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a threading bug with the VEX operators, which caused crashes periodically. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a bug where the file COP could not properly remap a single image into a sequence. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a bug where the file COP could not properly remap a single image into a sequence. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a bug where the file COP could not properly remap a single image into a sequence. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a bug where the file COP could not properly remap a single image into a sequence. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a bug where the file COP could not properly remap a single image into a sequence. |
木. 9月 25, 2003 |
![]() |
6.1.146 | Fixed a bug where the file COP could not properly remap a single image into a sequence. |
木. 9月 25, 2003 |
![]() |
6.1.146 | When doing a "Create Type From" operation on a subnet operator, the default parameter values for float type parameters would sometimes appear as "" instead of "0". This would result in bad initial parameter values. Now the defaults are properly set to "0", and the case of float parameter defaults of "" is handled properly. |
木. 9月 25, 2003 |
![]() |
6.1.146 | When doing a "Create Type From" operation on a subnet operator, the default parameter values for float type parameters would sometimes appear as "" instead of "0". This would result in bad initial parameter values. Now the defaults are properly set to "0", and the case of float parameter defaults of "" is handled properly. |
木. 9月 25, 2003 |
![]() |
6.1.146 | When doing a "Create Type From" operation on a subnet operator, the default parameter values for float type parameters would sometimes appear as "" instead of "0". This would result in bad initial parameter values. Now the defaults are properly set to "0", and the case of float parameter defaults of "" is handled properly. |
木. 9月 25, 2003 |