Invalid (pink) shader when using wireframe node #71788

New Issue

Juliano Bianchini · 2019-11-22T18:37:44+01:00

Juliano Bianchini commented

2019-11-22 18:37:44 +01:00

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 26.20.100.7463

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: 26bd5ebd42
Worked: none.

Short description of error
When using wireframe input node shader becomes invalid (pink) when using Eevee or Cycles.
PS: the video driver is up to date (latest version).

Exact steps for others to reproduce the error
Create a shader which uses the "Wireframe" node per the example in the attached file.

Blender file:
wire_frame_bug.blend

Screenshot of the issue:

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 26.20.100.7463 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: `26bd5ebd42` Worked: none. **Short description of error** When using wireframe input node shader becomes invalid (pink) when using Eevee or Cycles. PS: the video driver is up to date (latest version). **Exact steps for others to reproduce the error** Create a shader which uses the "Wireframe" node per the example in the attached file. Blender file: [wire_frame_bug.blend](https://archive.blender.org/developer/F8155925/wire_frame_bug.blend) Screenshot of the issue: ![blender 2.81 wireframe bug.png](https://archive.blender.org/developer/F8155927/blender_2.81_wireframe_bug.png)

Juliano Bianchini commented

2019-11-22 18:37:44 +01:00

Added subscriber: @jbianchini

Anthony Edlin commented

2019-11-22 22:42:52 +01:00

Added subscriber: @AnthonyEdlin

Anthony Edlin commented

2019-11-22 22:42:52 +01:00

When I open your file it works fine for me. Maybe Intel related.

Operating system: Linux-5.3.0-20-generic-x86_64-with-Ubuntu-18.04-bionic 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.26

When I open your file it works fine for me. Maybe Intel related. Operating system: Linux-5.3.0-20-generic-x86_64-with-Ubuntu-18.04-bionic 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.26

Juliano Bianchini commented

2019-11-22 22:55:11 +01:00

I think so. Probably it is something related to this specific Intel graphic card on Windows 10.
It works fine on my Linux (Ubuntu Studio) laptop with Nvidia graphic card.

I think so. Probably it is something related to this specific Intel graphic card on Windows 10. It works fine on my Linux (Ubuntu Studio) laptop with Nvidia graphic card.

Rudolf Wohland commented

2019-11-23 00:24:21 +01:00

Added subscriber: @r.wohland

Rudolf Wohland commented

2019-11-23 00:24:21 +01:00

Attached file works also fine on my Windows system

Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67

Attached file works also fine on my Windows system Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67

Germano Cavalcante commented

2019-11-25 14:54:11 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2019-11-25 14:54:11 +01:00

Try to run blender_debug-gpu.cmd that is included in the download.
Open the file with the problematic shader and then close blender.
After that, the logs will be in a text file which can be attached here.

Try to run `blender_debug-gpu.cmd` that is included in the download. Open the file with the problematic shader and then close blender. After that, the logs will be in a text file which can be attached here.

Philipp Oeser commented

2019-12-05 15:46:19 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-12-05 15:46:19 +01:00

Changed status from 'Open' to: 'Archived'

Philipp Oeser closed this issue

2019-12-05 15:46:19 +01:00

Philipp Oeser self-assigned this 2019-12-05 15:46:19 +01:00

Philipp Oeser commented

2019-12-05 15:46:19 +01:00

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

Juliano Bianchini commented

2019-12-10 20:28:47 +01:00

I was on vacation.

I ran the blender_debug-gpu.cmd file and the log is attached.

Log:
blender_debug_output.txt

System info:
blender_system_info.txt

I was on vacation. I ran the blender_debug-gpu.cmd file and the log is attached. Log: [blender_debug_output.txt](https://archive.blender.org/developer/F8206337/blender_debug_output.txt) System info: [blender_system_info.txt](https://archive.blender.org/developer/F8206339/blender_system_info.txt)

Philipp Oeser was unassigned by Juliano Bianchini

2019-12-10 20:33:07 +01:00

Philipp Oeser was assigned by Juliano Bianchini

2019-12-10 20:34:27 +01:00

Germano Cavalcante commented

2019-12-11 01:11:56 +01:00

Added subscriber: @fclem

Germano Cavalcante commented

2019-12-11 01:11:56 +01:00

The log mentions this error:

Type mismatch: Type of gl_ClipDistance different between shaders.
Out of resource error.

So there really is something wrong there.
@fclem, is this information sufficient to identify and solve the problem?

The log mentions this error: ``` Type mismatch: Type of gl_ClipDistance different between shaders. Out of resource error. ``` So there really is something wrong there. @fclem, is this information sufficient to identify and solve the problem?

Germano Cavalcante commented

2019-12-11 01:13:34 +01:00

Changed status from 'Archived' to: 'Open'

Germano Cavalcante reopened this issue

2019-12-11 01:13:34 +01:00

Philipp Oeser removed their assignment 2019-12-21 21:43:14 +01:00

blender-admin commented

2020-01-16 15:29:07 +01:00

This issue was referenced by faf563d27c

This issue was referenced by faf563d27ca8aa5451be7f835f8f6798a00c1699

Clément Foucault commented

2020-01-16 15:58:11 +01:00