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


OpenGL Few questions on opengl's vertex arrays

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

  • Announcements

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By test opty
      Hi all,
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
  • Popular Now