Page MenuHome

Viewport/crash artefacts with multiple materials and legacy NVIDIA drivers
Open, Confirmed, HighPublic

Description

System Information
Operating system: Linux-4.19.87-1-lts-x86_64-with-glibc2.29 64 Bits
Graphics card: GeForce GTX 275/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.107

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce 410M/PCIe/SSE2 NVIDIA Corporation 4.3.0

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce 210/PCIe/SSE2 NVIDIA Corporation 3.3.0

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: Quadro FX 4800/PCIe/SSE2 NVIDIA Corporation 3.3.0

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: Quadro FX 3800/PCIe/SSE2 NVIDIA Corporation 3.3.0

Short description of error
Drawing error with multi-material object. Faces dissapear or showing artefacts with 2 or more material slots applyed to same object

System Information
Operating system: Linux-5.0.0-36-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GT 220/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.107

Description:
When trying to use a second material or more on an object, the faces where it is applied become transparent or in some cases they are distorted as black rectangles that stretch to the origin (this second occurs above all with more complex models than a cube). This bug is noticed in edit mode or object, obviously if in viewport shading the option of material color or texture is used. In the other color modes of the Viewport Shading as Object, Vertex, Single or Random, the meshes of the object are displayed without the errors mentioned above. It happens in Blender 2.81 as well as in Blender 2.82, but in Blender 2.80 there is no such error.


Event Timeline

I tried to uninstalled and download many times but I can not click on material icon.When I clicked on material menu and the programme turn off immediately every times.How should I solved this problem.

Thank you

Stephen Swaney (stiv) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Nov 14 2019, 4:15 PM

Missing information:

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

Maciej Jutrzenka (Kramon) renamed this task from Material menu has problem to Windows 7 - Viewport/Crash artefacts when multiple materials on 1 object.Tue, Nov 26, 3:49 PM
Maciej Jutrzenka (Kramon) raised the priority of this task from Needs Information from User to Needs Triage by Developer.
Maciej Jutrzenka (Kramon) updated the task description. (Show Details)
Maciej Jutrzenka (Kramon) updated the task description. (Show Details)
Maciej Jutrzenka (Kramon) renamed this task from Windows 7 - Viewport/Crash artefacts when multiple materials on 1 object to Viewport/Crash artefacts when multiple materials on 1 object.Wed, Nov 27, 1:42 AM
Maciej Jutrzenka (Kramon) updated the task description. (Show Details)
Maciej Jutrzenka (Kramon) renamed this task from Viewport/Crash artefacts when multiple materials on 1 object to Viewport/Crash artefacts when multiple materials on 1 object [MERGED 4 Reports].Wed, Nov 27, 1:51 AM
Maciej Jutrzenka (Kramon) updated the task description. (Show Details)

There was similar bug report about this
https://developer.blender.org/T70106

but apperantly got fixed but apperantly it is still bugged? or is it just old GPU's

On Twitter I uploaded a video showing how the bug appears in Blender 2.81 and not in Blender 2.80
https://twitter.com/Gaonirico/status/1199367836440973314?s=20

so i guess it's an issue with old drivers.

@Maciej Jutrzenka (Kramon) I think it would. if you want to test (and can compile blender) change this line
#if !defined(GPU_INTEL) && !defined(GPU_DEPRECATED_AMD_DRIVER) && !defined(OS_MAC)
to this
#if 0

@Clément Foucault (fclem) sadly i don't have that kind of GPU's and i am not familiar with custom builds.. But if the issiue on MAC was exactly 1:1 the same.. so i think this should fix also those problems.. i think if we are gona do 2.81a it would be good idea to include this also for wind/linux

Well this fix has some issue as it cripple down the performance. So it should be limited to broken/end of life systems.

What I can see is that it only affect really old GPUs with legacy driver (correct me if i'm wrong) so we maybe need to limit this to old Nvidia drivers.

Clément Foucault (fclem) lowered the priority of this task from Needs Triage by Developer to Confirmed, High.Wed, Nov 27, 8:15 PM

i think we can set it for nvidia 3.3.0 driver and older.

Does running with --debug-gpu-force-workarounds (or use the script blender_debug_gpu_glitchworkaround.cmd) fixes the issue?

I've prepared D6351 to fix this issue but it does not seems 100% safe (to me) and I still don't know if it fixes the issue.

Maciej Jutrzenka (Kramon) renamed this task from Viewport/Crash artefacts when multiple materials on 1 object [MERGED 4 Reports] to Viewport/Crash artefacts when multiple materials on 1 object [MERGED 5 Reports].Fri, Dec 6, 6:13 PM
Maciej Jutrzenka (Kramon) updated the task description. (Show Details)
Maciej Jutrzenka (Kramon) updated the task description. (Show Details)
This comment was removed by Maciej Jutrzenka (Kramon).
Brecht Van Lommel (brecht) renamed this task from Viewport/Crash artefacts when multiple materials on 1 object [MERGED 5 Reports] to Viewport/crash artefacts with multiple materials and legacy NVIDIA drivers.Fri, Dec 6, 6:30 PM

@Clément Foucault (fclem) I'm running Archlinux with the 340xx driver, so I'll make blender with this settup and try it out, btw where's that line I have to edit?

so i guess it's an issue with old drivers.
@Maciej Jutrzenka (Kramon) I think it would. if you want to test (and can compile blender) change this line
#if !defined(GPU_INTEL) && !defined(GPU_DEPRECATED_AMD_DRIVER) && !defined(OS_MAC)
to this
#if 0