Texture won't display or won't do correctly on eevee when used as bump and other input #70614

New Issue

Daniel Calderón · 2019-10-07T19:07:22+02:00

Daniel Calderón commented

2019-10-07 19:07:22 +02:00

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: 4707f1982d
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).bug_tank.blend

Exact steps for others to reproduce the error
Plug a texture output in two different inputs of a principled material. bug_tank.blend
{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.

**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: `4707f1982d` 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).[bug_tank.blend](https://archive.blender.org/developer/F7795003/bug_tank.blend) **Exact steps for others to reproduce the error** Plug a texture output in two different inputs of a principled material. [bug_tank.blend](https://archive.blender.org/developer/F7794992/bug_tank.blend) {[F7794994](https://archive.blender.org/developer/F7794994/bug_tank.blend)}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.

Daniel Calderón commented

2019-10-07 19:07:22 +02:00

Added subscriber: @xdanic

blender-admin commented

2019-10-07 19:07:22 +02:00

#70611 was marked as duplicate of this issue

Philipp Oeser commented

2019-10-08 17:32:11 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-10-08 17:32:11 +02:00

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

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

Clément Foucault was assigned by Philipp Oeser

2019-10-08 18:06:23 +02:00

Philipp Oeser commented

2019-10-08 18:06:23 +02:00

Actually caused by 5c79f2d0fb...

Philipp Oeser commented

2019-10-08 19:06:17 +02:00

@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...)

@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](https://archive.blender.org/developer/P1133.txt) (couldnt find a quick check on a socket to see if it has more than one link...)

Philipp Oeser commented

2019-10-09 10:36:05 +02:00

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

note: `nodeCountSocketLinks` could be used in [P1133](https://archive.blender.org/developer/P1133.txt) [still not sure if that defeats the purpose / kills performance]

Clément Foucault commented

2019-10-10 00:23:29 +02:00

Added subscribers: @SpectreFirst, @fclem, @EAW, @Likkez-2, @mano-wii, @NahuelBelich