From: Domingo F. S. <lin...@ya...> - 2004-02-13 12:36:08
|
El Viernes, 13 de Febrero de 2004 01:29, Ville Syrj=E4l=E4 escribi=F3: > mga? The poster said it was observed on ATI cards. That's right. That's why I asked in the dri lists. I previously posted a=20 similar mail in debian-powerpc and Michel D=E4nzer suggested that the=20 problem could be DRI specific. I also have a nVidia card and everything=20 works well there. As Brian says, glPushAttrib() seems to bring OpenGL to an undefined state.= =20 =46or instance, I have some lights in the scene which are positioned after= =20 camera movement so if I move the camera the lights remain pointing to the=20 ground; then I have some objects pushing the GL_LIGHTING_BIT which causes=20 the lights to be displaced as the camera moves, weird. If I don't use=20 glPushAttrib() the scene renders properly. The GL_CURRENT_BIT doesn't work either, color is not well restored after=20 glPopAttrib(). Well, I guess the explanation is not quite clear. I could write a sample=20 program to test glPushAttrib() if you want. |