eevee performance drop with node tree in 2.81 #70766

New Issue

MACHIN3 · 2019-10-12T20:39:33+02:00

MACHIN3 commented

2019-10-12 20:39:33 +02:00

System Information
Operating system: Linux-4.13.10-041310-generic-x86_64-with-debian-stretch-sid 64 Bits
Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.67

Blender Version
Broken: version: 2.81 (sub 14), branch: master, commit date: 2019-10-10 23:31, hash: f9cc51788b
Worked: (optional)

Short description of error
Maybe related to this recent issue , I have another node tree that seems to affect eevee performance quite significantly.

eevee_performance_drop_with_eevee.blend

Exact steps for others to reproduce the error

open the attached blend file in 2.80 and drag any of the principled shader's inputs, like metallic or roughness, it should be smooth
repeat in a recent 2.81 build, it should be sluggish

**System Information** Operating system: Linux-4.13.10-041310-generic-x86_64-with-debian-stretch-sid 64 Bits Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.67 **Blender Version** Broken: version: 2.81 (sub 14), branch: master, commit date: 2019-10-10 23:31, hash: `f9cc51788b` Worked: (optional) **Short description of error** Maybe related to this [recent issue ](https://developer.blender.org/T70325), I have another node tree that seems to affect eevee performance quite significantly. [eevee_performance_drop_with_eevee.blend](https://archive.blender.org/developer/F7810623/eevee_performance_drop_with_eevee.blend) **Exact steps for others to reproduce the error** * open the attached blend file in 2.80 and drag any of the principled shader's inputs, like metallic or roughness, it should be smooth * repeat in a recent 2.81 build, it should be sluggish

MACHIN3 commented

2019-10-12 20:39:33 +02:00

Added subscriber: @MACHIN3

ThinkingPolygons commented

2019-10-12 21:34:33 +02:00

Added subscriber: @ThinkingPolygons

ThinkingPolygons commented

2019-10-12 21:34:33 +02:00

Confirmed. :(

noki paike commented

2019-10-13 00:33:57 +02:00

Added subscriber: @nokipaike

noki paike commented

2019-10-13 00:33:57 +02:00

I also confirm on the radeon

Philipp Oeser commented

2019-10-14 10:33:11 +02:00

Added subscribers: @fclem, @lichtwerk

Clément Foucault was assigned by Philipp Oeser

2019-10-14 10:33:11 +02:00

Philipp Oeser commented

2019-10-14 10:33:11 +02:00

Can confirm a performance difference.
@fclem: this expected? (I know there's changes to bump and tree traversal, but this also seems to affect trees not even connected to normal slot... but I guess the traversal runs regardless...)

Can confirm a performance difference. @fclem: this expected? (I know there's changes to bump and tree traversal, but this also seems to affect trees not even connected to normal slot... but I guess the traversal runs regardless...)

Clément Foucault commented

2019-10-15 14:40:03 +02:00

Well I guess it's a duplicate of #70325 which has already been resolved. Feel free to reopen if that's still a problem. Note that the new bump mapping increase the shader/nodetree complexity so it will never be on the same level as 2.80.

Clément Foucault commented

2019-10-15 14:40:16 +02:00

Closed as duplicate of #70325

Clément Foucault closed this issue

2019-10-15 14:40:16 +02:00

MACHIN3 commented

2019-10-15 14:58:34 +02:00

#70325 was also reported by me and seems to be resolved to me. This one here is not however. It also doesn't seem like it is related to bump, unless I misunderstand you. I can pipe the node tree into the roughness slot as well and it's just as sluggish.

It doesn't look like i can reopen this task, but I think it's very unfortunate if this slow down can't be resolved. I'll see if I can pin point the issue to any specific node or node combination in the tree.

#70325 was also reported by me and seems to be resolved to me. This one here is not however. It also doesn't seem like it is related to bump, unless I misunderstand you. I can pipe the node tree into the roughness slot as well and it's just as sluggish. It doesn't look like i can reopen this task, but I think it's very unfortunate if this slow down can't be resolved. I'll see if I can pin point the issue to any specific node or node combination in the tree.

Philipp Oeser commented

2020-01-15 18:08:22 +01:00

@MACHIN3 : reading your previous comment, just checking if this is still an issue in fresh builds?