Problem summary
Connections between single components of array parameters of certain shading node types seem to break when there is a shader is assigned to an object as well as that object’s parent location. This happens with the same shader assigned to parent and child and with different assigned shaders, as long as the shader with the problematic connection is assigned to the child object.
Customer reported version
Katana 2.5v5
Steps to reproduce
-
In the attached scene, click on the range node on the right’s output arrow (the node in the green backdrop) and connect out.r to the standard shading node’s Diffuse > Kd input.
-
Render the scene from the RenderSettings node. There should be two spheres visible in the render.
-
Disconnect the range node on the right and make the same connection from the range node on the left inside the red backdrop.
-
Render again from RenderSettings. One of the spheres now seems to have a broken shader and is only visible in the alpha, but not in the colour render.
Reproduced by support
Windows 7:
Katana 2.5v5, Arnold 4.2.14.2
RHEL 6.4:
Earliest tested version of Arnold that includes a range node is 4.2.7.4. I couldn’t find any examples of problematic nodes in earlier versions.
Katana 2.0v1, Arnold 4.2.7.4 & 4.2.8.0
Katana 2.0v5, Arnold 4.2.8.0
Katana 2.1v1, Arnold 4.2.8.0
Katana 2.1v5, Arnold 4.2.8.0
Katana 2.5v1, Arnold 4.2.8.0
Katana 2.5v5, Arnold 4.2.14.2
Expected behaviour
Connections between shading nodes shouldn’t break depending on shader assignments.
Actual behaviour
They break under certain circumstances.