Summary: | Wrong shader preprocessor string with Intel HD620 graphic card | ||
---|---|---|---|
Product: | Mesa | Reporter: | Max Perl <max.augsburg> |
Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | RESOLVED NOTOURBUG | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | 17.1 | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Max Perl
2017-08-13 18:19:21 UTC
Hi Max, I doubt this is a Mesa bug - it's more likely an application issue. If the application is using a "Core Profile" OpenGL context, it will get OpenGL 4.5 and can use: - GLSL 1.50 (#version 150) - GLSL 3.30 (#version 330) - GLSL 4.00 (#version 400) - GLSL 4.10 (#version 410) - GLSL 4.20 (#version 420) - GLSL 4.30 (#version 430) - GLSL 4.40 (#version 440) - GLSL 4.50 (#version 450) - GLSL ES 1.00 (#version 100) - GLSL ES 3.00 (#version 300 es) - GLSL ES 3.10 (#version 310 es) - GLSL ES 3.20 (#version 320 es) If the application is not specifically requesting a core profile context, it will get a legacy GL context, which is OpenGL 3.0, which lets you use: - GLSL 1.10 (#version 110 or no version line at all) - GLSL 1.20 (#version 120) - GLSL 1.30 (#version 130) - GLSL ES 1.00 (#version 100) - GLSL ES 3.00 (#version 300 es) - GLSL ES 3.10 (#version 310 es) - GLSL ES 3.20 (#version 320 es) There is no GLSL 1.00 - "#version 100" actually refers to GLSL ES 1.00, which is the shading language of OpenGL ES 2.0. OpenGL can use these shaders because we support GL_ARB_ES2_compatibility. Likely the application expects to be able to use GLSL 1.50 in a legacy / compatibility profile, while we only support it in core profile. It should certainly be able to use GLSL 1.30 / #version 130 though, and the fact that it doesn't work sounds like a bug in their fallback paths. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.