• Advertisement
Sign in to follow this  

OpenGL Get Available Space for 3D Texture

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

Hey guys, I'm trying to render a cube with a 3D texture on it and have trouble when the texturesize becomes to big. I tried a few things to figure out where the texture will be ok or not. 1) First: i figure out which maximum texture size is supported and which version of opengl i'm using.
int texSize[3];
glGetIntegerv(GL_MAX_3D_TEXTURE_SIZE, texSize);
const GLubyte* string = glGetString(GL_VERSION);

The results are: <512, uninitialized, uninitialized> for texSize and 2.0.1 for string. I assume that this means that the maximum size is <512, 512, 512> 2) Second: i use a proxy texture to find out whether there is enough space for the texture or not
             extent[0], extent[1], extent[2],
             0, GL_LUMINANCE, GL_UNSIGNED_BYTE, 0);
GLint width, height, depth;
glGetTexLevelParameteriv(GL_PROXY_TEXTURE_3D, 0, GL_TEXTURE_WIDTH, &width);
glGetTexLevelParameteriv(GL_PROXY_TEXTURE_3D, 0, GL_TEXTURE_HEIGHT, &height);
glGetTexLevelParameteriv(GL_PROXY_TEXTURE_3D, 0, GL_TEXTURE_DEPTH, &depth);

The extent i'm using is <512, 512, 267>. The width height and depth values are set according to the extent. After that i thought: Well looks good for my texture to fit into memory. 3) Third: Now i'm using Texture Objects to Bind the Texture with the following code
glBindTexture(GL_TEXTURE_3D, identifiers[textureId]);


// extent[0], extent[1], extent[2],
glTexImage3D(GL_TEXTURE_3D, 0, GL_RGBA, 
             extent[0], extent[1], extent[2], 
             0, GL_LUMINANCE, GL_UNSIGNED_BYTE, image);
delete[] image;

4) Fourth: I would like to check whether the texture is now ready to use or not, and did the following:
glBindTexture(GL_TEXTURE_3D, identifiers[textureId]);
GLint residency;
glGetTexParameteriv(GL_TEXTURE_3D, GL_TEXTURE_RESIDENT, &residency);
glGetTexLevelParameteriv(GL_TEXTURE_3D, 0, GL_TEXTURE_WIDTH, &width);
glGetTexLevelParameteriv(GL_TEXTURE_3D, 0, GL_TEXTURE_HEIGHT, &height);
glGetTexLevelParameteriv(GL_TEXTURE_3D, 0, GL_TEXTURE_DEPTH, &depth);

Cause' the width, height and depth values are still equal to the extent and not 0 i thought everything is ok. So whats the problem now: When i use glTexImage3D with my extent than the window is black. When i call it like this:
glTexImage3D(GL_TEXTURE_3D, 0, GL_RGBA, extent[0], extent[1], 220, 0, GL_LUMINANCE, GL_UNSIGNED_BYTE, image);

everything is ok. When i call it with 230 the window is black. So how can i find out why the window is black. Is it because the texture is to big? But why is glGetTexLevelParameteriv still returning non-zero values? looking forward to your help!!! myke

Share this post

Link to post
Share on other sites
1) - It returns only the depth parameter actually, so the maximum 3D texture resolution in your case is x*x*512 (where x is GL_MAX_TEXTURE_SIZE, usually 2048 on today hardware)

As for proxy textures, IIRC OpenGL is talking about size (as in dimensions), not space (as in memory space, which cannot be portably determined), thus seeing that you're texture is 512x512x267xRGBA => more then 256MB, i'd say that yes, you may be running out of graphics memory.

Share this post

Link to post
Share on other sites
Thanks for your reply snoutmate!
You are right, the texture is just to big. I didn't consider that, cause my texture is actually just ~68MB large, but with the internal format it becomes 4*68 which is too big. It works by changing the the glTexImage3D command to:

glTexImage3D(GL_TEXTURE_3D, 0, GL_LUMINANCE, extent[0], extent[1], extent[2], 0, GL_LUMINANCE, GL_UNSIGNED_BYTE, image);

I'm still interested if it is possible to find out at runtime, that a texture was to big? Cause' when you have more than one objects in memory and you don't know the exact size of each of them, it would still be interesting to find out how much space is left, or at least to find out if the data (GL_ARRAY_BUFFER, GL_TEXTURE_*) was bound successfully.

Share this post

Link to post
Share on other sites
For reference the value returned from glGetTexParameteriv(GL_TEXTURE_3D, GL_TEXTURE_RESIDENT, &residency); is pretty much worthless and tells you nothing on a modern system.

Share this post

Link to post
Share on other sites
Original post by Myke111
I'm still interested if it is possible to find out at runtime, that a texture was to big? Cause' when you have more than one objects in memory and you don't know the exact size of each of them, it would still be interesting to find out how much space is left, or at least to find out if the data (GL_ARRAY_BUFFER, GL_TEXTURE_*) was bound successfully.

What you are doing is correct.
shows the same method.

Perhaps your driver is buggy.
I would also call glGetError after creating the real texture to see if it returns any errors. Maybe it will return GL_OUT_OF_MEMORY.

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?
    • 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