Page MenuHome

Viewport graphics glitch in Eevee on macOS
Closed, ResolvedPublicBUG

Description

System Information
Operating system: Darwin-19.0.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon R9 M295X OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.0.52

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-18 14:52, hash: rB38d4483c6a51
Worked: (optional)

Short description of error
When using render in Eevee there is a 'perpetual image' glitch when the view or the object is changed. This also persists even when an object is deleted. Sometimes the object is pure black with just an outline.

Exact steps for others to reproduce the error
Switch into Eevee rendered in the viewport and either move the view or transform an object. The graphics of each state persist and build up into a multi image mess. Although this system is running macOS Catalina beta it was doing this before hand.








Event Timeline

Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 30.Jul 29 2019, 6:38 PM

Are you able to dual boot and test this on windows? I'm guessing that the mac gpu drivers are at fault here...

I’m not able to test on Windows as I don’t own a PC and have not created a Bootcamp partition (I have no room to do it). The graphic card drivers are updated with the macOS updates and are not available as separate downloads.

Sebastian Parborg (zeddb) raised the priority of this task from 30 to 80.Jul 30 2019, 10:31 AM

I cannot reproduce this on OSX 10.12.6

System Information
Operating system: Darwin-16.7.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon R9 M370X OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.51.8

Blender Version
version: 2.81 (sub 8), branch: master (modified), commit date: 2019-09-06 19:05, hash: rB9ecbd67dfb67

After a closer look I was able to reproduce it (somehow) in the viewport with the file . See also my system specs above.

Eitan Traurig (EitanSomething) changed the task status from Needs Information from Developers to Needs Information from User.Apr 30 2020, 6:01 PM

Is this still an issue with 2.83?

For me, the behaviour is the same in 2.80rc3, 2.81a and 2.90 today. neither can I redo the artefacts @Jean First (robbott) showed. Leaving open for some AMD testing.

Darwin-18.7.0-x86_64-i386-64bit 64 Bits
Graphics card: Intel(R) HD Graphics 6000 Intel Inc. 4.1 INTEL-12.10.12

Bastien Montagne (mont29) changed the subtype of this task from "Report" to "Bug".May 27 2020, 4:00 PM
Ankit Meel (ankitm) changed the task status from Needs Information from User to Confirmed.May 27 2020, 4:07 PM
Clément Foucault (fclem) closed this task as Resolved.Jun 24 2020, 5:48 PM
Clément Foucault (fclem) claimed this task.

This must have been fixed in the last 10 months. If anyone can still reproduce, I'll reopen the task.