Changes between Version 62 and Version 63 of WikiStart

Timestamp:

Jan 4, 2013, 4:27:33 AM (12 years ago)

Author:

Ben Lippmeier

Comment:

--

WikiStart

@@ -40 +40 @@
 
 '''Q: I'm getting an "internal stack overflow" or "internal stack underflow" error from OpenGL when running a program that draws a picture recursively.'''[[br]]
-A: Your GPU hardware has a fixed sized transform matrix stack. Each time you use a 'rotate' 'translate' or 'scale' transform then a matrix is pushed on this stack. When the stack is full you should get an overflow error and the OpenGL library should kill the process. If your OpenGL library was poorly implemented then matrices pushed onto a full stack will be silently discarded, and then when Gloss tries to pop the full number this will cause an underflow. This problem is discussed further in Section 4 of [http://www.opengl.org/archives/resources/features/KilgardTechniques/oglpitfall/ Overflowing the Projection Matrix Stack]. Gloss tries not to use the stack when it doesn't have to, but to avoid this error completely we'd need to give up on hardware accelerated geometry transforms, and write our own software implementation.  It is a deeply sad limitation of the OpenGL API. If you know a better way to address this problem then please let us know on the mailing list.
+A: Your GPU hardware has a fixed sized transform matrix stack. Each time you use a 'rotate' 'translate' or 'scale' transform then a matrix is pushed on this stack. When the stack is full you should get an overflow error and the OpenGL library should kill the process. If your OpenGL library was poorly implemented then matrices pushed onto a full stack will be silently discarded, and then when Gloss tries to pop the full number this will cause an underflow. 
+
+The OpenGL specification requires that every implementation has at least 32 entries in the transform matrix stack, so you should be able to apply this many nested 'rotate' 'translate' and 'scale' transforms to your picture. If this isn't enough then you can probably refactor your program so it doesn't use so many nested transforms. 
+
+This problem with a fixed size transform stack is discussed further in Section 4 of [http://www.opengl.org/archives/resources/features/KilgardTechniques/oglpitfall/ Overflowing the Projection Matrix Stack]. Gloss tries not to use the stack when it doesn't have to, but to avoid this error completely we'd need to give up on hardware accelerated geometry transforms, and write our own software implementation.  It is a regretful limitation of the OpenGL API. If you know a better way to address this problem then please let us know on the mailing list.
 
 '''Q: Gloss crashes at startup.'''[[br]]