ID 546700 - The NetworkMaterialEdit node corrupts when editing a Children Material Location that has a parent containing an exposed parameter with a Widget Type set to Mapping Popup Menu while changing the value from a float to a string.

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Katana

Problem summary
The NetworkMaterialEdit node corrupts when editing a Children Material Location that has a parent containing an exposed parameter with a Widget Type set to Mapping Popup Menu while changing the value from a float to a string.
 
Customer reported version
Katana.6.0v2
 
Customer reported platform
CentOs7
 
Steps to reproduce
 

  1. Create a NetworkMaterialCreate node and go inside the NetworkMaterialCreate node and add a "dlStandard" and expose the base weight parameter by clicking in the wrench icon and selecting "Add to Material Interface".
  2. Click on the wrench icon and select Widget Type and change it to Mapping Popup Menu, click on the wrench icon and select Widget Options change the Popup options in the first box to any string value.

  3. Then create a Material node downstream from the NetworkMaterialCreate and set it to "create children material" and set its location to the previously created Network Material.

  4. Create a Network Material Edit node and connect that downstream from the Material node and go to Sources & Order.
 
Expected behaviour
I would expect for any Material that were exposed to appear in the parameters tab of the NetworkMaterialEdit and for the exposed parameters to also appear in the Sources & Order tab.
 
Actual behaviour
All parameters get hidden in NetworkMaterialEdit node and an error occurs "NetworkMaterialEdit: Op: Error getting string value from StringAttribute." in the Sources & Order tab of the NetworkMaterialEdit node.
 
Workaround
Unknown.
 
Reproduced by support
This bug has been reproduced in:
Katana 6.0v2 - Windows 10, CentOs 7
 
Unable to reproduce bug in:
Katana 6.0v1 - Windows 10, CentOs 7
Katana 5.0v5 - Windows 10, CentOs 7
 
Earliest version tested
Katana 6.0v1 - This issue doesn't appear in this version and has regressed
 

    We're sorry to hear that

    Please tell us why