Page MenuHome
Create Task
Maniphest T59827

Adding Normal Map to object in EEVEE results in emissive material
Closed, DuplicatePublic
Actions

Description

System Information
Operating system: antergos (Arch current)
Graphics card: GTX 770

Blender Version
Broken: 2.80, 6d89337257b6, 2018-12-24

Short description of error
Adding Normal Map node to Normal slot in Principled BSDF produce emissive material on Text object in EEVEE. Converting Text to Mesh doesn't change this behavior.
Same material used on different mesh works properly. Also it is working ok in Cycles.

Using different shader (Diffuse, Glossy, SSS, Translucent) produce black material.

Exact steps for others to reproduce the error

  1. Add Text object.
  2. Create new material.
  3. Add Normal Map (Tangent Space) node and connect to Normal socket in Principled BSDF.

text_normal_eevee_bug.blend639 KBDownload

Related Objects

Event Timeline

cgslav (LukeD) renamed this task from Adding Normal Map to Text object in EEVEE results in glowing object to Adding Normal Map to Text object in EEVEE results in emissive material.Dec 25 2018, 12:02 AM
cgslav (LukeD) created this task.
Patrick Worthey (ptrick) added a subscriber: Patrick Worthey (ptrick).Dec 25 2018, 5:33 AM

Seems to occur on generic curves as well. Converting from text/curve to mesh WILL work if you also add a uv map I noticed. I'm not sure how a tangent-space normal map is supposed to work on an object that has no UVs, but the make-it-black behavior is inconsistent with other renderers and is certainly jarring.

cgslav (LukeD) added a comment.Dec 25 2018, 7:24 PM
In T59827#587973, @Patrick Worthey (ptrick) wrote:

Seems to occur on generic curves as well. Converting from text/curve to mesh WILL work if you also add a uv map I noticed. I'm not sure how a tangent-space normal map is supposed to work on an object that has no UVs, but the make-it-black behavior is inconsistent with other renderers and is certainly jarring.

Mesh without UV.

Cycles:

EEVEE:

Also I wonder why it turns into emissive material? It doesn't seem right.

Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 30.Dec 28 2018, 12:47 PM
Sebastian Parborg (zeddb) added a subscriber: Sebastian Parborg (zeddb).

I can't reproduce the emissive issue on a build from today. Could you guys retry with a newer build?

I do however get two black text objects in the file you provided. So it seems like the behavior now matches the other shaders for me.

cgslav (LukeD) added a comment.EditedDec 28 2018, 3:57 PM
In T59827#589534, @Sebastian Parborg (zeddb) wrote:

I can't reproduce the emissive issue on a build from today. Could you guys retry with a newer build?

I do however get two black text objects in the file you provided. So it seems like the behavior now matches the other shaders for me.

It's still there with 2018-12-18, 3610f1fc43d0

Check what's going on there while scaling viewport.

Sebastian Parborg (zeddb) assigned this task to Clément Foucault (fclem).Dec 28 2018, 4:21 PM
Sebastian Parborg (zeddb) raised the priority of this task from 30 to Normal.
Alexander Court (spiegelball) added a subscriber: Alexander Court (spiegelball).Dec 31 2018, 3:21 PM

Seems to be related to T59784.

Sebastian Parborg (zeddb) merged a task: T60991: Normal Map on Tangent Space makes some objects emissive.Jan 29 2019, 7:08 PM
Sebastian Parborg (zeddb) added a subscriber: Henrique Balduino Gonzaga (henriquebg88).
Philipp Oeser (lichtwerk) renamed this task from Adding Normal Map to Text object in EEVEE results in emissive material to Adding Normal Map to object in EEVEE results in emissive material.Feb 11 2019, 2:22 PM
Philipp Oeser (lichtwerk) triaged this task as 50 priority.
Philipp Oeser (lichtwerk) mentioned this in T61408: NormalMap input causing Material Viewport issue in dual 3DView Layout.
Philipp Oeser (lichtwerk) merged a task: T61408: NormalMap input causing Material Viewport issue in dual 3DView Layout.
Philipp Oeser (lichtwerk) added subscribers: MACHIN3 (MACHIN3), Philipp Oeser (lichtwerk), Joao Paulo (gendosplace).
MACHIN3 (MACHIN3) added a comment.Feb 11 2019, 2:35 PM

Just to make sure it does't get lost, you can reproduce this issue with a single mesh object, if you use multiple 3d views and switch from solid to eevee, see https://developer.blender.org/T61408

Philipp Oeser (lichtwerk) mentioned this in T59207: Material suddenly became emissive, but not for all objects using it.Feb 12 2019, 10:03 AM
Jeff Lee (godfrey) added a subscriber: Jeff Lee (godfrey).Feb 12 2019, 10:58 PM

I've been seeing this on models where there are degenerate faces and a normal map is applied; it's especially noticeable if Bloom and Depth of Field are enabled. (Text objects seem to create degenerate faces on curves rather frequently).

I can consistently reproduce the issue on a cube:

  1. Start a new scene, with Eevee as the renderer.
  2. Edit the default cube (or create a new one) and subdivide the vertical edges twice, creating two new horizontal edges all around the cube.
  3. Select one of the new horizontal edges, on a face visible to the camera, and subdivideonce.
  4. Select both new sets of horizontal edges, and scale to 0 in the Z direction. (It should now look like there's a single horizontal edge around the cube as they're overlaying each other.)
  5. UV unwrap the cube using the Smart UV Project method, default values are fine.
  6. Add a PrincipledBDSF shader to the model; connect an image node (through a Normal Map node) to the Normal Map input of the shader. Actually, you don't even need a normal map image; just a bare Normal Map node with no input will also produce the issue.
  7. With the viewport in LookDev mode, enable Bloom and Depth of Field to really see the effect.

I've attached a file containing the above.

EmissiveBug.blend652 KBDownload

Clément Foucault (fclem) closed this task as a duplicate of T61870: Eevee Shading Error- Object's go completely black if they have a normal map..Mar 13 2019, 11:14 PM
Clément Foucault (fclem) edited projects, added EEVEE & Viewport; removed Eevee.Jun 19 2020, 11:09 PM