White OSGView & GLSL Version Not Supported
hpuhr opened this issue · comments
When the OSGView is started on older, unsupported Intel graphics cards the OSGView only show a white window and the following error messages are logged in the console:
"
...
glLinkProgram 0x1af6a320"" FAILED
VERTEX glCompileShader "main(vertex)" FAILED
VERTEX Shader "main(vertex)" infolog:
0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES
FRAGMENT glCompileShader "main(fragment)" FAILED
FRAGMENT Shader "main(fragment)" infolog:
0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, and 3.10 ES
Program "" infolog:
error: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shader
glLinkProgram 0x82eefa0"" FAILED
"
This is due to the the used graphics libraries OpenSceneGraph and osgEarth depending on shaders defined in GLSL 3.30 (shading language version) and the used graphics card driver not supporting this version of shaders.
There is a tested a workaround: There exists the issue that in some cases the shaders are supported in the used Mesa graphics driver, but are not detected correctly. One can override the reported OpenGL version for one application using a system variable and start the app in that mode using:
MESA_GL_VERSION_OVERRIDE=3.3 ./ATSDB-v0.5.3.AppImage
At least on the authors workstation with an Intel graphics card this resolved the issue.
It is currently being investigated if that can be recommended. If you encountered that issue please contact the author if that workaround worked for you.
The workaround has been confirmed by two different users, and is now the recommended option to mitigate this issue.
If this was not the case for you please contact the author.
I am having this issue when i simulate my omnetpp.ini. I have already tried MESA_GL_VERSION_OVERRIDE=3.3 in linux terminal but still the issue persists. Can you please elaborate if i am doing something wrong. I am literally trying to run the inbuilt Boston example.
Unfortunately no. This issue is related to graphics card / driver issues, which are not my expertise and out of scope for this project. If the issue persists the final resort would be to use a different workstation / OS.