[RESOLVED] Blender 2.8 Viewport flickering

Hello everyone !
First topic here, usually I always find solution to my problems, but not this time !

I’m running Blender 2.80 on MacBook Pro 2017 :sweat_smile: : MacOS Mojave (10.14.6), proc Intel Core i5 3,1GHz, graphic chipset Intel Iris Plus Graphics 650 1536Mb, and everything is up to date.

The problem is :
Sometimes my viewport is flickering and I can’t fix it.
Most of the time, it happens when I “shade smooth” something.
The problem still in all viewport shadings except when it’s Cycles rendered. And once it’s happening, there’s no way to fix it.
And it’s only happening in the workspace where the problem began (in my case it happened in Layout, UV Editing, Shading).
Here a link to a video to show you : https://youtu.be/55zr4iPB_fM

It’s not impossible to work with, but is really annoying to the eyes and as you can see in the video, sometimes when I click on an object it’s not the good selection.

I tried to open it on an other laptop (MacBook Pro 2018), the bug is still here.
When I send the file to a friend (this time Windows 10 on Asus, with Blender 2.79), none of the objects where in the file, neither in the viewport or the outliner :thinking:

Here the dropbox link to the file : https://www.dropbox.com/s/9yo84q7hdav1mkv/phone.blend?dl=0

And by the way, the link to another file with the same problem in the UV Editing workspace : https://www.dropbox.com/s/05ynv53axnjsars/interphone%20vintage%20CTS.blend?dl=0

I hope my problem could be solved, thank you very much !

1 Like

Hi. Increase “Clip Start” value:


Both the files where at 0.001cm, but instead I changed it to 0.1cm and it works !

I don’t understand why the smooth shading triggered it though :thinking:

Simple problem, simple solution, thank you very much !

1 Like

It’s not due to the smooth shading, it’s about how to talk with hardware in 3D: https://en.wikipedia.org/wiki/Clipping_(computer_graphics)#Clipping_in_3D_graphics

Large scale differences between near and far clipping planes produce less tolerance for computation approximations, and so more artefacts.


Ok thanks ! I’ll be more carefull in the futur :wink:

Thanks a lot! I’ve been looking around for a solution for a whole day now and this worked. I always just kept the clip start to bare minimum and end to as far as it can go