Hi, Agreed this is not for OSG to workaround. But rather than do without arrays, couldn't your app conditionally append the "[0]"? Not clear why this is a showstopper. Just curious.
-- mew > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:osg-users- > [EMAIL PROTECTED] On Behalf Of Christian Muschick > Sent: Tuesday, January 29, 2008 4:38 AM > To: osg-users@lists.openscenegraph.org > Subject: [osg-users] ATI GLSL bug regarding uniform arrays? > > > Hello! > > There seems to be a bug in ATI OpenGl drivers when using uniform > arrays. > For e.g. the uniform array "float arr[3]" I have found that > getUniformLocation("arr") returns an error while > getUniformLocation("arr[0]") returns the desired value. > > This is in clear contrast to the glGetUniformLocation documentation, > where it says: > "... Except if the last part of name indicates a uniform variable > array, > the location of the first element of an array can be retrieved by using > the name of the array, or by using the name appended by "[0]"." > > Has anybody else experienced this issue? I expect no workaround will be > implemented in OSG, so I'll have to do without array uniforms? > > If nothing else, this should warn anybody searching for ATI and array > uniforms... > > regards > cm > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users- > openscenegraph.org _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org