• Advertisement
Sign in to follow this  

OpenGL glColorTable with textures

This topic is 3419 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

Hi All, I'm hardly experienced in OpenGL, but here are my thoughts. I have a project in which I have one fixed texture that will only change color every frame. Later, it will have to be displayed real time, so I thought it would be easy to just draw the same texture all the time and only change the colortable underlying it. For this purpose I have adapted some sample code from the red book. However, it seems the glcolortable calls have no effect. What am I missing? A second question: Can I define my texture as a 2D array (e.g. tex[row][column]) where each value is an index into the colortable? Colortable examples I find online all seem to work on 3D (RGB in third dimension) texture-array, but that doesn't work for me here also. Thanks! Here is my code:
#include <glew.h>
#include <freeglut.h>
#include <stdlib.h>
#include <stdio.h>

#define	checkImageWidth 80
#define	checkImageHeight 60
static GLubyte checkImage[checkImageHeight][checkImageWidth][3];

static GLuint texName;

void makeCheckImage(void)
{
   int i, j, c;
    
   for (i = 0; i < checkImageHeight; i++) {
      for (j = 0; j < checkImageWidth; j++) {
         c = ((((i&0x8)==0)^((j&0x8))==0))*255;
         checkImage[j][0] = (GLubyte) c;
         checkImage[j][1] = (GLubyte) c;
         checkImage[j][2] = (GLubyte) c;
      }
   }
}

void init(void)
{    
   glClearColor (0.0, 0.0, 0.0, 0.0);

   makeCheckImage();

   glGenTextures(1, &texName);
   glBindTexture(GL_TEXTURE_2D, texName);

   glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_REPEAT);
   glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_REPEAT);
   glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST);
   glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST);
   glTexImage2D(GL_TEXTURE_2D, 0, GL_RGB, checkImageWidth, checkImageHeight, 
                0, GL_RGB, GL_UNSIGNED_BYTE, checkImage);
   
   float ColorTable[256][3];
   for (int i=0;i<256;i++)
   {
       // initialize to 0
       ColorTable[0] = 0.0f;
       ColorTable[1] = 0.0f;
       ColorTable[2] = 0.0f;
   }
   ColorTable[0][0] = 0.5f;
   ColorTable[0][1] = 0.0f;
   ColorTable[0][2] = 0.0f;
   ColorTable[255][0] = 0.0f;
   ColorTable[255][1] = 1.0f;
   ColorTable[255][2] = 1.0f;
   glColorTable(GL_COLOR_TABLE, GL_RGB, 256, GL_RGB, GL_FLOAT, ColorTable);
}

void display(void)
{
   glClear(GL_COLOR_BUFFER_BIT);
   glEnable(GL_TEXTURE_2D);
   glTexEnvf(GL_TEXTURE_ENV, GL_TEXTURE_ENV_MODE, GL_DECAL);
   glBindTexture(GL_TEXTURE_2D, texName);
   glEnable(GL_COLOR_TABLE);

   glBegin(GL_QUADS);
   glTexCoord2f(0.0, 0.0); glVertex3f(-1.0, -1.0, 0.0);
   glTexCoord2f(0.0, 1.0); glVertex3f(-1.0, 1.0, 0.0);
   glTexCoord2f(1.0, 1.0); glVertex3f(1.0, 1.0, 0.0);
   glTexCoord2f(1.0, 0.0); glVertex3f(1.0, -1.0, 0.0);
   glEnd();
   glutSwapBuffers();
   glDisable(GL_TEXTURE_2D);
   glDisable(GL_COLOR_TABLE);
}

void reshape(int w, int h)
{
   glViewport(0, 0, (GLsizei) w, (GLsizei) h);
   glMatrixMode(GL_PROJECTION);
   glLoadIdentity();
   glOrtho(-2,2,-2,2,-1,1);
}

void keyboard (unsigned char key, int x, int y)
{
   switch (key) {
      case 27:
         exit(0);
         break;
      default:
         break;
   }
}

int main(int argc, char** argv)
{
   glutInit(&argc, argv);
   glutInitDisplayMode(GLUT_DOUBLE | GLUT_RGB);
   glutInitWindowSize(250, 250);
   glutInitWindowPosition(100, 100);
   glutCreateWindow(argv[0]);
   glewInit();
   init();
   glutDisplayFunc(display);
   glutReshapeFunc(reshape);
   glutKeyboardFunc(keyboard);
   glutMainLoop();
   return 0; 
}

[Edited by - TheWickedD on October 11, 2008 12:11:18 AM]

Share this post


Link to post
Share on other sites
Advertisement
You should call glGetError before and after glColorTable.
If after glColorTable, you get GL_INVALID_OPERATION, then the drivers don't support the imaging subset of GL, of which glColorTable is part of.

Share this post


Link to post
Share on other sites
Hi V-man,

Thanks for the tip. Using GlGetError I found that no error (glColorTable related or otherwise) occurs at any time during execution of the program.

Extra info I just figured out how to retrieve: OpenGL reports version 2.1.2. I'm running on Windows XP with an Nvidia Quadro FX 1500 and updated drivers.

Seems I am somehow forgetting something to enable the colormap, or the current mix of texture drawing and colormap is not correct.

Thanks for the help!

Share this post


Link to post
Share on other sites
Hmm, so never minding the code,
I guess the question is how do I implement the following:
Use an indexed texture (just a single layer, with indices into a color table) and specify a colortable (color lookup table) to color the texture.

Which commands should I use and are there any things I should pay special attention to?

I've tried about 7 possible leads that I found with Google and none seem to make a difference.

Thanks!

Share this post


Link to post
Share on other sites
Well, in general, common GPUs don't support color indexing but if you really want to see what will happen
I'm guessing you need to reference the indices

glTexImage2D(GL_TEXTURE_2D, 0, GL_COLOR_INDEX, checkImageWidth, checkImageHeight,
0, GL_COLOR_INDEX, GL_UNSIGNED_BYTE, checkImage);

It's possible that the driver will just convert to GL_RGBA8.

The other way way to do color indexing is to use a texture and a fragment shader.

Share this post


Link to post
Share on other sites
Hi V-man,

Thank you for the suggestion. I'll look into the shaders, hopefully the implementation of those on the different brands and models of recent graphics cards will be similar. I've given up hope on these ``older'' extentions. Seems on my brand new ATI here glColorTable doesn't exist, where on the Quadro glColorTable has no effect (i've tried the GL_COLOR_INDEX stuff before).

Anyway, shaders are nice and flexible, it will be cool to learn more about them.

Thanks again!

For others with these kind of questions, as a first lead I've found http://www.lighthouse3d.com/opengl/glsl/index.php?color, which seems promising. Example code downloadable at bottom of page

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