Problem summary
Nesting ShadingGroup nodes and connecting their inputs upstream heavily impacts performance at depths between the top-most ShadingGroup and the bottom of the hierarchy
Customer reported version
Katana 3.5v3
Customer reported platform
CentOS 7
Steps to reproduce
1) Launch Katana w/ Arnold
2) Open attached scene file
3) In the Node Graph traverse into NetworkMaterialCreate->ShadingGroup
4) Select ShadingGroup1 and ShadingGroup2
5) Run the attached
script in the Python tab
Notes:
- Performance impact scales, copy/paste ShadingGroup1 and ShadingGroup2 and connect the new nodes using attached script for more visible impact
- Issue still occurs after removing all non-ShadingGroup nodes in the scene - See attached OSN scene
Expected behaviour
Katana remains performant at all depths of the NetworkMaterialCreate hierarchy
Actual behaviour
Performance is significantly reduced between the top-most ShadingGroup and the bottom of the hierarchy
Workaround
Unknown.
Reproduced by support
This bug has been reproduced in:
3.6v1 - Windows 10 - CentOS 7
3.5v3 - Windows 10 - CentOS 7
3.5v1 - Windows 10 - CentOS 7
3.2v4 - Windows 10 - CentOS 7
3.2v1 - Windows 10 - CentOS 7
Earliest version tested
3.2v1 - This feature did not exist before this version -
What's new in Katana 3.2