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

Thread: OpenGL API Decisions

  1. #1
    Intern Contributor
    Join Date
    Apr 2005
    Posts
    98

    OpenGL API Decisions

    Does anybody know why the authors of GLU decided to only support doubles for methods such as gluProject, gluUnproject, and gluTessVertex? I find it odd since GL is type friendly in almost every other part of the API, and most systems are optimized for floats. To this point, I have left my data as doubles, but have been persuaded to change them to floats to maintain compatibility with some legacy code. I realize I can write floating point versions. I am just curious about the design decision.

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

    Re: OpenGL API Decisions

    For GL, way back then it was assumed that perhaps one day video cards that support doubles would become available although that didn't happen yet.

    GLU is not part of GL.
    I don't know the reason. There are other "math libs" and "utility lib"

    Lots of libs here
    http://abattoir.wolfpaw.net/personal/gamelibs.php

    Math++, GLM, Graphics Library Helper (that one is mine)
    ------------------------------
    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);

Posting Permissions

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