Sign in to follow this  
DaMuzza

OpenGL signed LUMINANCE8_ALPHA8

Recommended Posts

Under Direct3D, I store my normal maps in the format V8U8. This is a signed format so I in the pixel shader I can do: normal.xy = texture.RG; normal.z = (computed...) Under OpenGL, Nvidia recommend using the format GL_LUMINANCE8_ALPHA8. However, I'm having some troubles getting the correct results from it. I *think* that my problem lies with my texture generation rather than my pixel shader. For reference, the only difference in the pixel shader is that rather than doing: normal.xy = texture.RG; it becomes: normal.xy = texture.GA; My results are 'close' to being correct, and at first glance appeared to be fine, but on further examination, the normal values are not correct. I create my texture data like this: glTexImage2D( GL_TEXTURE_2D, miplevel, GL_LUMINANCE8_ALPHA8, Width, Height, 0, GL_LUMINANCE_ALPHA, GL_BYTE, // signed data ); There are two things I'm not sure about. Firstly, I cannot find anywhere whether GL_LUMINANCE8_ALPHA8 is a signed format. Will my pixel shader (in Cg) read the texture to be from -1 to 1, or 0 to 1? From observation, it appears to be signed, but it would be nice if I could find documentation somewhere to support that. Secondly, before calling glTexImage2D, I suspect I may need to use glPixelTransfer to tell OpenGL exactly how I want the texture data formatted. I've experimented with various values that I though made sense, but with no luck. Can anyone help? Alternatively, if anyone knows of any demo that generates a texture of format GL_LUMINANCE8_ALPHA8, then that could be useful too. Thanks

Share this post


Link to post
Share on other sites
To add to this, I've discovered that glTexImage2D is discarding the sign bit on all the data that I pass in.
If I use GL_SIGNED_LUMINANCE8_ALPHA8_NV, rather than GL_LUMINANCE8_ALPHA8, then everything works fine.
I can find no version of GL_SIGNED_LUMINANCE8_ALPHA8_NV for ATI cards though.

Any ideas?

Thanks

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
      627765
    • Total Posts
      2978983
  • 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.  
      -Questions
      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