Hey everyone, I'm new to these forums... so please be gentle! :)

I'm just wondering if anyone has put thought towards / knows the solution to displaylists with the new openGL standards coming up in future versions.

What I mean is, currently we use glTranslate and glRotate etc when positioning our camera in 3D space... but I personally also use them when rendering geometry into a display list.

If perfectly at peace with losing these functions and working out our own custom matrices... but what if we need to modify the matrix during a list call? displaylists will only store openGL commands, ignoring my own matrix modifications?

Is the solution simply to make sure that calls to glVertex3f() are already transformed within the geometry without using a matrix within the displaylist?

Jon

If you are worried about losing the matrix functions in the new versions, then you are also losing display lists and immediate mode rendering at the same time. Vertex arrays and shaders are the only way forward in the new versions. Also, this is not really new. The new API which dropped all the old stuff was released nearly six years ago.

Moving the thread from coding horrors as well, this is clearly and OpenGL topic.

Basically it boils down to replicating the same functions. Either with something like GLM, some other, or hand-rolled. And then passing to shader via uniform like Hodgman mentioned.