ID 233352 - Some inherited PrmanGlobalSetting parameters show incorrect state badges and act as if locally set

For certain values that are set in the Parameters tab of a PrmanGlobalSettings node, another PrmanGlobalSettings node downstream will not show the correct state badge and the value is treated as if it was set locally rather than inherited. See attached Katana scene.

 

These values, like

prmanGlobalSettings.commandArguments.riFilters

prmanGlobalSettings.commandArguments.woff

 

will have a state badge indicating, incorrectly, that they have a locally set value when the value is actually inherited from upstream:

 

 

Setting the value back to default in the upstream PrmanGlobalSettings node also doesn’t remove the value from the parameter in the downstream node.

 

This only happens with certain parameters, others, for example camera.projection, will correctly be shown as inherited and will change downstream when they are changed upstream in the node where they are initially set:

 

 

 

1) Open Katana, add a CameraCreate and a PrmanGlobalSettings node.

 

2) Set prmanGlobalSettings.commandArguments.riFilters to some value

 

3) Add another PrmanGlobalSettings node downstream of the first one and examine the commandArguments.riFilters parameter value. It is shown like a locally set value.

 

4) Set the parameter back to default in the upstream node and examine the downstream one again. The previous value is still there, flagged as being set locally.

 

Unknown.

 

Reproduced in 2.0v1, 2.0v5, 2.1v4, 2.5v3 on RHEL 6.6

Does not happen in 1.6v3 (all inherited values show correct state badges and act like inherited values)

 

Inherited values should be show that they are inherited on their state badge in downstream nodes and when the value changes in the node where they are initially set, it should also change in all PrmanGlobalSettings nodes downstream

 

The value of some parameters is retained and they are shown as locally set