Houdini Main Changelogs
18.5.111 | Fixed a recent bug that was causing some Linux machines to fail to load Houdini's USD plugins (including the Houdini GL and Karma render delegates, and the BGEO file format plugin). |
Mon. February 3, 2020 | |
18.5.111 | Fixed a recent bug that was causing some Linux machines to fail to load Houdini's USD plugins (including the Houdini GL and Karma render delegates, and the BGEO file format plugin). |
Mon. February 3, 2020 | |
18.5.111 | When saving an HDA in unpacked format some per node data is now stored in separate files along side the Contents.mime file.
When reading an unpacked HDA (or converting it to packed) the values are first read from the files mentioned above and then filled in accordingly. If the file is missing, no error is produced, the blank/zero value will remain. |
Mon. February 3, 2020 | |
18.5.111 | When saving an HDA in unpacked format some per node data is now stored in separate files along side the Contents.mime file.
When reading an unpacked HDA (or converting it to packed) the values are first read from the files mentioned above and then filled in accordingly. If the file is missing, no error is produced, the blank/zero value will remain. |
Mon. February 3, 2020 | |
18.5.111 | When saving an HDA in unpacked format some per node data is now stored in separate files along side the Contents.mime file.
When reading an unpacked HDA (or converting it to packed) the values are first read from the files mentioned above and then filled in accordingly. If the file is missing, no error is produced, the blank/zero value will remain. |
Mon. February 3, 2020 | |
18.5.111 | When saving an HDA in unpacked format some per node data is now stored in separate files along side the Contents.mime file.
When reading an unpacked HDA (or converting it to packed) the values are first read from the files mentioned above and then filled in accordingly. If the file is missing, no error is produced, the blank/zero value will remain. |
Mon. February 3, 2020 | |
18.5.111 | When saving an HDA in unpacked format some per node data is now stored in separate files along side the Contents.mime file.
When reading an unpacked HDA (or converting it to packed) the values are first read from the files mentioned above and then filled in accordingly. For the timestamps, if the file is missing, no error is produced, the blank/zero value will remain. For the Contents.houdini_versions, if the file is needed (i.e. there are now values in Contents.mime set to "___EXTERNAL___") then an error is produced indicating the file is missing. |
Mon. February 3, 2020 | |
18.5.111 | When saving an HDA in unpacked format some per node data is now stored in separate files along side the Contents.mime file.
When reading an unpacked HDA (or converting it to packed) the values are first read from the files mentioned above and then filled in accordingly. For the timestamps, if the file is missing, no error is produced, the blank/zero value will remain. For the Contents.houdini_versions, if the file is needed (i.e. there are now values in Contents.mime set to "___EXTERNAL___") then an error is produced indicating the file is missing. |
Mon. February 3, 2020 | |
18.5.111 | When saving an HDA in unpacked format some per node data is now stored in separate files along side the Contents.mime file.
When reading an unpacked HDA (or converting it to packed) the values are first read from the files mentioned above and then filled in accordingly. For the timestamps, if the file is missing, no error is produced, the blank/zero value will remain. For the Contents.houdini_versions, if the file is needed (i.e. there are now values in Contents.mime set to "___EXTERNAL___") then an error is produced indicating the file is missing. |
Mon. February 3, 2020 | |
18.5.111 | When saving an HDA in unpacked format some per node data is now stored in separate files along side the Contents.mime file.
When reading an unpacked HDA (or converting it to packed) the values are first read from the files mentioned above and then filled in accordingly. For the timestamps, if the file is missing, no error is produced, the blank/zero value will remain. For the Contents.houdini_versions, if the file is needed (i.e. there are now values in Contents.mime set to "___EXTERNAL___") then an error is produced indicating the file is missing. |
Mon. February 3, 2020 | |
18.5.111 | Added support for specifying a custom serialization module name for PDG's Python Object attributes. The module name can be set using the type registry or with the PDG_PYATTRIB_LOADER environment variable. The module name is made available using that env. variable on the job-side as well, so that serialized work items can be loaded outside of the Houdini session. The module must have the dumps and loads functions, for saving and loading Python objects. Both the pickle and json modules that ship with Python support that interface and can be set as the PDG_PYATTRIB_LOADER. |
Mon. February 3, 2020 | |
18.5.111 | Added support for specifying a custom serialization module name for PDG's Python Object attributes. The module name can be set using the type registry or with the PDG_PYATTRIB_LOADER environment variable. The module name is made available using that env. variable on the job-side as well, so that serialized work items can be loaded outside of the Houdini session. The module must have the dumps and loads functions, for saving and loading Python objects. Both the pickle and json modules that ship with Python support that interface and can be set as the PDG_PYATTRIB_LOADER. |
Mon. February 3, 2020 | |
18.5.111 | Added support for specifying a custom serialization module name for PDG's Python Object attributes. The module name can be set using the type registry or with the PDG_PYATTRIB_LOADER environment variable. The module name is made available using that env. variable on the job-side as well, so that serialized work items can be loaded outside of the Houdini session. The module must have the dumps and loads functions, for saving and loading Python objects. Both the pickle and json modules that ship with Python support that interface and can be set as the PDG_PYATTRIB_LOADER. |
Mon. February 3, 2020 | |
18.5.111 | Added support for specifying a custom serialization module name for PDG's Python Object attributes. The module name can be set using the type registry or with the PDG_PYATTRIB_LOADER environment variable. The module name is made available using that env. variable on the job-side as well, so that serialized work items can be loaded outside of the Houdini session. The module must have the dumps and loads functions, for saving and loading Python objects. Both the pickle and json modules that ship with Python support that interface and can be set as the PDG_PYATTRIB_LOADER. |
Mon. February 3, 2020 | |
18.0.370 | Fixed warning message about sceneviewpurpose in non-GUI applications. |
Mon. February 3, 2020 | |
18.5.111 | Fixed warning message about sceneviewpurpose in non-GUI applications. |
Mon. February 3, 2020 | |
18.5.111 | Fixed warning message about sceneviewpurpose in non-GUI applications. |
Mon. February 3, 2020 | |
18.5.111 | Fixed warning message about sceneviewpurpose in non-GUI applications. |
Mon. February 3, 2020 | |
18.5.111 | Fixed warning message about sceneviewpurpose in non-GUI applications. |
Mon. February 3, 2020 | |
18.5.111 | Added initial support for OIDN (the Intel Denoiser) |
Mon. February 3, 2020 | |
18.5.111 | Added initial support for OIDN (the Intel Denoiser) |
Mon. February 3, 2020 | |
18.5.111 | Added initial support for OIDN (the Intel Denoiser) |
Mon. February 3, 2020 | |
18.5.111 | Added initial support for OIDN (the Intel Denoiser) |
Mon. February 3, 2020 | |
18.0.369 | OpenColorIO now generates 1D LUTs for display when possible, instead of always generating 3D LUTs. |
Sun. February 2, 2020 | |
18.5.110 | OpenColorIO now generates 1D LUTs for display when possible, instead of always generating 3D LUTs. |
Sun. February 2, 2020 |