Page MenuHome

Shader Node/Eevee Issue between 2.80 and 2.81
Closed, InvalidPublic


System Information
Operating system: macOS Mojave (10.14.6)
Graphics card: NVIDIA GeForce GT 755M (1GB VRAM)

Blender Version
Broken: 2.81 official release
Worked: 2.80 official release

Short description of error
I have a rather complex texture node setup for a 100% procedurally textured eye which works in both Cycles and the Eevee renderer in Blender 2.80 official release.
In 2.81 it contiues to render correctly in Cycles, but not in Evee.

Exact steps for others to reproduce the error
To recreate the issue, simply open up the same file (attached) in both the 2.80 and 2.81 official releases.
If the issue is not specific to my system, you should see that the "sclera" object renders correctly in 2.80, but in 2.81 complete disappears.
I've attached the .blend file and Eevee render results that I am seeing.

Thank you!



Event Timeline

Philipp Oeser (lichtwerk) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Fri, Nov 29, 11:44 AM

Looking fine here [both in 2.81 and 2.82]

System Information
Operating system: Linux-5.3.11-200.fc30.x86_64-x86_64-with-fedora-30-Thirty 64 Bits
Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.31
2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: rB26bd5ebd42e3

Seeing this is on macOS Mojave, we had a fix for something related [maybe the same?], see rB4e42a98edd8c: Fix T71147 Eevee stops rendering after selection attempt.
Mind checking if todays fresh build resolves the issue for you?

Hi, Philipp

I get the same issue with the 2.82 alpha build.

Also, in 2.80 the scene loads and materials render almost instantly.
In 2.81+ Blender opens and the mac pinwheel spins for a while before ever displaying the rendering issues and also takes quite a while to be responsive after a slight material adjustment.

Something is wrong with the Mac build of 2.81 and 2.82alpha

The file works on Linux and Windows in those versions.

Philipp Oeser (lichtwerk) raised the priority of this task from Needs Information from User to Waiting for Developer to Reproduce.Mon, Dec 2, 7:20 PM

@Clément Foucault (fclem): coul you check on this, too?

@Brian Staub (invertedNormal) Can you try simplifying until it works?

My intuition tells me that it comes from the bump node that became high quality in 2.81. I think your system or the driver cannot compile a shader that big and just gives an incorrect result, instead of just doing the proper thing to do (which is to say that shader compilation could not succeed).

@Clément Foucault (fclem)

Clément, you're exactly right! I disconnected all of the bump nodes in the scene and it now renders in Eevee in 2.81+

Thank you guys!

Is there an option somewhere to use legacy bump for Eevee?

@Philipp Oeser (lichtwerk)

Is there an option somewhere to use legacy bump for Eevee?

Unfortunatelly no. You could try to simplify the heightmap node branch as it is duplicated 3 times internally. Also note that the noise texture node is one of the heaviest node there is.

Clément Foucault (fclem) claimed this task.

So it is an expected behavior. I'll close the report.