• Advertisement
Sign in to follow this  

OpenGL Question about glBindTexture and using different targets with the same ID

This topic is 2851 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, I've been poking around with glBindTexture, and I noticed that you can store at least two different textures under the same texture ID by using different targets. For example:
void init() {
  glActiveTexture(GL_TEXTURE_0);

  glBindTexture(GL_TEXTURE_2D, id); //2d target
  loadSome2DTexture(); //store 2d texture here

  glBindTexture(GL_TEXTURE_CUBE, id); //cube target
  loadSkyTextures(); //store cube map for sky texture here
}

void render() {
  ..
  useSkyShader(); //with samplerCube type in the glsl code, for cube map texture
  drawSky(); 
  useQuadShader(); //with sampler2d type in the glsl code, for the 2d texture
  drawQuad();
}



And this will actually work, both the sky and the quad will render with their different textures. So I was wondering if there is a point of allowing different textures to be stored under the same ID? From what I've quickly looked at direct3d, it doesn't do odd things like this. I ask because I am writing my own effects system and am wrapping up certain opengl functions, and I am trying to decide on how to handle this, like maybe I should hide this functionality, since it seems pointless. Thanks.

Share this post


Link to post
Share on other sites
Advertisement
The name spaces are separate for different texture dimensions. It means that two textures of different dimensions may have the same name returned by glGenTextures, not that one name returned by glGenTextures can be used for multiple textures of different dimension.

Your code is, therefore, logically incorrect. One ID should reference one texture, but you use one ID for multiple textures. In OpenGL 3.0 and up, you cannot allocate your own names anymore, and that code is, even in practice, invalid. Every object must be allocated by the corresponding glGen-function, and you cannot use object names that wasn't allocated.

Share this post


Link to post
Share on other sites
Sorry, I didn't include this in the code above:

glGenTextures(1, &id);


But it was used when I tested it.

Quote:
Original post by Brother Bob
The name spaces are separate for different texture dimensions. It means that two textures of different dimensions may have the same name returned by glGenTextures, not that one name returned by glGenTextures can be used for multiple textures of different dimension.


What do you mean the glGenTextures may return the same name? Normally I thought it's just a different ID/name (I assume you are using name, ID interchangeably) is used per texture of any dimension.

Quote:
Original post by Brother Bob
In OpenGL 3.0 and up, you cannot allocate your own names anymore, and that code is, even in practice, invalid. Every object must be allocated by the corresponding glGen-function, and you cannot use object names that wasn't allocated.


I didn't understand what you mean that you cannot allocate own names anymore. Is there somewhere I can read about how opengl 3.0 allocation of names is different from the previous versions?

Thanks.

[Edited by - andrew111 on April 30, 2010 11:58:29 AM]

Share this post


Link to post
Share on other sites
Quote:
Original post by andrew111
Quote:
Original post by Brother Bob
The name spaces are separate for different texture dimensions. It means that two textures of different dimensions may have the same name returned by glGenTextures, not that one name returned by glGenTextures can be used for multiple textures of different dimension.


What do you mean the glGenTextures may return the same name? Normally I thought it's just a different ID/name (I assume you are using name, ID interchangeably) is used per texture of any dimension.

You can ignore that. I thought for a moment you had to specify the dimension when allocating names, since the name spaces are different, but that is not the case. It will never return the same ID twice, unless it's deleted.
Quote:
Original post by andrew111
Quote:
Original post by Brother Bob
In OpenGL 3.0 and up, you cannot allocate your own names anymore, and that code is, even in practice, invalid. Every object must be allocated by the corresponding glGen-function, and you cannot use object names that wasn't allocated.


I didn't understand what you mean that you cannot allocate own names anymore. Is there somewhere I can read about how opengl 3.0 allocation of names is different from the previous versions?

It is, or was, perfectly OK to allocate your own names and bypass glGenTextures.

GLuint ID = 1;
glBindTexture(GL_TEXTURE_2D, ID);

When allocating the names manually, it is (or, again, was) OK to allocated ID's separate for different texture dimensions. Thus, two textures could have the same ID, but since they belong to different dimensions, they reference different texture objects. Having two variables with the same ID is logically correct, but having the same variable for two textures is not.

You can real all about it in the specification.

Share this post


Link to post
Share on other sites
Quote:
Original post by andrew111
So I was wondering if there is a point of allowing different textures to be stored under the same ID? From what I've quickly looked at direct3d, it doesn't do odd things like this.


The ID returned by glGenTextures is different everytime you call it.

This is wrong
glActiveTexture(GL_TEXTURE_0);

it should be
glActiveTexture(GL_TEXTURE0);

I also suggest different variable names like (id1 and id2 instead of having id for both)
glBindTexture(GL_TEXTURE_2D, id1);
glBindTexture(GL_TEXTURE_CUBE, id2); //cube target

also, there is no such thing as GL_TEXTURE_CUBE. There is something wrong with your glext.h file.

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