ID 390684 - RGBA images only render in the 3D (OpenGL) Viewport if the Image item is selected in the Shader Tree.

Problem summary
RGBA images only render in the 3D (OpenGL) Viewport if the Image item is selected in the Shader Tree.

The only 3D (OpenGL) Viewport style that this issue isn't present is in the Advanced viewport style.

Other options within Effects work correctly.

Customer reported version
modo.13.0v1

Customer reported platform
windows10

Steps to reproduce

1) Launch Modo, and select Geometry>Primitive Tools>Cube, then left click and drag within the 3D (OpenGL) Viewport.

2) Press N to create a new mesh layer and repeat the previous step, there should now be two meshes within the 3D (OpenGL) Viewport.

​

3) Select the first mesh and press M this will bring up the Polygon Set Material window, name it Mesh1 and select OK.

4) Now select the second mesh and press M again this will bring up the Polygon Set Material window, name it Mesh2 and select OK.

5) Navigate to the Shader Tree and select Mesh1, now select Add Layer>Image Map>(load image) and select an image file.

6) Now select Mesh2 and once again select Add Layer>Image Map>(load image) and select an image file.

7) Notice how they both render within the 3D (OpenGL) Viewport.

​

8) Now set the Effect of both images to RGBA and notice how the image only renders if the image is selected. 

​

Expected behaviour
When both images are set to RGBA they should both be rendered within the 3D (OpenGL) Viewport.

Actual behaviour
The RGBA images need to be selected in order for them to render within the 3D (OpenGL) Viewport.

Workaround
If you set the 3D (OpenGL) Viewport style to Advanced both RGBA images will be rendered within the viewport.

​

You may also need to enable Make Inactive Items Same As Active, to do this press O and navigate to the Inactive Meshes tab. Now enable this override and the inactive items should also be rendered within the viewport.

​

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.1v1 - Windows 10

Modo 11.0v3 - Windows 10

Modo 10.2v4 - Windows 10 - Centos 7 - MacOS 10.13

Earliest version tested
Modo 10.2v4 - This issue appears to be in all versions of the product