Page MenuHome

Drawing artifacts in the Blender UI on macOS
Needs Developer to Reproduce, HighPublic


System Information
Operating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits
Graphics card: Intel(R) UHD Graphics 630 Intel Inc. 4.1 INTEL-14.6.18
Intel UHD Graphics 630 1536 MB (internal) @Gabriel Zagury (zodecky)
Intel(R) Iris(TM) Plus Graphics 655 @Christoph Schmitz (chr.schmitz)
Intel(R) HD Graphics 615 @Alan Taylor (skororu)

Blender Version
Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-06-25 21:53, hash: rB62aa103d485f

Short description of error
Drawing artifacts in the Blender UI.

Exact steps for others to reproduce the error
Launch Blender on macOS

Event Timeline

Looks like the kind of glitches in T78256

This comment was removed by hujin (MAXMADZZ).

I do not know whether this information helps, but I want to report it anyhow. The problem first appeared on my system after I updated from macOS 10.15.6 to macOS 11.0 DevBeta1.

I see, obviously, this happened coincidentally.

macOS 10.15.5 Catalina, MacBook Retina 12" 2017, 8GB, HD615
ec776f18ff70, build date: 2020-06-24, 23:04:37

This was introduced a week or so ago, master daily builds were certainly working fine before that. I can see the issue OP reported on both 10.14.6 and 10.15.5.

I was having the same issue when I downloaded 2.9 Alpha last night.

On the -modifier ui branch (June 28) the issue doesn't happen


Ankit (ankitm) changed the task status from Needs Triage to Confirmed.EditedSun, Jun 28, 10:12 PM
Ankit (ankitm) triaged this task as High priority.

This was introduced a week or so ago, master daily builds were certainly working fine before that.

Looks like a recent change, so marking high.

Can't reproduce this on Catalina 10.15.5 here. However, Blender runs on my Radeon Pro.

For those who can reproduce: Is it possible that you only have the integrated Intel GPU?
(You can use HelpSave System Info in Blender to double check which GPU Blender runs on.)

Yes, I have a MacBook Pro 13 inch with an Intel Iris Plus 655 (1635 MB RAM). Attached you will find my system-info.txt.

Alan Taylor (skororu) added a comment.EditedWed, Jul 1, 3:15 PM

It looks like this issue was introduced in 15dda0115c78; the UI is fine with the previous commit (3cea42ce29cb).

+1 for the core developers for the current state of the dependency installation and source in general: I hadn't needed to compile Blender for a few years, and it was much easier this time round.

If anyone is willing to try my hotfix, I've kicked the buildbot so the new build should be up in ~20min.

Tried with build 35, blender-2.90.0-b0da78084bd7-macOS, and the issue is still there (MacBook Air with Intel Iris Plus graphics)

I compiled Blender this morning, but the bug is still present (MacBook Pro with Intel(R) Iris(TM) Plus Graphics 655).

Sadly still persists for me, too. Macbook Pro, Intel Iris Plus Graphics 1536 MB.

The patch solved the issue in macOS 10.15.5 Catalina.

In macOS 11 Big Sur (Dev Beta 1 and 2) it is resolved in the 3D viewport, but not in all panels (see attached screenshots).

@Christoph Schmitz (chr.schmitz) is that Big Sur on an old mac or on the devkit? if the latter, don't worry we have the hardware.

macOS Big Sur 11.0 Beta (20A4300b) is running on a MacBook Pro (13-inch, 2018, Four Thunderbolt 3 Ports), 2,7 GHz Quad-Core Intel Core i7, 16 GB 2133 MHz LPDDR3, Intel Iris Plus Graphics 655 1536 MB.

A few days ago I tried to compile Blender with XCode 12 Beta, but this failed. Therefore I re-installed XCode 11.5.

since big sur is still beta I would wait see if they fix their drivers first. If we can reproduce on the devkits we will try to fix it ourselves.

Thanks! No problem! I'll keep you informed if anything changes...

Hi. I've just downloaded the latest build, and the problem is still there with macOS Catalina.

I can confirm what Francois writes. macOS Catalina here, too. It is not as bad as before anymore but it is definitely not fuly fixed sadly.

Clément Foucault (fclem) reopened this task as Needs Developer to Reproduce.Wed, Jul 8, 7:21 PM

It really seems to be an Intel driver issue. On my Mac Pro with AMD graphics card, it works with charm.

But then, why on the same machine would 2.8x work fine and not 2.9 alpha?

It really seems to be an Intel driver issue
But then, why on the same machine would 2.8x work fine and not 2.9 alpha?

They meant that it's an Intel Driver + Blender 2.90 issue.