• Advertisement
Sign in to follow this  

OpenGL palettes and opengl [Solved]

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

Hello all, I've been trying to get paletted textures to work under OpenGL for the past 4 hours and haven't had any luck so far. Googling turns up a lot of man pages for glColorTable and glTexture2D, but I haven't been able to find a single piece of sample code. My current hardware is an nVidia GeForce 2, which supports the GL_EXT_paletted_texture extention. Since newer GeForces don't support palettes directly, I plan to write a pixel shader to support them -- but I was trying to get older hardware to work right first. :) Anyway, my code looks something like this right now:
	glEnable(GL_TEXTURE_2D);
	glEnable(GL_COLOR_TABLE);
	glPixelStorei(GL_UNPACK_ALIGNMENT, 1);
	glPixelTransferi(GL_INDEX_SHIFT, 8);
	glBindTexture(GL_TEXTURE_2D, texID);
	glColorTable(GL_COLOR_TABLE, GL_RGBA8, 256, GL_RGBA, GL_UNSIGNED_BYTE, palette);
	glTexImage2D(GL_TEXTURE_2D, 0, GL_COLOR_INDEX8_EXT, width, height, 0, GL_COLOR_INDEX, GL_UNSIGNED_BYTE, texture);


The texture is a simple 128x128 8-bit texture with a 256 color RGBA palette. Unfortunately, all I see is a white polygon. I did notice that if I change internalFormat to 1 and format to GL_LUMINANCE, the texture actually shows up, but of course it's just black and white... so I know I'm close. Can anyone give me a tip on what I might be doing wrong here? Or perhaps, even a link to some sample code? Thanks! [ Edit: Added source tags :) ] [Edited by - bpoint on September 5, 2005 11:23:32 PM]

Share this post


Link to post
Share on other sites
Advertisement
Still searching, still poking around and no luck yet.

I have been able to determine that GL_COLOR_TABLE is not a valid glEnable flag, nor is it even necessary -- so I have removed that. I have also changed the target of glColorTable to be GL_TEXTURE_2D, but still no go.

Any thoughts? Anyone? Please? :)

Share this post


Link to post
Share on other sites
Okay, I've been able to determine that the initial code actually works (somewhat) after applying the small changes I described above.

If I force set the first entry in the palette to be RGBA (255,0,0,255), I get a solid red polygon. Just to make sure that my texture data isn't messed up (even though I used GL_LUMINANCE to test it), I force-wrote color indices 0-255 repeatedly in my texture. Still, the only color that is visible is red.

From what I can tell, OpenGL isn't using 256 entries, but using only one... or something like that. I've looked at glPixelMap and notice that there are settings to map indicies to individual R, G, B, and A components, and the fact that the initial size is only 1 leads me to believe that this might be part of the issue. But if I specify individual palette components through glPixelMap, glColorTable then becomes unnecessary... the logic doesn't quite make sense.

I also grabbed the source to PrBoom (OpenGL DOOM clone which uses paletted textures) and looked through their code to see if I could locate anything odd, but unfortunately not. They also don't use glPixelMap at all.

BTW, the glColorTable I use is actually glColorTableEXT. I notice that the function address for glColorTable and the EXT version are different -- and that the non-EXT version doesn't seem to work at all (no red polygon either).

Can anyone shed some light on what could be wrong in that little small code there is? I'm starting to run out of ideas... :(

Share this post


Link to post
Share on other sites
I think you want either:
glEnable(GL_TEXTURE_2D);
glEnable(GL_COLOR_TABLE);
glPixelStorei(GL_UNPACK_ALIGNMENT, 1);
glPixelTransferi(GL_INDEX_SHIFT, 8);
glBindTexture(GL_TEXTURE_2D, texID);
glColorTable(GL_COLOR_TABLE, GL_RGBA8, 256, GL_RGBA, GL_UNSIGNED_BYTE, palette);
glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA8, width, height, 0, GL_COLOR_INDEX, GL_UNSIGNED_BYTE, texture);

or
glEnable(GL_TEXTURE_2D);
glEnable(GL_COLOR_TABLE);
glPixelStorei(GL_UNPACK_ALIGNMENT, 1);
glPixelTransferi(GL_INDEX_SHIFT, 8);
glBindTexture(GL_TEXTURE_2D, texID);
glColorTableEXT(GL_TEXTURE_2D, GL_RGBA8, 256, GL_RGBA, GL_UNSIGNED_BYTE, palette);
glTexImage2D(GL_TEXTURE_2D, 0, GL_COLOR_INDEX8_EXT, width, height, 0, GL_COLOR_INDEX, GL_UNSIGNED_BYTE, texture);

But I haven't actually tried either, so they might still be wrong. Regardless, you'll almost certainly get better performance by converting your indexed images to RGBA format yourself.

Enigma

Share this post


Link to post
Share on other sites
Enigma, thanks for the reply. Unfortunately, neither of the two suggestions worked... :(

glEnable(GL_COLOR_TABLE) doesn't appear to be valid. I get a GL_INVALID_ENUM error after calling it.

Quote:
Original post by Enigma
I think you want either:

glColorTable(GL_COLOR_TABLE, GL_RGBA8, 256, GL_RGBA, GL_UNSIGNED_BYTE, palette);
glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA8, width, height, 0, GL_COLOR_INDEX, GL_UNSIGNED_BYTE, texture);



This made my test polygon black, even though I have the default color set to white... :/ I can't seem to get glColorTable (non-EXT) to do anything. If this did work, I believe what would happen here is OpenGL would probably unpack the color indexed texture into RGBA format when uploaded into video memory...

Quote:
or
glColorTableEXT(GL_TEXTURE_2D, GL_RGBA8, 256, GL_RGBA, GL_UNSIGNED_BYTE, palette);
glTexImage2D(GL_TEXTURE_2D, 0, GL_COLOR_INDEX8_EXT, width, height, 0, GL_COLOR_INDEX, GL_UNSIGNED_BYTE, texture);



This is basically what I've been able to get to work so far -- but the entire texture is mapped to a single color, which is the value of palette[0].

Quote:
Regardless, you'll almost certainly get better performance by converting your indexed images to RGBA format yourself.


The GeForce2 I have only has (heh) 64Mb of video RAM and I'm going over the limit already for a single frame when I use 24-bit RGB textures. I don't know how much a performance impact paletted textures have, but it's gotta be faster than having to page in/out 24-bit textures every frame. That's really the reason why I'm trying to get palettes to work.

Any other ideas? :) I'm gonna see if I can find some sample code somewhere on sourceforge...

Share this post


Link to post
Share on other sites
One more small thing:

As a test, I added the following code in my render loop, after calling glBindTexture():

static u8 val = 0;

palette[0].r = val++;
palette[0].g = 0;
palette[0].b = 0;
palette[0].a = 255;
glColorTableEXT(GL_TEXTURE_2D, GL_RGBA8, 256, GL_RGBA, GL_UNSIGNED_BYTE, palette);


This causes the entire polygon to cycle through red color range, so it's obvious palettes are at least _working_. Now why the entire texture map is reallocated to only use palette entry zero is the only remaining mystery... :/

Share this post


Link to post
Share on other sites
FIXED IT! Finally...!

The culprit was the call to glPixelTransfer to set GL_INDEX_SHIFT. After commenting out that line, everything worked perfectly. Incidentally, GL_INDEX_SHIFT defaults to zero.

In the end, all that was necessary was:

glEnable(GL_TEXTURE_2D);
glPixelStorei(GL_UNPACK_ALIGNMENT, 1);
glBindTexture(GL_TEXTURE_2D, texID);
glColorTableEXT(GL_TEXTURE_2D, GL_RGBA8, 256, GL_RGBA, GL_UNSIGNED_BYTE, palette);
glTexImage2D(GL_TEXTURE_2D, 0, GL_COLOR_INDEX8_EXT, width, height, 0, GL_COLOR_INDEX, GL_UNSIGNED_BYTE, texture);


That's it!

I don't think too many people are using palettes nowadays, but even still, this might not be a bad thing to add to the FAQ... ;)

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Unless you're working with 256 colors (why on Gods green earth are you recreating Wolf3D) you really don't need to do this. Plus from my understanding glPixelTransfer is SLOW. I could be wrong it's been 2 years and I don't remember using that function, just something about staying away from it... *shrug*.

Share this post


Link to post
Share on other sites
If you had even bothered to read the thread in its entirety before commenting, you would have already noticed that I'm running out of video memory, and textures are being paged in and out.

I don't know what kind of bad experience you had with glPixelTransfer, but I was able to bring my frame rate back from ~6fps (paging 24-bit RGB textures) to around 80fps (using 8-bit palettes). I'm quite pleased with the result.

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