@Clément Foucault (fclem) There's no a build since 4th dec for Mac OSX.

I think you need to check your topology.. you've got overlapping faces.. That's how that looks like.. has nothing to do with this (fixed) bug as I see it

Hi!
I use Radeon Vega 64
I have some other type of overlapping glitches in viewport when using bevel modifier in Edit Mode.
It randomly flickers and changing during viewport movements.

Thats unfortunate for us Mac users... I guess there is not much of a chance that we will see Metal support in the future - maybe through the help of MoltenVK?

@Hans-Simon Sagave (wizardx) I read that there are plans for a Metal wrapper for Vulkan in the future. I guess a pure Metal version of Blender would require maintaining a separate macOS branch. But if you already want a taste of Metal-assisted rendering, you can try Radeon ProRender. It's quite well-integrated in Blender and is also free.

Just for reference:

A little debugging update:

Cycles: OpenCL on macOS has been disabled

There was a growing payload of bugs in Cycles related on OpenCL on macOS
platform, and those issues were caused by a compiler bug, which we have no
control over.

Surely, it is sometimes possible to work compiler bugs around from a
source, but we are facing some of the issues which are not solvable in this
way. Also, such solutions are usually short-living,. since adding more
features are often kicking compiler to provide buggy binary again.

In this case compiler will not get fixed since Apple decided to discontinue
OpenCL on its platform.

So the decision was made to drop support of OpenCL, keep official features
of Blender stable and predictable, and focus on things we have control over.

P.S. Older Blender releases are always available. Surely, this sounds like
using an ancient software without neat features. But we can't push Cycles
OpenCL on macOS measurably beyond that anyway.

Cycles: OpenCL on macOS has been disabled

There was a growing payload of bugs in Cycles related on OpenCL on macOS
platform, and those issues were caused by a compiler bug, which we have no
control over.

Surely, it is sometimes possible to work compiler bugs around from a
source, but we are facing some of the issues which are not solvable in this
way. Also, such solutions are usually short-living,. since adding more
features are often kicking compiler to provide buggy binary again.

In this case compiler will not get fixed since Apple decided to discontinue
OpenCL on its platform.

So the decision was made to drop support of OpenCL, keep official features
of Blender stable and predictable, and focus on things we have control over.

P.S. Older Blender releases are always available. Surely, this sounds like
using an ancient software without neat features. But we can't push Cycles
OpenCL on macOS measurably beyond that anyway.

Cycles: OpenCL on macOS has been disabled

There was a growing payload of bugs in Cycles related on OpenCL on macOS
platform, and those issues were caused by a compiler bug, which we have no
control over.

Surely, it is sometimes possible to work compiler bugs around from a
source, but we are facing some of the issues which are not solvable in this
way. Also, such solutions are usually short-living,. since adding more
features are often kicking compiler to provide buggy binary again.

In this case compiler will not get fixed since Apple decided to discontinue
OpenCL on its platform.

So the decision was made to drop support of OpenCL, keep official features
of Blender stable and predictable, and focus on things we have control over.

P.S. Older Blender releases are always available. Surely, this sounds like
using an ancient software without neat features. But we can't push Cycles
OpenCL on macOS measurably beyond that anyway.

Same problem here, in both 2.79 and 2.8

Apple will not longer develop OpenCL... So what about Metal? This is the new one. It's much much faster on Mac and is the new language! Will Blender ever support Metal? This'd be a great idea: much faster render times on Mac, denoising and baking would work as well. Can we expect something like this for 2.81??? It would bring up Blender for a new level on Mac!

It's crashing here too. I'll take a closer look at it this weekend.

Commit: rBbb0d812d98f.
Link to the mailing list: https://lists.blender.org/pipermail/bf-committers/2018-December/049695.html
Link to the release notes: https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Cycles#GPU_rendering

Well, guess its finally time to get this tackled. Been delaying this for quite some time, since this is one of the things which doesn't really have a happy end :(

Yeah it would totally be great if this could be fixed! I tried it with 2.8 and 2.79b without success,.. With 2.8 I get the random black tiles. I just tried it again with 2.79b but that made my Mac reboot itself:( Tried it again just to be sure but the second time my whole screen went yellow and I had to unplug my eGPU.
Using a MacBook Pro 2018 i9 32GB ram with AMD Vega56 eGPU running MacOS Mojave.
Really hoping this can get fixed soon. In the meantime, does anyone know a way to still use the denoise function?

Hi. I will upload a new patch later today (code cleanup and without the previous "fix").

This crashes in background mode for me, running blender -b -E BLENDER_EEVEE -f 1.

This is not an error only a warning. As long as shader interface (in and out variables) matches the compilation / linking is ok.
We had to make sure the interface matches for eevee in the past so that's why there is many related warning.

I've added a new option to test gpu driver workarounds : --debug-gpu-force-workarounds

Hi. Here's a patch solves the current issue with the FRAMEBUFFER_UNDEFINED as mentioned in the opening post.

Makes sense, thanks for looking into this.

Thanks, will commit.

@Paweł (Wiggle) Honnestly if you follow this page it should go quite fast, the longest is to install xcode https://wiki.blender.org/wiki/Building_Blender/Mac. Keep in mind that you don't need cuda and also that for the make command to work you need to put cmake in your PATH (export PATH=$PATH:/path/to/cmake/bin/in/his/content/folder) If you need futher assistance go to blendercoders on freenode I'm sure they will be people to help you and I might be here as well as Abrases

@Hugo Lamarche (antares) Okay, I can help. How can you configure this environment?

@Paweł (Wiggle) So I check and it work properly on my mac in build 63ac7c799c8. If you want to help track that bug I think you should go to blendercoders and setup a dev environnement to be able to test it with the blender coders (What I did) they don't have the proper hardware.

@Paweł (Wiggle) Alright, will check that later I don't have my Macbook with me. Either the problem is still here in some case or the build doesn't really contain the fix for some reason...

@Hugo Lamarche (antares) I checked on this build. So the problem, however, not solved: /

@Paweł (Wiggle) I'm not sure to understand but what I can tell you for sure is that the fix is in the latest macOS build : 63ac7c799c8
I only have the MacBook Pro 2016 to test it on, I will try it with latest build version on the website tonight, the one I try so far was the one I built with the fix.

@Hugo Lamarche (antares) I understand. I thought that in this build from December 3 this is not yet corrected, but it probably is. I also checked the imac 27 inch 2015 and MacBook Pro 2017 and there the problem also occurs. Can I check it on your build?

Pawel on my end it's doesn't make any difference but you have faster and different hardware. I recorded a small video of the demonstration with and without the debug menu, it's difficult to see with the lag that it create but even without the record I don't see any difference.

In today's compilation, it's better, but still in the debug mode set to 23, the blender is smoother.

Because of the screen recording it's much worse that it is normally but you get the idea

I have the same problem on a MacBook Pro 2016 i5 and Intel Iris Graphics 540 1536 MB. Latest macOS and latest blender 2.8 (Both on latest beta and latest git update (4ee29d3fdff) that I've built). I can confirm that enabling the debug menu to 23 does smooth the fps and running a more complex scene doesn't seems to slow down more the viewport. I'm available for further debugging.

See below my new equipment because of Graphic-Chip-Crash of my loved 2011-Mac (I was crying).
--> Phenomen of "Input Cursor has a backgound square, input cannot be seen completely" seems to be gone.
--> Until now (1 Month) I never saw the "background square" with this new equipment, neither on internal nor on external screen.

Hi. Sorry for kind of spamming this topic.

@Clément Foucault (fclem) This is the comparison of two computers.

Hi. I tried to create a "patch.diff", but it didn't work out very well (I'm not familiar with patching yet), so I will just upload 2 files in this post.