State:Closed|icon_bug|icon_katana|database:public|Resolution:Fixed|TargetRelease:3.0v5|BugID:354556|
Problem summary:
The getGraphState() function that is available on all Katana node types is meant to return the Graph State accumulated between a particular given Node instance and the respective Node on which the function is called. Typically, the current view node is passed as the Node at which to start the traversal of nodes in the node graph.
Currently, the function only considers Graph State modifications that are performed via overrides of the getLogicalInputPort() function in node type classes that are implemented in C++, such as TimeOffset and VariableSwitch. The getGraphState() function does not currently consider modifications of local Graph State that are made via input requests in functions that build the Op chain of a custom node type that is implemented in Python using NodeTypeBuilder.
Steps to reproduce:
Expected behaviour:
The Graph State Variables popup ilsts the following two Graph State Variables in the Locals section:
The message printed includes both of the local Graph State Variables in the variables group:
<GroupAttribute: childCount=2> {
timeSlice = {
currentTime = FloatAttribute(1.0),
shutterOpen = FloatAttribute(0.0),
shutterClose = FloatAttribute(1.0),
numSamples = IntAttribute(1),
},
variables = {
sequence = StringAttribute("seq050"),
shot = StringAttribute("s002"),
},
} Actual behaviour:
The Locals section in the Graph State Variables popup only shows the shot variable.
The sequence variable is not listed.
The output in the shell as shown above is correct.
Workaround:
No known workaround.
Tested versions/platforms:
Customer version/platform:
Not supplied
We're sorry to hear that
Please tell us why