• Advertisement
Sign in to follow this  

OpenGL OpenGL Shaders

This topic is 4734 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

New poster here, but I'm working on my PhD; greetings to all season-tempered vets. I have a quick question for the community. I had a relatively large project which used fixed-functionality multi-texturing for coloring items. In order to have more control over the way the textures were applied, I replaced this fixed-functionality multi-texturing with OpenGL Shading Language vertex and fragment shaders. However, though I mimic the modulate equations specified in the OpenGL standard, the results don't look the same. Previously I was using GL_MODULATE which multiplies each RGBA component for each texture to determine the final fragment color. In my shader (which is attached), I read in the texture correctly, get the texture coordinates correctly, but the equation does not give the same result as the fixed-functionality multi-texturing gave. Do you see anything in the attached vertex and fragment shader code that I could be doing wrong? If I had to guess, I think the differences arise due to truncation error or loss of precision in the pow() function. Does anyone know how GL_MODULATE is implemented in the fragment shader more specifically than: glFragColor *= texture2D(tex0,gl_TexCoord[0].xy) as specified in the GLSL Orange Book (pg.232)? For multitexturing this *should* translate into equation 1 below, but it doesn't. To keep this post from being any longer, I'm pretty sure that everything is correct except the equation itself. Following are the fragment shader equations that have been tried (with comments) where each color variable is a vec4 lookup from the appropriate texture: //OpenGL definition which doesn't get close to approximating the original gl_FragColor = color1*color2*color3; (Equation 1) //Gets much closer, but the colors are still slightly off (enough to be unacceptable) gl_FragColor = pow((color1*color2*color3),(1.0/3.0)); (Equation 2) Thanks in advance, []HoA[]Newbird forever, lol.

Share this post


Link to post
Share on other sites
Advertisement
Maybe this can help:

ShaderGen - Fixed Functionality Shader Generation Tool
http://developer.3dlabs.com/downloads/shadergen/index.htm

Share this post


Link to post
Share on other sites
One of my friends actually sent me this yesterday. It's a very nice tool and can be useful for generating shaders when you don't know what's going on. However, this tool doesn't support multi-texturing which is my whole problem. To be more thorough, the entire fragment shader I'm using is provided below. I only have one color lookup table texture, but I have 3 floating point (between 0.0 and 1.0 of course) RGBA values that I want to use exactly as if they were 3 different textures being used by OpenGL's fixed-functionality multi-texturing. Again, any help would be greatly appreciated.

uniform sampler1D clutTexture;
void main(void) {
vec4 color1 = vec4 (texture1D(clutTexture, gl_TexCoord[0].x));
vec4 color2 = vec4 (texture1D(clutTexture, gl_TexCoord[1].x));
vec4 color3 = vec4 (texture1D(clutTexture, gl_TexCoord[2].x));

gl_FragColor = color1*color2*color3;
//gl_FragColor = pow((color1*color2*color3),(1.0/3.0));
}

Share this post


Link to post
Share on other sites
Total longshot at the moment, but just throwing out something I noticed. Doesn't GL_MODULATE also multiply in the polygon color or material properties? Though if you were using white, this wouldn't be an issue.

Share this post


Link to post
Share on other sites
Its probably not the issue, but worth a mention: according to an nVidia engineer even when you duplicate the stages of the fixed function pipeline on Fx cards and older you won't get the exact same results because back then the code ran on different parts of the card and so different results can be produced.

Like I said, its more than likely not an issue for this but just wanted to share that tidbit of info, because it made a huge difference for me on depth buffer manipulation.

Share this post


Link to post
Share on other sites
Yes, you are right GluCose. But, I am using white and no materials or lighting. I'm aware of the issues that would arise if I used either of these with the posted fragment shader.

The engineering consideration of the fragment shader running on different parts of the card is plausible since I'm using a Quadro FX 1000. I will look into this. I've already emailed 3D labs and Randi Rost (author of OpenGL orange book). jm_hewitt, where did you find that information?

Just a general statement, I personally find the lack of information on OpenGL's shaders for fixed-functionality operation a great shame. The fixed-functionality operations for vertex and fragment shaders should be provided to the community. Programmers want to manipulate, augment, and enhance the functionality of OpenGL, not replace it outright. </rant>

Share this post


Link to post
Share on other sites
u should be able to duplicate it pretty much exactly the only difference is the glsl pipeline uses 32bit throughout (thus is higher precision) but this shouldnt result in anty great difference

check out first how multitexture works
see the opengl spec at www.opengl.org
also goto the nvidia developer site and download some pdf's about multitexture,

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement