Thread: Program starting to become laggy...

To give you an idea of a render loop this is one of mine. It is from my terrain engine that I posted screenshots of.

Code:

bool Display(float timeDelta)
{
  if (g_pDevice)
  {
    g_pDevice->Clear(0,0,D3DCLEAR_TARGET | D3DCLEAR_ZBUFFER,SkyColor,1.0f,0);
    g_pDevice->SetRenderState(D3DRS_FILLMODE,D3DFILL_WIREFRAME);


    D3DXMATRIX View;

    TheCamera.getViewMatrix(&View);
    g_pDevice->SetTransform(D3DTS_VIEW,&View);
    GetKeyboardInput();    
  
    g_pDevice->BeginScene();
    
    
    TheTerrain.Render(timeDelta);
    
    g_pDevice->EndScene();
    
    g_pDevice->Present(0,0,0,0);
  }


  return true;
}

That's it. Now a game would have significantly more, but most of the processing and core code is outside of the main render loop. Main render loops should be small and concise.

And translating one quad to create a grid is well...um...ludicrous.
Have you actually read any of these responses? If you have you would know about 95% of this already since it has already been posted. Read.

My patience grows thin because:

• Nearly everyone that has responded has said the same thing and yet you insist that your way is working. If it was working right then well you wouldn't be here asking us now would you? I don't like it when people tell someone a solution and they respond with arguments. Just admit you have no idea what you are doing and let us help you.
• It's obvious from your recent replies that you have not read or heeded any of the advice given in any of the responses because your code still has the for loops, still has the glBegin() and glEnd() functions all over - all of these have been addressed. Fix it.
• You need to probably read a book on how OpenGL works. We cannot explain the API in one post. It also appears that you don't understand some fundamental graphics concepts in 2D, let alone use an API that was really designed for 3D. Buy a book:
  www.amazon.com has many.
• All of us started out in graphics not having a clue as to what we are doing. Don't be a poser. There is nothing wrong with not knowing how to do something in code, there is something wrong with acting like you do, when we all know you don't. Be open and honest and have an open mind when people respond and you will get a much better attitude from all of us.
  

When you show that you are interested in fixing your code rather than arguing with us when we tell you it's wrong, then we, or at least I, will be a lot nicer.

I am reading all the posts that are being sent my way but, I'm just not understanding, not everyone is saying the exact same thing.... I guess there is no excuse for ignorance when you've been told your problem, but you still don't understand it....

You keep saying I'm using the API incorrectly, I learned all I know from NeHe, I guess theres nothing on there about writing efficient drawing methods.... (it is understandable that drawing 392 quads for a grid is unreasonable, just felt like the most logical way to do it... (one object for each seat)), guess not, guess it would be better if I were to write just a couple functions that used lines to create a border and cells..... and then use mouse detection to seperate the cells... that would definately be more efficient....

You make it seem that I am purposely not taking your information, but I am, I'm just not understanding it...

About the GLBegin()/end()'s..... what do I do to avoid them?
Do display lists provide a way around them? whenever you draw a new object don't you need to GLBegin???

I'll just go read the RedBook, I suppose, maybe i'll be able to teach myself something about proper drawing methods...

I believe you when you say loops and glbegins/ends are my problem, but I just want to know all the logic behind it as well, forgive me if I can't take your word as law, logic is king in my world, I need to know WHY :d..... (especially If I'm about to rewrite my entire program)....

I will take your word for truth, but all this time i've just been bugging for an answer why...

Alright, sounds simple, gotta figure out how to manipulate the vertex buffer though, more learning to do!


Doh, stupid post, this might work, if I make a function that makes click detection for each cell, if you click the cell, it does something along these lines:

Code:

glColor3f (1.0, 0.0, 0.0);  /* the current RGB color is red: */
                            /* full red, no green, no blue. */
glBegin (GL_POINTS);
    glVertex3fv (point_array);
glEnd ();

I'd have to do that for 10x10 pixels though (and then 392 times), thats a bunch...
Must be a better way......

Vertex Buffer, Vertex Buffer..... hmmmmm

"reads about the framebuffer"....... Oh...

so theres a color buffer, a depth buffer, stencil buffer... etc etc, all of these hold information for a single pixel, which buffer it is determines what kind of information they hold, okay, got it....

But to manipulate the color buffer to color in a specific set of pixels... (instead of drawing a square for each area I want to color!)...

Still researching....

I believe I've pinpointed the exact thing I need to learn, Redbook says, and I quote

Up to four optional, nondisplayable auxiliary color buffers can also be supported. OpenGL doesn't specify any particular uses for these buffers, so you can define and use them however you please. For example, you might use them for saving an image that you use repeatedly; rather than redrawing the image, you can just copy it into the usual color buffers. See the description of glCopyPixels() in "Reading, Writing, and Copying Pixel Data" for more information about how to do this.

Now I just gotta find out where the actual description is

Ahah!

You can read the contents of the color, depth, and stencil buffers with the glReadPixels() command. Likewise, glDrawPixels() and glCopyPixels() are available for sending images to and BLTing images around in the OpenGL buffers.

Info can be found here I believe

Learning is cool