Workbench: display corrupted in 2.91 with file from 2.90 #83039

New Issue

Ben Thery · 2020-11-26T09:51:05+01:00

Ben Thery commented

2020-11-26 09:51:05 +01:00

System Information
Operating system: Windows 10
Graphics card: AMD Radeon Vega 8 (driver: 19.10.02.13 and 20.9.1)
CPU: AMD Ryzen 5 3500U

Blender Version
Broken: 2.91.0
Worked: 2.90.1

Short description of error

When I open a file created in Blender 2.90.1 with the new Blender 2.91 in workbench mode the display of transparent materials (alpha set in material shader viewport properties) is corrupted: no transparency, just a bunch of "random" pixels (see window in first screenshot).

Then, when I enable x-ray mode, all the viewport display becomes corrupted (see second screenshot).

Note: the issue doesn't appear if I create a new file in 2.91. It seems to only happen with the file I created initially in Blender 2.90.1 (bad settings saved in file ?).

Exact steps for others to reproduce the error
Load attached .blend file in Blender 2.91

fenetre-02.blend

**System Information** Operating system: Windows 10 Graphics card: AMD Radeon Vega 8 (driver: 19.10.02.13 and 20.9.1) CPU: AMD Ryzen 5 3500U **Blender Version** Broken: 2.91.0 Worked: 2.90.1 **Short description of error** When I open a file created in Blender 2.90.1 with the new Blender 2.91 in workbench mode the display of transparent materials (alpha set in material shader viewport properties) is corrupted: no transparency, just a bunch of "random" pixels (see window in first screenshot). ![blender-2.91-workbench-corruption-alpha-material.jpg](https://archive.blender.org/developer/F9379159/blender-2.91-workbench-corruption-alpha-material.jpg) Then, when I enable x-ray mode, all the viewport display becomes corrupted (see second screenshot). ![blender-2.91-workbench-corruption-alpha-material-xray-enabled.jpg](https://archive.blender.org/developer/F9379165/blender-2.91-workbench-corruption-alpha-material-xray-enabled.jpg) **Note:** the issue **doesn't appear if I create a new file in 2.91**. It seems to only happen with the file I created initially in Blender 2.90.1 (bad settings saved in file ?). **Exact steps for others to reproduce the error** Load attached .blend file in Blender 2.91 [fenetre-02.blend](https://archive.blender.org/developer/F9379179/fenetre-02.blend)

Ben Thery commented

2020-11-26 09:51:05 +01:00

Added subscriber: @oxben

Ben Thery commented

2020-11-26 10:24:37 +01:00

May be similar to the issue reported in #83022, but in my case it only happens with files from previous version.
It works fine with default cube in new scene created in 2.91.

May be similar to the issue reported in #83022, but in my case it only happens with files from previous version. It works fine with default cube in new scene created in 2.91.

Robert Guetzkow commented

2020-11-26 10:29:48 +01:00

Added subscriber: @rjg

Robert Guetzkow commented

2020-11-26 10:29:48 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Robert Guetzkow commented

2020-11-26 10:29:48 +01:00

I can't reproduce this with a Nvidia GPU. Could you please check what driver version you're using? If you're using an older driver, please update it. Don't use version 20.11.2 though, as this version is known to cause issues (see #82856).

Ben Thery commented

2020-11-26 10:38:45 +01:00

I'll try to update the drivers. But I said above, it works fine if I create a new scene in 2.91, that's why suspect an issue in the process that loads the file from 2.90.1 which probably initialize badly a data structure.

Robert Guetzkow commented

2020-11-26 10:57:20 +01:00

Just for reference regarding problems with viewport display alpha, there is an issue with how it is stored as identified in #82514.

Ben Thery commented

2020-11-26 11:03:47 +01:00

As requested, I've updated the Radeon drivers to 20.9.1. The issue is still present when loading the "old" Blender file.

Philipp Oeser commented

2020-11-26 11:18:53 +01:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Julian Mohr commented

2020-11-26 11:23:07 +01:00

Added subscriber: @Jewls

Julian Mohr commented

2020-11-26 11:23:07 +01:00

works fine with 2.91 and 2.92 (Nvidea Gpu & windows). Seems AMD related.

works fine with 2.91 and 2.92 (Nvidea Gpu & windows). Seems AMD related. ![2.92.PNG](https://archive.blender.org/developer/F9379742/2.92.PNG)

Stas Haas commented

2020-11-26 12:40:26 +01:00

Added subscriber: @girafic

Stas Haas commented

2020-11-26 12:40:26 +01:00

Works fine with OSX and AMD in 2.91 and 2.92.

Works fine with OSX and AMD in 2.91 and 2.92. ![Bildschirmfoto 2020-11-26 um 12.36.24.png](https://archive.blender.org/developer/F9380312/Bildschirmfoto_2020-11-26_um_12.36.24.png)

Star Weaver commented

2020-11-26 14:23:37 +01:00

Added subscriber: @starweaver

Star Weaver commented

2020-11-26 14:23:37 +01:00

I'm also having this problem. I managed to reduce it to a file with 2 meshes, 4 objects, 2 scenes, and 1 material. Things I've learned:

New objects in a new scene in an old file are not affected.
Old objects added to a new scene in- or cross-file cause it to fail.
Changing a good object's mesh pointer to an old mesh causes it to fail.
Changing out and back into a scene after removing offending objects from it causes failure to clear.
There needs to be a transparent-in-viewport material in the scene for it to fail, but that can be a working material on a new good object that only fails in the presence of a bad old object with no material of its own.
I even get HOM effects on some of my 3d viewports. But not all. No idea what the difference is.

Minimal Failure.blend

Reproduction: File will load on bad scene. Switch to good scene and problem should clear. Change a good object to point to bad mesh and it should fail again. Remove references to bad mesh and it should clear again on scene load.

System: AMD Ryzen 7 1800X & Radeon R9 380
Drivers: 20.11.2 (I only read it was bad just after installing) and also 19.something

I had this problem a few weeks ago when I tried the betas but figured it was a one-off that would be fixed soon and went back to stable.

Oh, and I couldn't find any notable differences between the two meshes in the DNA view.
So far, all of my attempts to get the data out of one of these files and into 2.91 safely have failed. This has included exporting from 2.91 in .abc, .dae, and .fbx, and from 2.90 in .abc; it still breaks transparant shading when you import any of these into 2.91.

I'm also having this problem. I managed to reduce it to a file with 2 meshes, 4 objects, 2 scenes, and 1 material. Things I've learned: - New objects in a new scene in an old file are not affected. - Old objects added to a new scene in- or cross-file cause it to fail. - Changing a good object's mesh pointer to an old mesh causes it to fail. - Changing out and back into a scene after removing offending objects from it causes failure to clear. - There needs to be a transparent-in-viewport material in the scene for it to fail, but that can be a working material on a new good object that only fails in the presence of a bad old object with no material of its own. - I even get HOM effects on some of my 3d viewports. But not all. No idea what the difference is. [Minimal Failure.blend](https://archive.blender.org/developer/F9380839/Minimal_Failure.blend) Reproduction: File will load on bad scene. Switch to good scene and problem should clear. Change a good object to point to bad mesh and it should fail again. Remove references to bad mesh and it should clear again on scene load. System: AMD Ryzen 7 1800X & Radeon R9 380 Drivers: 20.11.2 (I only read it was bad just after installing) and also 19.something I had this problem a few weeks ago when I tried the betas but figured it was a one-off that would be fixed soon and went back to stable. - Oh, and I couldn't find any notable differences between the two meshes in the DNA view. - So far, all of my attempts to get the data out of one of these files and into 2.91 safely have failed. This has included exporting from 2.91 in .abc, .dae, and .fbx, and from 2.90 in .abc; it still breaks transparant shading when you import any of these into 2.91.

Ben Thery commented

2020-11-26 18:32:14 +01:00

This ticket is probably a duplicate of #83022.

Initially I thought it was an import issue from 2.90.1 file, but I can now reproduce it on a new blank scene in 2.91.

As describe in #83022, the trick is really to have two objects: one with a material with viewport alpha set to 1.0, another with viewport alpha < 1.0. Two default cubes are sufficient.

This ticket is probably a duplicate of #83022. Initially I thought it was an import issue from 2.90.1 file, but I can now reproduce it on a new blank scene in 2.91. As describe in #83022, the trick is really to have two objects: one with a material with viewport alpha set to 1.0, another with viewport alpha < 1.0. Two default cubes are sufficient.

Robert Guetzkow commented

2020-11-26 18:36:13 +01:00

Closed as duplicate of #83022

Robert Guetzkow closed this issue

2020-11-26 18:36:13 +01:00

Robert Guetzkow commented

2020-11-26 18:36:16 +01:00

I'll merge the tickets then.

Stas Haas commented

2020-11-28 00:26:43 +01:00

So, I've tested this file with Windows 10 and Blender 2.91. Same bug also occurs here with AMD.

Blender_2_91_Windows10_AMD_.mp4

So, I've tested this file with Windows 10 and Blender 2.91. Same bug also occurs here with AMD. [Blender_2_91_Windows10_AMD_.mp4](https://archive.blender.org/developer/F9393507/Blender_2_91_Windows10_AMD_.mp4)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Workbench: display corrupted in 2.91 with file from 2.90 #83039