Page MenuHome

Texture won't display or won't do correctly on eevee when used as bump and other input
Closed, ResolvedPublic

Description

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GT 555M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35

Blender Version
Broken: version: 2.81 (sub 14), branch: master, commit date: 2019-10-05 20:51, hash: rB4707f1982ddb
Worked: (optional)

Short description of error
Texture won't display or won't do correctly on eevee when used as bump and other input.
If I connect it only to normal, with a bump node between it works fine, but if I use that same texture to also drive the albedo, either connecting it directly or throught some nodes it won't work, affecting only the albedo.
If I use that same texture as a roughness and bump map, it will display correctly as roughness but not for the normal input.
Workaround is duplicating that same texture (shift + D).

Exact steps for others to reproduce the error
Plug a texture output in two different inputs of a principled material.


{F7794994}attached .blend file

EDIT: I sent a version without the image packed and don't know how to delete the older version without it, so the bigger one is the right file to open.

Event Timeline

Philipp Oeser (lichtwerk) lowered the priority of this task from Needs Triage by Developer to Confirmed, High.Tue, Oct 8, 5:32 PM

Can confirm, checking... (assume this is caused by ffd5e1e6acd2)

@Clément Foucault (fclem): havent done performance checks, not sure if this defeats the purpose of backwards iter [could even be worse!], but if we check if the links are actually the same, we can fix by P1133
(couldnt find a quick check on a socket to see if it has more than one link...)

note: nodeCountSocketLinks could be used in P1133 [still not sure if that defeats the purpose / kills performance]