Sign in to follow this  

OpenGL Trouble arranging my 3d model data inside a vertex array

Recommended Posts

Greetings everyone, I've had my .Obj file loader working for a really long time under immediate mode rendering. I really want to move away from the slow immediate mode calls for sending vertex data through the pipeline and I figured that I should first get my code to work using vertex arrays and then ultimately VBO's. The following is the structure that defines my vertex data and my model data. I use std::vectors to append data but I'm not entirely sure how to deference a vector when specifying the vertex data when creating the vertex array in opengl. Can someone give me some insight as to what I should do in order to get vertex arrays to work?
struct sVertex3d 
	float vertex[3];

// a single texture coordinate
struct sTexCoord
	float coord[2];

// a single triangle normal
struct sNormal3d
	float normal[3];

struct sFace
	vector<int> vertlist;	// the vertices that make up this face
	vector<int> normlist;	// the list of normals that make up this face
	vector<int> texcoordlist;	// the list of texture coordinates that make up this face
	vector<int> combined;	// the combined indices for this face

	string material;	// which material does this face use

class ObjModel {
	bool LoadModel(char *fname);
	bool LoadMtl(char *mtlfilename);	// loads a material library file
	sMaterial *FindMatByName(string name);	// searches the array of materials by name and returns the matching material
	void Draw();	// draw the geometry for the model

	int numObjects;	// the number of objects that make up this model
	string filename;	// the name of the obj model file
	sObject *objects; // the list of objects that make up the model

	int numVerts;
	int numTexCoords;
	int numNormals;
	int numFaces;

	sVertex3d *pvertices;	// array of vertices in the model
	sNormal3d *pnormals;	// array of normals in the model		
	sTexCoord *ptexcoords;  // array of texture coordinates in the model
	sFace *pfaces;	// array of faces in the model. Faces have indices into the normals, texture coords, and vertex lists

	map<string, sMaterial> mats;	// the list of materials from all of the material libraries

Share this post

Link to post
Share on other sites
Hey jon723, you've definitely made the right decision moving to VBO's.

To dereference an stl vector what you need to do is something along the lines of:
// loop through all elements in the vector
for( std::vector<int>::iterator it; it = vertlist.begin(); it != vertlist.end(); it++ ) {
int a_number = (*it); // this dereferences the iterator 'it'

So just to give you an overview of what you *should* be doing here to initialise:
#1.) Create your VBO & bind it
#2.) Map your VBO (From here we get a data pointer)
#3.) Loop through your vertex elements
#4.) Copy the elements into the VBO (Using that data pointer)
#5.) Unmap your VBO


Share this post

Link to post
Share on other sites
With stl::vector, the elements are stored in an array so a simple

glBufferData(........., &myvector[0]);


glBufferSubData(........., &myvector[0]);



memcpy(pointer, &myvector[0], size);

Share this post

Link to post
Share on other sites
Hey, thanks for both of the replies. I've read the nehe article before, but I wasn't exactly sure how to mold it into the vector solution I was using. I'll definitely take your suggestions into account. Thanks again.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By JFT

      I am trying to optimize shadow mapping for an rts-view (nearly top down) with directional light.

      My approach so far is to intersect the camera view frustum with the plane of the terrain on which all the units are moving and
      fit a box around the four intersection points:

      Then I use the center of the box and the light direction to construct a view matrix.
      To construct the orthographic projection matrix I use the corners of my box. 

      With that I somehow do not get the wanted results (no shadows) /shadow map is not correctly created for the view of the camera.
      I think I am maybe missing some translation/rotation?

      Is there a better way for rts-views with a single shadow map ?

      Thanks for your help beforehand!
    • By lonewolff
      Hi guys,
      With OpenGL not having a dedicated SDK, how were libraries like GLUT and the likes ever written?
      Could someone these days write an OpenGL library from scratch? How would you even go about this?
      Obviously this question stems from the fact that there is no OpenGL SDK.
      DirectX is a bit different as MS has the advantage of having the relationship with the vendors and having full access to OS source code and the entire works.
      If I were to attempt to write the most absolute basic lib to access OpenGL on the GPU, how would I go about this?
    • By DelicateTreeFrog
      Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
      Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
      For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
      So, here's what the plan is so far as far as loading goes:
      Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
      Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
      Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
      The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
      So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
      With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!
    • By JJCDeveloper
      I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks
    • By AyeRonTarpas
      A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

      -What I'm using:
          C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.  
      Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?  
  • Popular Now