ID 336080 - GafferThree nodes showing incoming scene do not take Graph State Variables into account

Problem summary

When using local Graph State Variables and VariableSwitch nodes to control which of several GafferThree nodes is used, downstream GafferThree nodes showing the incoming scene may not show the correct lights in their UI.

Customer reported version

Katana 2.6

Customer reported platform

Not supplied

Steps to reproduce

1. Open the attached Katana scene.
   Enable Dim Nodes Not Contributing to Viewed Node in the Node Graph tab’s Edit menu to see clearly which input ports are currently selected.

2. Set the View flag on the VariableSet_passB node to set the variable for the upstream node graph.

3. Set the Edit flag on the GafferThree_B_override node and inspect its UI.
   Result: The GafferThree UI contains the light created in GafferThree_A, even though the input from GafferThree_B should be used and the light shown in the GafferThree_B_override UI does not exist in the Scene Graph.

Workaround

Unknown

Reproduced by support

Katana 2.6v3 - Windows 10

Katana 2.6v4 - CentOS 7

Expected behaviour

The downstream GafferThree node should show the correct incoming scene as produced by the node graph, taking into account node inputs controlled by VariableSwitch nodes.

Actual behaviour

The downstream GafferThree node shows the incoming scene as produced by the leftmost input on the VariableSwitch node, even if this is not the input that is currently being used to generate the scene data.