Sign in to follow this  

OpenGL does GLSL support const arrays?

Recommended Posts

I've declared an array as const in my fragment shader and my nVidia drivers complain warning C7516: OpenGL does not allow constant arrays but then allows the shader to execute (correctly). Looking through the GLSL specs and through my orange book I can't find a mention of arrays not being allowed to be constant. Does GLSL allow const arrays or is this nVidia being weird? I can't think of a reason const arrays wouldn't be allowed........

Share this post

Link to post
Share on other sites
Guest Anonymous Poster
Beware NVidia GLSL compiler allows you to use cg constructs which are not allowed in pure OpenGL (... and you may face angry owners of ATI cards very soon :) To remedy this, I recomend you to download small NVidia utility(look on their dev page) where you can force strict OpenGL compiler.


Share this post

Link to post
Share on other sites
yeah :-D the thing is that I don't trust nVidia's compiler. In their last driver release (not the current dev drivers, the one before) the compiler claimed gl_MaxTextureCoords wasn't a const which it blatantly is. This has been fixed but leaves me doubtful as to whether GLSL really doesn't allow const arrays (can't find a mention in the spec) or if it's nVidia's driver playing games with me... again..... anyone tried const arrays with ATI drivers?

Share this post

Link to post
Share on other sites
As of GLSL v1.1 rev 60, this is allowed as arrays are first class objects, but before it was not, and I quote:

"There is no mechanism for initializing arrays at declaration time from within a shader." (GLSL v1.1 rev 59!, §4.1.9)

"It is an error to write to a const variable outside of its declaration, so they must be initialized when declared." (GLSL v1.1 rev 59, §4.3.2)

Combining these two leads to the conclusion that prior to v1.1 rev 60, constant arrays are not allowed. As of rev 60, you _can_ initialise an array using an array constructor.

And although nVidia has great drivers and an amazingly flexible GLSL compiler, be warned, ATI isn't as forgiving :-). I had written a blur shader that used a const kernel which compiled without a problem on my GF6800 GT, but failed to compile on an (albeit not so recent) ATI. This isn't surprising, knowing that nVidia adheres to the Cg standard. Perhaps newer ATIs do to, I wouldn't know.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By DelicateTreeFrog
      Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
      Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
      For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
      So, here's what the plan is so far as far as loading goes:
      Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
      Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
      Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
      The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
      So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
      With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!
    • By JJCDeveloper
      I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks
    • By AyeRonTarpas
      A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

      -What I'm using:
          C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.  
      Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?  
    • By ferreiradaselva
      Both functions are available since 3.0, and I'm currently using `glMapBuffer()`, which works fine.
      But, I was wondering if anyone has experienced advantage in using `glMapBufferRange()`, which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
      Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
    • By xhcao
      Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness. 
  • Popular Now