ID 390882 - Material groups that have been placed inside a folder aren't properly recognised by the Polygon Set Material window.

Problem summary
Material groups that have been placed inside a folder aren't properly recognised by the Polygon Set Material window.

On the Polygon Set Material window, when you select a material group that's inside a folder on the Shader Tree and press OK, a duplicate material group is created in the Shader Tree using the values of the previously selected material within the Polygon Set Material window.

Customer reported version
modo.13.0v1

Customer reported platform
10.13

Steps to reproduce

1) Launch Modo and select Geometry>Primitive Tools>Cube, create a cube within the 3D (OpenGL) Viewport.

2) Enable Polygons mode and select 2 polygons on the cube, then press the M key. This opens the Polygon Set Material window.

3) Within the window select a green colour and name it 'Green', select OK.

​

4) Navigate to the Shader Tree and select Add Layer>Folder, you may need to drag this folder above the Base Material.

5) Place the Green material group inside the folder.

​

6) Select 2 other polygons on the cube and again press the M key.

7) Set a blue colour and name it 'Blue', select OK.

8) Select the last 2 polygons that you haven't had a material assigned to yet.

9) Press the M key and select 'Green' from the list and notice how the Color field doesn't change, select OK.

​

10) Check the Shader Tree and see that another Green material group has been created with a different Diffuse Color.

​

Expected behaviour
The Polygon Set Material window should set the polygons material to the 'Green' material group within the folder.

Actual behaviour
The Polygon Set Material window creates a duplicate 'Green' material group using its current selections.

Workaround
Unknown.

Reproduced by support

This bug has been reproduced in:
Modo 13.0v1 - Windows 10 - Centos 7 - MacOS 10.13

Modo 12.2v2 - Windows 10

Modo 12.1v2 - Windows 10

Modo 12.0v1 - Windows 10

Modo 11.2v3 - Windows 10

Modo 11.2v1 - Windows 10

Unable to reproduce bug in:

Modo 11.1v1 - Windows 10 - Centos 7 - MacOS 10.13

Earliest version tested

Modo 11.1v1 - This feature did not exist before this version