Pink Material with Node Groups in Eevee #62790

New Issue

Julien Kaspar · 2019-03-20T17:52:59+01:00

Julien Kaspar commented

2019-03-20 17:52:59 +01:00

System Information
Operating system: Linux-4.13.0-46-generic-x86_64-with-debian-stretch-sid 64 Bits
Graphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 384.130

Blender Version
Broken: version: 2.80 (sub 51), branch: master, commit date: 2019-03-20 14:01, hash: blender/blender@4e0b5a0baf

Short description of error
In some cases while working on the production files of Spring, the material turns pink for Eevee. This is usually coupled with long shader compiling. I saw this usually only occurring for big material setups that use node groups to some extend.

Example file: bug_pink.blend

Both the jacket and rock end up pink when going into LookDev or rendering with Eevee. For the rock it seems to be the node group "rocks_frost" near the material output that is causing it. When skipping this node group the material renders fine.

The jacket used to render fine but then I put most of the textures into node groups and plugged them into the material on multiple locations. After that it ended up pink as well. By removing some of the node groups or muting enough nodes along the way, the pink material becomes fixed.

**System Information** Operating system: Linux-4.13.0-46-generic-x86_64-with-debian-stretch-sid 64 Bits Graphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 384.130 **Blender Version** Broken: version: 2.80 (sub 51), branch: master, commit date: 2019-03-20 14:01, hash: `blender/blender@4e0b5a0baf` **Short description of error** In some cases while working on the production files of Spring, the material turns pink for Eevee. This is usually coupled with long shader compiling. I saw this usually only occurring for big material setups that use node groups to some extend. ![Selection_031.png](https://archive.blender.org/developer/F6856215/Selection_031.png) Example file: [bug_pink.blend](https://archive.blender.org/developer/F6856122/bug_pink.blend) Both the jacket and rock end up pink when going into LookDev or rendering with Eevee. For the rock it seems to be the node group "rocks_frost" near the material output that is causing it. When skipping this node group the material renders fine. The jacket used to render fine but then I put most of the textures into node groups and plugged them into the material on multiple locations. After that it ended up pink as well. By removing some of the node groups or muting enough nodes along the way, the pink material becomes fixed.

Julien Kaspar commented

2019-03-20 17:52:59 +01:00

Added subscriber: @JulienKaspar

Clément Foucault was assigned by Julien Kaspar

2019-03-20 17:54:10 +01:00

Sebastian Parborg commented

2019-03-20 18:18:12 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-03-20 18:18:12 +01:00

Getting an assert:

BLI_assert failed: /home/zed/programmering/blender_master/blender/source/blender/blenkernel/intern/node.c:1741, ntreeFreeLocalNode(), at '(ntree->id.tag & LIB_TAG_LOCALIZED) != 0'

And if I use lookdev or eevee, I simply get a black material which I suppose in the same error.

Getting an assert: ``` BLI_assert failed: /home/zed/programmering/blender_master/blender/source/blender/blenkernel/intern/node.c:1741, ntreeFreeLocalNode(), at '(ntree->id.tag & LIB_TAG_LOCALIZED) != 0' ``` And if I use lookdev or eevee, I simply get a black material which I suppose in the same error.

Clément Foucault commented

2019-03-20 19:43:03 +01:00

Changed status from 'Open' to: 'Archived'

Clément Foucault closed this issue

2019-03-20 19:43:03 +01:00

Clément Foucault commented

2019-03-20 19:43:03 +01:00

From @JulienKaspar on IRC:

GPUShader: linking error:
Fragment info
-------------
Internal error: assembly compile error for fragment shader at offset 1666214:
-- error message --
line 66297, column 1:  error: too many instructions

The shader is just too complex for the driver to generate a shader that would fit its maximum instruction count. The problem is that using nodegroups generate a few more dummy instructions that the compiler may not remove at compile time.

So we are talking about optimization here, not a real bug.

From @JulienKaspar on IRC: ``` GPUShader: linking error: Fragment info ------------- Internal error: assembly compile error for fragment shader at offset 1666214: -- error message -- line 66297, column 1: error: too many instructions ``` The shader is just too complex for the driver to generate a shader that would fit its maximum instruction count. The problem is that using nodegroups generate a few more dummy instructions that the compiler may not remove at compile time. So we are talking about optimization here, not a real bug.

Clément Foucault commented

2019-03-22 14:59:22 +01:00

@JulienKaspar I added a small optimization for rgb curves (blender/blender@c49a70bcd1) that could help in this case. Here the material just displays black so I guess it is still not working on my end. But I have a different GPU so you might have better luck.