Houdini Main Changelogs

18.0.428

When saving a hip file, only dirty nodes that use HIP, HIPFILE, or HIPNAME variables if those variable values actually change as a result of the save. Previously Houdini would always dirty node that use HIPNAME or HIPFILE.

Sun. April 5, 2020
18.0.427

Removed the Error nodes from the inside the ROP Geometry, ROP Alembic, ROP Composite, ROP Mantra and ROP USD TOP nodes. The warning message that was reported by the error node is now part of the ROP Fetch implementation itself. This fixes an issue with the work item topology in those ROP wrappers not working as expected when wired into a mapper.

Sat. April 4, 2020
18.0.427

Fixed an issue with ROP TOP nodes not dirtying when the target network was changed. For example, if the LOP network being cooked by a ROP USD Output TOP is modified, the TOP will now correctly be flagged as needing to dirty its work items on the next PDG graph cook.

Sat. April 4, 2020
18.5.172

Removed the Error nodes from the inside the ROP Geometry, ROP Alembic, ROP Composite, ROP Mantra and ROP USD TOP nodes. The warning message that was reported by the error node is now part of the ROP Fetch implementation itself. This fixes an issue with the work item topology in those ROP wrappers not working as expected when wired into a mapper.

Sat. April 4, 2020
18.5.172

Removed the Error nodes from the inside the ROP Geometry, ROP Alembic, ROP Composite, ROP Mantra and ROP USD TOP nodes. The warning message that was reported by the error node is now part of the ROP Fetch implementation itself. This fixes an issue with the work item topology in those ROP wrappers not working as expected when wired into a mapper.

Sat. April 4, 2020
18.5.172

Removed the Error nodes from the inside the ROP Geometry, ROP Alembic, ROP Composite, ROP Mantra and ROP USD TOP nodes. The warning message that was reported by the error node is now part of the ROP Fetch implementation itself. This fixes an issue with the work item topology in those ROP wrappers not working as expected when wired into a mapper.

Sat. April 4, 2020
18.5.172

Removed the Error nodes from the inside the ROP Geometry, ROP Alembic, ROP Composite, ROP Mantra and ROP USD TOP nodes. The warning message that was reported by the error node is now part of the ROP Fetch implementation itself. This fixes an issue with the work item topology in those ROP wrappers not working as expected when wired into a mapper.

Sat. April 4, 2020
18.5.172

Fixed an issue with ROP TOP nodes not dirtying when the target network was changed. For example, if the LOP network being cooked by a ROP USD Output TOP is modified, the TOP will now correctly be flagged as needing to dirty its work items on the next PDG graph cook.

Sat. April 4, 2020
18.5.172

Fixed an issue with ROP TOP nodes not dirtying when the target network was changed. For example, if the LOP network being cooked by a ROP USD Output TOP is modified, the TOP will now correctly be flagged as needing to dirty its work items on the next PDG graph cook.

Sat. April 4, 2020
18.5.172

Fixed an issue with ROP TOP nodes not dirtying when the target network was changed. For example, if the LOP network being cooked by a ROP USD Output TOP is modified, the TOP will now correctly be flagged as needing to dirty its work items on the next PDG graph cook.

Sat. April 4, 2020
18.5.172

Fixed an issue with ROP TOP nodes not dirtying when the target network was changed. For example, if the LOP network being cooked by a ROP USD Output TOP is modified, the TOP will now correctly be flagged as needing to dirty its work items on the next PDG graph cook.

Sat. April 4, 2020
18.5.172

When saving a hip file, only dirty nodes that use HIP, HIPFILE, or HIPNAME variables if those variable values actually change as a result of the save. Previously Houdini would always dirty node that use HIPNAME or HIPFILE.

Sat. April 4, 2020
18.5.172

When saving a hip file, only dirty nodes that use HIP, HIPFILE, or HIPNAME variables if those variable values actually change as a result of the save. Previously Houdini would always dirty node that use HIPNAME or HIPFILE.

Sat. April 4, 2020
18.5.172

When saving a hip file, only dirty nodes that use HIP, HIPFILE, or HIPNAME variables if those variable values actually change as a result of the save. Previously Houdini would always dirty node that use HIPNAME or HIPFILE.

Sat. April 4, 2020
18.5.172

When saving a hip file, only dirty nodes that use HIP, HIPFILE, or HIPNAME variables if those variable values actually change as a result of the save. Previously Houdini would always dirty node that use HIPNAME or HIPFILE.

Sat. April 4, 2020
18.0.426

The Python Script TOP can now be configured to evaluate its script code during the work item generation step instead of when the work items are cooking. That option is now available as one of three entries in a newly added "Evaluate Code During" parameter, which has replaced the In-Process toggle. It can be used to, for example, programmatically create attributes using PDG's Python API.

Fri. April 3, 2020
18.0.426

Fixed crash when updating materials in 3ds Max that were exported from Houdini via a geometry Hda.

Fri. April 3, 2020
18.5.171

The Python Script TOP can now be configured to evaluate its script code during the work item generation step instead of when the work items are cooking. That option is now available as one of three entries in a newly added "Evaluate Code During" parameter, which has replaced the In-Process toggle. It can be used to, for example, programmatically create attributes using PDG's Python API.

Fri. April 3, 2020
18.5.171

The Python Script TOP can now be configured to evaluate its script code during the work item generation step instead of when the work items are cooking. That option is now available as one of three entries in a newly added "Evaluate Code During" parameter, which has replaced the In-Process toggle. It can be used to, for example, programmatically create attributes using PDG's Python API.

Fri. April 3, 2020
18.5.171

The Python Script TOP can now be configured to evaluate its script code during the work item generation step instead of when the work items are cooking. That option is now available as one of three entries in a newly added "Evaluate Code During" parameter, which has replaced the In-Process toggle. It can be used to, for example, programmatically create attributes using PDG's Python API.

Fri. April 3, 2020
18.5.171

The Python Script TOP can now be configured to evaluate its script code during the work item generation step instead of when the work items are cooking. That option is now available as one of three entries in a newly added "Evaluate Code During" parameter, which has replaced the In-Process toggle. It can be used to, for example, programmatically create attributes using PDG's Python API.

Fri. April 3, 2020
18.5.171

Fixed crash when updating materials in 3ds Max that were exported from Houdini via the geometry Hda.

Fri. April 3, 2020
18.5.171

Fixed crash when updating materials in 3ds Max that were exported from Houdini via the geometry Hda.

Fri. April 3, 2020
18.5.171

Fixed crash when updating materials in 3ds Max that were exported from Houdini via the geometry Hda.

Fri. April 3, 2020
18.5.171

Fixed crash when updating materials in 3ds Max that were exported from Houdini via the geometry Hda.

Fri. April 3, 2020