Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Results 1 to 4 of 4

Thread: Unbinding VBO under GL-3

  1. #1
    Member Regular Contributor DmitryM's Avatar
    Join Date
    Mar 2009
    Location
    Toronto
    Posts
    436

    Unbinding VBO under GL-3

    I just realized that I'm not able to unbind any VBO...
    Calling BindBuffer(<some>,0) causes InvalidOperation error.
    WinXP, Catalyst 9.5, Radeon 2400HD.

    I'm using VAO storing all required VBO attached so I really didn't need to unbind any VBO until now.
    But now I'm trying to use PBO. If I don't unbind PIXEL_UNPACK_BUFFER, then I'm not able to call glTexImage* to initialize any of my textures after that.

    Did anyone experience such problems?

  2. #2
    Super Moderator OpenGL Guru
    Join Date
    Feb 2000
    Location
    Montreal, Canada
    Posts
    4,421

    Re: Unbinding VBO under GL-3

    Have you tried to unbind VAO?
    ------------------------------
    Sig: http://glhlib.sourceforge.net
    an open source GLU replacement library. Much more modern than GLU.
    float matrix[16], inverse_matrix[16];
    glhLoadIdentityf2(matrix);
    glhTranslatef2(matrix, 0.0, 0.0, 5.0);
    glhRotateAboutXf2(matrix, angleInRadians);
    glhScalef2(matrix, 1.0, 1.0, -1.0);
    glhQuickInvertMatrixf2(matrix, inverse_matrix);
    glUniformMatrix4fv(uniformLocation1, 1, FALSE, matrix);
    glUniformMatrix4fv(uniformLocation2, 1, FALSE, inverse_matrix);

  3. #3
    Member Regular Contributor DmitryM's Avatar
    Join Date
    Mar 2009
    Location
    Toronto
    Posts
    436

    Re: Unbinding VBO under GL-3

    Yes, it was the first thing I tried.
    No errors, but it doesn't help to unbind VBO...

  4. #4
    Senior Member OpenGL Guru
    Join Date
    May 2009
    Posts
    4,726

    Re: Unbinding VBO under GL-3

    Calling BindBuffer(<some>,0) causes InvalidOperation error.
    WinXP, Catalyst 9.5, Radeon 2400HD.
    Sounds like a driver bug. Also, your drivers are old; try newer versions. If those don't work, contact ATi as best you can.

Posting Permissions

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