Problem summary
Empty ShadingGroup/Group nodes which have a connected input and output port that share the same name causes Katana to crash when the View flag is set on the node/downstream.
Customer reported version
Katana 6.5v5
Customer reported platform
Alma 9
Steps to reproduce
NetworkMaterialCreate Example:
1) Create a NetworkMaterialCreate node and enter it.
2) Create a ShadingGroup node and enter it.
3) Create a dlStandard node and connect the Parameters > Base > Color port to the input terminal of your Shading Group.
4) Delete the dlStandard node and then connect the input terminal port to the output terminal to create a matching port.
5) Exit the ShadingGroup node and create a new dlStandard node.
6) Connect the output port of the ShadingGroup node to the Parameters > Base > Color input port on the dlStandard node.
7) Exit the NetworkMaterialCreate context and set the View flag on the node.
Expected behaviour
Katana cooks the scene and populates the Scene Explorer tab with the hierarchy.
Actual behaviour
Katana freezes and then eventually crashes.
Workaround
Create a Dot node within the Empty Shading Group node to ensure a node exists between the two matching port names.
Reproduced by support
This bug has been reproduced in:
Katana 6.0v6 - Windows 11 / CentOS7
Katana 6.5v5 - Windows 11 / CentOS7
Katana 6.5v6 - Windows 11 / CentOS7
Katana 7.0v5 - Windows 11 / Rocky 9
Katana 7.0v6 - Windows 11 / Rocky 9
Katana 7.5v2 - Windows 11 / Rocky 9
Katana 8.0v2 - Windows 11 / Rocky 9
Unable to reproduce bug in:
Katana 6.0v5 - Windows 11 / CentOS7
Katana 6.5v4 - Windows 11 / CentOS7
Katana 7.0v4 - Windows 11 / Rocky 9
Katana 7.5v1 - Windows 11 / Rocky 9
Katana 8.0v1 - Windows 11 / Rocky 9
Earliest version tested
Katana 6.0v5 - This issue doesn't appear in this version and has regressed