Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-28 Thread James Turner
On 24 Dec 2011, at 14:06, Vivian Meazza wrote: The model-combined shader uses EXT_texture3D Right, I've gained a bit more understanding from digging in the OSG sources: The error: OpenGL extension 'GL_EXT_texture3D' is not supported. is a red-herring; the Texture3D class in

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-28 Thread Mathias Fröhlich
Hi, On Wednesday, December 28, 2011 15:29:50 James Turner wrote: So, this is where my knowledge runs out - can someone suggest the next debugging step, to identify the problem in the water effect? Can you post the output from glxinfo -l. Where the -l prints 'some interresting limits' ... Or

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-28 Thread James Turner
On 28 Dec 2011, at 15:40, Mathias Fröhlich wrote: Can you post the output from glxinfo -l. OpenGL limits: GL_MAX_ATTRIB_STACK_DEPTH = 16 GL_MAX_CLIENT_ATTRIB_STACK_DEPTH = 16 GL_MAX_CLIP_PLANES = 6 GL_MAX_COLOR_MATRIX_STACK_DEPTH = 10 GL_MAX_ELEMENTS_VERTICES = 1048575

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-28 Thread Frederic Bouvier
Hi James, De: James Turner So, what's the next step in understanding this? The effect claims to use the noise texture (in unit 9, as always): texture-unit unit9/unit typenoise/type /texture-unit Can you post the output from glxinfo -l. OpenGL

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-28 Thread James Turner
On 28 Dec 2011, at 16:04, Frederic Bouvier wrote: GL_MAX_TEXTURE_UNITS_ARB = 8 ... GL_MAX_TEXTURE_COORDS_ARB = 8 It looks like the texture unit of the noise texture is beyond the limits of your card Indeed. What I find strange (but probably due to lack of knowledge) is that the

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-28 Thread Csaba Halász
On Wed, Dec 28, 2011 at 5:04 PM, Frederic Bouvier fredfgf...@free.fr wrote: Hi James, De: James Turner So, what's the next step in understanding this? The effect claims to use the noise texture (in unit 9, as always): OpenGL limits: ...    GL_MAX_TEXTURE_UNITS_ARB = 8 ...    

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-28 Thread James Turner
On 28 Dec 2011, at 16:15, Csaba Halász wrote: Since we are talking about shaders, aren't the limits GL_VERTEX_SHADER_ARB: GL_MAX_TEXTURE_IMAGE_UNITS_ARB = 16 GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS_ARB = 16 GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS_ARB = 16

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-28 Thread Mathias Fröhlich
Hi, On Wednesday, December 28, 2011 16:22:20 James Turner wrote: On 28 Dec 2011, at 16:15, Csaba Halász wrote: Since we are talking about shaders, aren't the limits GL_VERTEX_SHADER_ARB: GL_MAX_TEXTURE_IMAGE_UNITS_ARB = 16 GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS_ARB = 16

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-28 Thread Csaba Halász
On Wed, Dec 28, 2011 at 5:22 PM, James Turner zakal...@mac.com wrote: Csaba, since you have the same card as me, but are not seeing this issue, what limit are you getting for GL_MAX_TEXTURE_UNITS_ARB? (From the fglrx driver, I guess) My limits differ in a few places from yours, sometimes

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-28 Thread Frederic Bouvier
De: James Turner On 28 Dec 2011, at 16:15, Csaba Halász wrote: Since we are talking about shaders, aren't the limits GL_VERTEX_SHADER_ARB: GL_MAX_TEXTURE_IMAGE_UNITS_ARB = 16 GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS_ARB = 16 GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS_ARB =

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-24 Thread Mathias Fröhlich
Hi, On Friday, December 23, 2011 17:05:03 James Turner wrote: == glValidateProgram FAILED id=12 contextID=0 infolog: Validation Failed: Sampler error: Samplers of different types use the same texture image unit. - or - A sampler's texture unit is out of range (greater

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-24 Thread James Turner
On 24 Dec 2011, at 08:32, Mathias Fröhlich wrote: Thie required extensions are in the effect files. Whatever changes are done with the shaders, the effect files *must* contain the minimum condition under which gl version/extensions this shader is valid. This is complex, but the only

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-24 Thread Erik Hofman
On Sat, 2011-12-24 at 10:12 +, James Turner wrote: On 24 Dec 2011, at 08:32, Mathias Fröhlich wrote: Thie required extensions are in the effect files. Whatever changes are done with the shaders, the effect files *must* contain the minimum condition under which gl

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-24 Thread Mathias Fröhlich
Hi, On Saturday, December 24, 2011 11:12:10 James Turner wrote: According to this, there should be no extension required: http://lists.apple.com/archives/mac-opengl/2007/Oct/msg00108.html And 'glxinfo' reports: OpenGL vendor string: ATI Technologies Inc. OpenGL

[Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-23 Thread James Turner
I'm having the dreaded 'invalid operation after ' errors from OSG, which makes seeing other debug output. Once again, it relates to 3D textures, and is presumably Ati specific. Details: - latest Git of fg+sg+fgdata, OSG 3.0.1 - card is a Radeon 5770, with the official Apple

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-23 Thread Csaba Halász
On Fri, Dec 23, 2011 at 5:05 PM, James Turner zakal...@mac.com wrote: I'm having the dreaded 'invalid operation after ' errors from OSG, which makes seeing other debug output. Once again, it relates to 3D textures, and is presumably Ati specific. Details:        - latest Git of

Re: [Flightgear-devel] Debugging an Ati shaders issue (with 3d textures, again)

2011-12-23 Thread Robert
Csaba, I have the same problem. Lock-up is caused by the Landmass shader as soon as I switch to level 4. Linux, fglrx Just as a data point: HD5770 here too, but linux fglrx. I don't see such messages, up to quality level 3. Anything higher causes lock-up of FGFS (have to kill it).