it disables shaders on start with this error message: GL_ARB_point_sprite: Yes Error compiling shader: data/shaders/postprocessBloom1Downsample.frag.glsl: 0:122(1): error: syntax error, unexpected EXTENSION, expecting $end OpenGL vendor: X.Org R300 Project OpenGL renderer string: Gallium 0.4 on ATI R580 Pioneer will run with shaders disabled. this works with mesa 7.10 branch the code to the game is here: https://github.com/pioneerspacesim/pioneer Distro is Slackware64 13.37
(In reply to comment #0) > it disables shaders on start with this error message: > > GL_ARB_point_sprite: Yes > Error compiling shader: data/shaders/postprocessBloom1Downsample.frag.glsl: > 0:122(1): error: syntax error, unexpected EXTENSION, expecting $end This concerns me a bit. This is saying that the error is in line 122. #extension lines can only be preceded in a shader by comments, whitespace, and the #version line. The shader at github has #extension as the first line, so something fishy is going on. Can you run with MESA_GLSL=dump and attach the output? > OpenGL vendor: X.Org R300 Project > OpenGL renderer string: Gallium 0.4 on ATI R580 > > Pioneer will run with shaders disabled. > > this works with mesa 7.10 branch > > the code to the game is here: > https://github.com/pioneerspacesim/pioneer > > Distro is Slackware64 13.37
Created attachment 49176 [details] output with MESA_GLSL=dump
Just as I thought. The #extension line is embedded in the middle of the shader test, and that is illegal in GLSL. From page 12 (page 18 of the PDF) of the GLSL 1.10 spec (emphasis mine): "Each extension can define its allowed granularity of scope. If nothing is said, the granularity is a shader (that is, a single compilation unit), and the *extension directives must occur before any non-preprocessor tokens*." Please report this bug to the Pioneer Spacesim developers.
I've just merged a patch to Pioneer git to fix this. Thanks for the guidance.
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.