gl.getShaderInfoLog() fragment 0:109(188): error: invalid input layout qualifier used

Description of the problem

When I open any kind of samples from threejs, I get this error : For example, when I use https://threejs.org/examples/#webgl_water this is the output that I get :

On Chrome : THREE.WebGLShader: gl.getShaderInfoLog() fragment 0:109(188): error: invalid input layout qualifier used 0:117(170): error: invalid input layout qualifier used 0:120(205): error: invalid input layout qualifier used

On FireFox : gl.getProgramInfoLog Must have an compiled fragment shader attached. 0:2(12): warning: extension GL_ARB_gpu_shader5' unsupported in vertex shader 0:2(12): warning: extension GL_ARB_gpu_shader5’ unsupported in fragment shader 0:115(188): error: invalid input layout qualifier used 0:123(170): error: invalid input layout qualifier used 0:126(205): error: invalid input layout qualifier used

Three.js version

• Dev
• r98
• r97

Browser

• Chrome
• Firefox

OS

• All of them
• Windows
• macOS
• Linux
• Android
• iOS

Hardware Requirements (graphics card, VR Device, …)

Name	Value
Platform	Linux x86_64
Browser User Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36
Context Name	webgl
GL Version	WebGL 1.0 (OpenGL ES 2.0 Chromium)
Shading Language Version	WebGL GLSL ES 1.0 (OpenGL ES GLSL ES 1.0 Chromium)
Vendor	WebKit
Renderer	WebKit WebGL
Unmasked Vendor	Intel Open Source Technology Center
Unmasked Renderer	Mesa DRI Intel® HD Graphics 530 (Skylake GT2)
Antialiasing	Available
ANGLE	No
Major Performance Caveat	No

[olivierchatry]

Just got an update of mesa on fedora 29 and it fixed the issue. All good now. Closing it. Thanks for the quick support !

[kenrussell]

I’m not 100% sure. I think it means that the shader is using the syntax:

layout(location=0) in vec4 inColor;

which is OpenGL ES 3.0 / WebGL 2.0 syntax, and the driver is rejecting it for some reason.

Would need to see the text of the failing shader to know for sure.

@gyagp or @Richard-Yunchao from Intel may be able to help route this problem report to the Mesa team, but first we need to confirm the driver version on which it’s happening.