• Advertisement


This topic is now archived and is closed to further replies.

OpenGL Few questions on opengl's vertex arrays

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

1. Is there a limit to how many arrays you can make/use? I have a mesh manager so memory is optimized in a way already, but say I have 100 different mesh type each with its own array that will be fine? 2. Im using md2 for mesh format. So I will need to store each animation frame info into the array as well. Is it possible to pass the beginning index of the frame to glDrawElements (ie if frame 3 begins at index 600 of my array i would pass that and pass m_nbVertices long since all animation have the same vertices count. 3. What does glLockArrays and glUnlockArrays do exactly? is it useful to use them? 4. How do I use multiple array? I mean how to I pass from one array to the other. I did a quick test just now and my computer completely crashed, must have not loaded the array correctly. First mesh to render(terrain) ================================ glLockArraysEXT(0, vertXRes*vertYRes); glVertexPointer(3, GL_FLOAT, 0, posVB); glEnableClientState(GL_VERTEX_ARRAY); glDrawElements.... glUnlockArraysEXT; Second mesh to render ======================== glLockArraysEXT(0, m_numVertices); glVertexPointer(3, GL_FLOAT, 0, posVB); glEnableClientState(GL_VERTEX_ARRAY); glDrawElements(GL_TRIANGLES, m_numVertices, GL_UNSIGNED_INT, posVB); glUnlockArraysEXT; This will help me a lot if I figure these out, thanks in advance!

Share this post

Link to post
Share on other sites
First, try to use the normal vertex array function, not the compiled vertex array extension, and see if it works.

The size of the array shouldn''t matter, only that, of course, the more vertices, the more tiem to render them.


3. What does glLockArrays and glUnlockArrays do exactly? is it useful to use them?

They might speed up the things a little bit, but you can''t modify the content of those arrays if you do that.

Height Map Editor | Eternal Lands | Fast User Directory

Share this post

Link to post
Share on other sites
My application currently work if I only use 1 vertex array(ie only render the terrain) but if I try using multiple arrays (1 for the terrain and also render the meshes with an array) it crashes.

Dont need to modify the array ever. They will always be the same.

Thanks for your help, still need some answers though

Share this post

Link to post
Share on other sites
No, my terrain is an object and my mesh is another object, posVB is just the member variable to hold the array.

Share this post

Link to post
Share on other sites
Alright I dont crash now using glDrawArrays....but holy shit check that out lol


Must be with the ways im building my array....although i think its fine.

Are you sure this is okay, I mean the order in which I call them and all?

glVertexPointer(3, GL_FLOAT, 0, posVB);
glDrawArrays(GL_TRIANGLES, 0, 3*m_numTriangles);

Share this post

Link to post
Share on other sites
Well thing is im loading my array with the same data I used before to render my mesh vertex per vertex (it works perfect that way), so the data is obviously good.

the data in vertexListPtr is good im certain of it.

posVB= new float[3*m_numVertices];

for(int i= 0; i < m_numVertices; i++)
posVB[3*i+0]= vertexListPtr[i ].x;
posVB[3*i+1]= vertexListPtr[i ].y;
posVB[3*i+2]= vertexListPtr[i ].z;

edit by ze: fixed code. Please people, don't use i as a loop counter when posting code.

[edited by - zealouselixir on April 30, 2003 12:02:17 AM]

Share this post

Link to post
Share on other sites
Guest Anonymous Poster
You put posVB as the "elements" pointer. That''s wrong. That should be a number of indices.

DrawArrays is slow, because you get no vertex cache re-use on modern cards.

LockArrays() does two things:
1) tells the driver how many vertices there will be in the array (i e, what the maximum index value will be) -- very useful for HT&L cards
2) tells the driver that it can cache transformed vertices until you unlock, unless you re-specify arrays with new calls to VertexPointer (very useful for software transform cards doing multipass)

DrawRangeElements does 1), but not 2).

As far as GL is concerned, there is only one logical vertex array, starting wherever you put the VertexPointer (and NormalPointer, and TexCoordPointer, etc). When you re-specify some other base address, that''s now "the" vertex array. Thus, you can have as many as you can malloc(); GL doesn''t care.

Share this post

Link to post
Share on other sites

You put posVB as the "elements" pointer. That''s wrong. That should be a number of indices.

so you mean when I do
glVertexPointer(3, GL_FLOAT, 0, posVB);

I shouldnt pass posVB? this doesnt makes sense to me, just looked at msdn and it says that third parameter of glVertexPointer should be a pointer to the first element of my array, which is exactly what im doing.

Unless you mean something else?

Share this post

Link to post
Share on other sites

  • 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