Page MenuHome

Blender 2.77 & up, GLSL Viewport rendering not working correctly, material glitches & artifacts
Closed, ArchivedPublic


System Information
Mac OS X 10.11.6, Nvidia GT750m 2GB, OS X Built in drivers (310.xx.xxxx) as well as Nvidia Web Drivers (346.03.15f03)
Mac OS X 10.11.6, Nvidia GTX580 1.5GB, OS X Nvidia Web Drivers (346.03.15f03)
Mac OS Sierra GM 10.12, Nvidia GT750m 2GB, OS X Built in drivers

Blender Version
Broken: 2.77 22a2853
Broken: 2.77a abf6f08
Broken: 2.78RC 9d70344
Worked: 2.76b f337fea

Short description of error
GLSL Viewport rendering is broken, has artifacts & glitches. Material Nodes don't work properly. OS X bug only. Checked on Windows & it works fine. (on 2.78RC)

Based on original file/post:

Exact steps for others to reproduce the error
Open attached blend files to see the artifacts, OS X only, or see the screenshots.



Event Timeline

Marek Dlugajczyk ( renamed this task from GLSL Viewport rendering not working correctly, material glitches & artifacts to Blender 2.77 & up, GLSL Viewport rendering not working correctly, material glitches & artifacts.
Sergey Sharybin (sergey) triaged this task as Normal priority.

Can't reproduce this on Linux. @Mike Erwin (merwin), mind testing on OSX?

Today I did some more tests, and it turns out that even Blender 2.76b has problems on OS X with Material nodes.

Material nodes or probably "Normal node" is causing the shader to be broken, when trying to mix 2 materials or more. Weird thing is that when you go to Edit mode shader is OK, after switch back to Object mode shader is broken again. See the OS X video for details.

I also opened the "broken" test file from OS X on the Windows system and it didn't work anymore. I had to manually re-create the material.

Blender 2.76b OS X:

Blender 2.78 RC2 Windows:

Hi Guys! Any update on this topic?

Blender 2.78.1 Still not working as expected under OS X. Recently I was doing some client work and created simple showcase scene with business card I wanted to render it in the OpenGL viewport.

I created the scene on Windows, and after that opened it on OS X, whenever I use normal map in the textures it goes crazy ;/

I did some additional searching and found similar bug: related to normal maps.

The weird thing happens when I got to Edit Mode, suddenly the material is working as expected. But as soon as I got to Object Mode it breaks. Please see the screenshots attached:

I don't think it's only driver Nvidia/Apple related issue, because it shouldn't work in Edit Mode then.

.blend file attached:

On Windows I was able to render it without problems:

Hi, is this problem still an issue 2.78c ?

Hi, new here but long time Blender user. Registered an account on this just to chime in on this bug.

It's is sole reason I've been unable to upgrade and work in new versions of Blender since 2.76a. Can't wait to try the newer features :/ !

I keep checking back to this same page incase it's fixed (I think I can subscribe now, though.) I guess working around it wouldn't be so bad if I was able to keep both 2.76a and the newest version installed on my workstation, but apparently Unity actually has huge problems with imported blender models from before 2.76b if 2.76b is installed? I'm sure there's already a ticket open for that somewhere?

I'm appreciative of all the work that gets done on Blender, and if this never gets fixed I'd probably be fine working in 2.76a for years before even being tempted to switch 3d packages lol. I just wanted to make sure you guys know this little issue in the main branch is actually a total deal-breaker for some blender game developers.

It looks like there's a bunch of screenshots and details about the problem here already, but if there's anything else I can share to help, I'd be glad to know! thanks

I believe that I might also be suffering from this bug.

MacOS 10.13.3 High Sierra
Early 2015 MacBookPro with Intel Iris Graphics 6100
Blender 2.79

I noticed that when I have a noise texture going into a mixRGB node to control between two slightly different textures, the output is only ever all black or all white. I use a ColorRamp node to alter the output of the noise, and then it becomes very obvious.

Rendered mode is totally fine, just Material view mode.

Brecht Van Lommel (brecht) closed this task as Archived.

Archiving old report, we no longer work on fixing these types of issues in 2.79 but focus on the new viewport in 2.8.