Sure thing. Thanks.

CPU for me works fine. Is just when I switch to GPU. It could be a Nvidia only issue but I thought there was direct communication between Blender and Nvidia so the problem could be sorted out quicker than me alone trying to get in touch with them and doing anything about it. Not entirely sure how to proceed with this issue. It would be great to get other people to try it out and see if this is just me or something that is affecting other issues. I guess you need to have the same card as mine and have latest drivers installed.

It would be great to hear what the use of Allow Negative Frame Values is when you can't actually set anything below 0. I needed this atm and it seems there is no work around?

That's a good guess. Thanks for sharing.

Thanks Germano.

Ok I spent some time to simplify that and the problem seems to be using Is Glossy Ray in the Mix Shader for the 2 HDRI nodes. A new simplified version has been uploaded. So the emissive light gets in conflict with that somehow. Is Camera ray does not have the same problem.

In T71067#851065, @Germano Cavalcante (mano-wii) wrote:

If the problem is word node setup, it would be nice to simplify it to make it easier for developers to investigate.
Given the seriousness of the problem, I don't think it's worth spending a lot of time trying to find the cause.

I have just downloaded the project and latest beta build and still happening. What a mystery and super annoying not being able to use the addon because of that.

That world setup comes from the Asset Management addon. If that could be the root cause then it would be great to know why that emissive mesh gets in conflict with it. It doesn't really make much sense even if you have wrong connections.

I also think a pointiness map generation for the mesh would be appropriate if not real-time.

Thanks for switching this to high, Brecht.

It would be great to know why this bug is delayed as no one from the team said anything regarding this issue. Neither has been fixed yet and it's extremely important for some people.

I was about to post the same thing. Pretty annoying not being able to speed up single elements preview for large scenes as already mentioned.

If it will eventually be done at some point I can leave it here as TODO for now. Thanks, Philipp.

No problem. I didn't know how things work internally. Please let me know so I can open a proper request as I think this is very important when changing lots of keystrokes.

After upgrading to 10.13.5 with latest Nvidia drivers the problem persists. Any idea if I could do anything else? Would 2.8 use a newer version? I guess EEVEE would be even better anyway for that type of shadings.

I now checked the project using another Windows drive that I had around and it seems to be working fine. So I guess the problem is as you said with the OpenGL in my OSX version or something. Will update my system as there is a new one and see if the new drivers solve it. Any idea about what I could do in the case that would not solve it?

I just checked the file using another iMac and the Matcap looks correctly in Material shading. OSX 10.10.5 with Ati Radeon HD 2400 XT. I was wondering if this has to do with Nvidia drivers as you said. Will check the other person graphics card brand as he reported not working on Windows.

The project as stated was tested by another user using a PC on windows and he had the same result while he could have the right result using a Macintosh. I was hoping from you or someone else to download the file and test if you could replicate the problem. My graphics card is up to date and I never had any problem visualizing everything as the way things should look.