Part of the Khronos Group

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Results 1 to 5 of 5

Thread: OpenGL: VBO and a broken GC

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Junior Member Newbie
    Join Date
    Jul 2013

    OpenGL: VBO and a broken GC

    I have recently tried the use of VBO. I just copy pasted the code from this site(This site preventing me to post the URL)

    It compiles fine and seems running well. However, I noticed on the taskmanager that the program runs at 50% CPU usage. Its just a simple triangle, nothing else. I was expecting it to be of 0% because all of other programs I created in glfw3 runs on 0% when idle. I know that V-SYNC in glfw3 is set true by default, but still I add this line of code to ensure
    Code :
    glfwSetInterval(GL_TRUE); //sets V-SYNC on
    but still nothings changed.

    After messing with the `test_vs.glsl` (I think this has nothing to do with the problem):

    code I changed:


    Code :
    in vec3 vp;
        void main ()
            gl_Position = vec4 (vp, 1.0);


    Code :
    in vec2 vp;
        void main ()
            gl_Position = vec4 (vp, 0, 1.0);

    And changed attributes of vertex in .cpp code to 2D.

    Running several times the `Hello Triangle` program again, computer stops and hang a bit ---> Then **CRAASSH**. The graphics card is broken! (literally ouch). The computer shutdowns itself, and I try rebooting it again, I got a screen with full of random lines displaying and fail to continue on desktop.

    I don't have much of the information about the graphics card but glew says
    GeForce 7300 GT/PCI/SSE2/3DNOW!
    and running on Windows XP with OpenGL v2.1 support according to glew.

    Some of the extensions I added:

    • Code :
      glfwWindowHint(GLFW_SAMPLES, 4);
    • Code :
      glfwWindowHint(GLFW_OPENGL_CORE_PROFILE, 2);
    • Code :
      glewExperimental = GL_TRUE;
    • And I add the prefix ARB to any function related to VBO

    I suspect this is due to lack of OpenGL extensions support check. But, is that so really the problem? Is it the simple program or other? If so, why would they let this to happen?
    Last edited by mr5zzz; 01-08-2014 at 06:59 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts